asn.dev

Observed topology

AS214331 TESKE-VIRTUAL-SYSTEM

Unclassified RIPE NSP

Upstreams 4 carry this network
Downstreams 6 this network carries
Adjacent (IPv4) 8
Adjacent (IPv6) 8
Upstream graph Who carries AS214331, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS214331 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS214331: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS267613ELETRONET S.A.UnclassifiedIPv4 IPv6116
AS6939Hurricane Electric LLCTransitIPv4 IPv689
AS174Cogent Communications, LLCTransitIPv4 IPv623
AS24482SG.GSHostingIPv4 IPv65

Transit

Downstream networks

inferred

Networks for which AS214331 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS214569MIRALIUM SERVICOS EM TECNOLOGIA DA INFORMACAO LTDAUnclassifiedIPv4 IPv6133
AS270765VIVA PIXEL AGENCIA DIGITALUnclassifiedIPv4 IPv659
AS209338Mauro Paes CorreaUnclassifiedIPv620
AS214205Cristian Tudor MarcusUnclassifiedIPv619
AS198057Flooyd Telecom LTDAResidentialIPv41
AS200464PAULO HENRIQUE SILVA DE OLIVEIRAUnclassifiedIPv41

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS214331 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS267613ELETRONET S.A.UnclassifiedIPv4 IPv6235
AS6939Hurricane Electric LLCTransitIPv4 IPv6204
AS214569MIRALIUM SERVICOS EM TECNOLOGIA DA INFORMACAO LTDAUnclassifiedIPv4 IPv6133
AS270765VIVA PIXEL AGENCIA DIGITALUnclassifiedIPv4 IPv659
AS174Cogent Communications, LLCTransitIPv4 IPv653
AS214205Cristian Tudor MarcusUnclassifiedIPv652
AS209338Mauro Paes CorreaUnclassifiedIPv620
AS24482SG.GSHostingIPv4 IPv610
AS198057Flooyd Telecom LTDAResidentialIPv43
AS200464PAULO HENRIQUE SILVA DE OLIVEIRAUnclassifiedIPv42

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-31 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.50M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.