asn.dev

Observed topology

AS214173 Sever-Telecom-SPb Sever Telecom JSC

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS214173: 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
AS50509Transroute Telecom LTDUnclassifiedIPv4218
AS60139Sever Telecom JSCUnclassifiedIPv460
AS31133PJSC MegaFonMobileIPv427
AS24482SG.GSHostingIPv45
AS37721Virtual Technologies & SolutionsResidentialIPv45

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS60139Sever Telecom JSCUnclassifiedIPv4109

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS50509Transroute Telecom LTDUnclassifiedIPv4320
AS60139Sever Telecom JSCUnclassifiedIPv4169
AS31133PJSC MegaFonMobileIPv427
AS24482SG.GSHostingIPv46
AS37721Virtual Technologies & SolutionsResidentialIPv46
AS50629LWLcom GmbHUnclassifiedIPv42
AS8732JSC ComcorUnclassifiedIPv41
AS25091IP-Max SAUnclassifiedIPv41
AS34927iFog GmbHHostingIPv41

Provenance

Where this comes from

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