asn.dev

Observed topology

AS2906 AS-SSI

Hosting ARIN

Upstreams 95 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 87
Adjacent (IPv6) 63
Upstream graph Who carries AS2906, and who carries them, drawn as a map up to the transit-free core. 93 exchanges Where AS2906 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 95

Networks observed carrying traffic for AS2906: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv65,043
AS6939Hurricane Electric LLCTransitIPv4 IPv62,734
AS1299Arelion Sweden ABTransitIPv4 IPv6459
AS9002RETN LimitedUnclassifiedIPv4 IPv6410
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6354
AS24482SG.GSHostingIPv4 IPv6332
AS3320Deutsche Telekom AGMobileIPv4 IPv6296
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6293
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6289
AS7018AT&T Enterprises, LLCResidentialIPv4 IPv6211

All 95 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS40027Netflix Streaming Services Inc.UnclassifiedIPv4 IPv61,600

Adjacency

Adjacent networks

All 96

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv65,382
AS6939Hurricane Electric LLCTransitIPv4 IPv62,918
AS40027Netflix Streaming Services Inc.UnclassifiedIPv4 IPv61,600
AS1299Arelion Sweden ABTransitIPv4 IPv6471
AS9002RETN LimitedUnclassifiedIPv4 IPv6422
AS24482SG.GSHostingIPv4 IPv6368
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6354
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6349
AS3320Deutsche Telekom AGMobileIPv4 IPv6308
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6293

All 96 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.22M 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.