asn.dev

Observed topology

AS12958 MCC T2 Mobile LLC

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS12958: 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
AS12389PJSC RostelecomResidentialIPv4832
AS3216PJSC "Vimpelcom"MobileIPv4379
AS50673Serverius Holding B.V.UnclassifiedIPv444
AS24482SG.GSHostingIPv422
AS37721Virtual Technologies & SolutionsResidentialIPv422
AS49673Truenetwork LLCUnclassifiedIPv422
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv422
AS50384iHome LLCUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS34287T2 Mobile LLCUnclassifiedIPv4110

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4832
AS3216PJSC "Vimpelcom"MobileIPv4379
AS34287T2 Mobile LLCUnclassifiedIPv4110
AS6939Hurricane Electric LLCTransitIPv455
AS50673Serverius Holding B.V.UnclassifiedIPv449
AS24482SG.GSHostingIPv427
AS37721Virtual Technologies & SolutionsResidentialIPv427
AS49673Truenetwork LLCUnclassifiedIPv427
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv427
AS50384iHome LLCUnclassifiedIPv46

All 15 adjacent →

Provenance

Where this comes from

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