asn.dev

Observed topology

AS207137 PACKETHUBSA

VPN RIPE

Upstreams 17 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 18
Adjacent (IPv6) 16
Upstream graph Who carries AS207137, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS207137 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 17

Networks observed carrying traffic for AS207137: 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
AS1299Arelion Sweden ABTransitIPv4 IPv61,408
AS5405Inter.link GmbHUnclassifiedIPv4 IPv6552
AS3257GTT Communications Inc.TransitIPv4 IPv6427
AS6939Hurricane Electric LLCTransitIPv4 IPv6157
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6144
AS6461Zayo BandwidthTransitIPv4 IPv6114
AS44735Nova hfUnclassifiedIPv4 IPv6106
AS2914NTT America, Inc.TransitIPv4 IPv676
AS12578SIA TetResidentialIPv4 IPv676
AS56704Farice ehfUnclassifiedIPv4 IPv666

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS209854Cyberzone S.A.VPNIPv4 IPv6782
AS211192NetWave Inc.UnclassifiedIPv4545

Adjacency

Adjacent networks

All 19

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv62,038
AS209854Cyberzone S.A.VPNIPv4 IPv6782
AS5405Inter.link GmbHUnclassifiedIPv4 IPv6745
AS211192NetWave Inc.UnclassifiedIPv4545
AS3257GTT Communications Inc.TransitIPv4 IPv6491
AS44735Nova hfUnclassifiedIPv4 IPv6244
AS6461Zayo BandwidthTransitIPv4 IPv6222
AS6939Hurricane Electric LLCTransitIPv4 IPv6176
AS12578SIA TetResidentialIPv4 IPv6156
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6144

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.