asn.dev

Observed topology

AS5537 JSC "RU-CENTER"

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS5537: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS48287JSC "RU-CENTER"HostingIPv41,207
AS39494JSC "RU-CENTER"HostingIPv4 IPv6158
AS43489JSC "RU-CENTER"UnclassifiedIPv4 IPv665

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS48287JSC "RU-CENTER"HostingIPv4 IPv62,129
AS12389PJSC RostelecomResidentialIPv4 IPv61,827
AS39561"Domain names registrar REG.RU", LtdUnclassifiedIPv4387
AS39494JSC "RU-CENTER"HostingIPv4 IPv6158
AS43489JSC "RU-CENTER"UnclassifiedIPv4 IPv665
AS59692IQWeb FZ-LLCUnclassifiedIPv452
AS29076Citytelecom LLCHostingIPv641
AS1299Arelion Sweden ABTransitIPv613

Provenance

Where this comes from

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