asn.dev

Observed topology

AS31275 Samtelecom-AS LLC Telecom-Service

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS31275: 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 RostelecomResidentialIPv4 IPv61,947
AS31133PJSC MegaFonMobileIPv499
AS24482SG.GSHostingIPv4 IPv634
AS49673Truenetwork LLCUnclassifiedIPv433
AS25091IP-Max SAUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS205773LLC Telecom-ServiceUnclassifiedIPv635

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4 IPv61,980
AS31133PJSC MegaFonMobileIPv499
AS24482SG.GSHostingIPv4 IPv635
AS205773LLC Telecom-ServiceUnclassifiedIPv635
AS49673Truenetwork LLCUnclassifiedIPv433
AS25091IP-Max SAUnclassifiedIPv62

Provenance

Where this comes from

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