asn.dev

Observed topology

AS48287 RU-CENTER

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS48287: 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
AS201706SERVICEPIPE LLCUnclassifiedIPv41,197
AS5537JSC "RU-CENTER"HostingIPv41,154
AS199599Telecom-Birzha, LLCUnclassifiedIPv4126
AS24482SG.GSHostingIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS39494JSC "RU-CENTER"HostingIPv4 IPv61,502
AS199472Foundation for Assistance for Internet Technologies and Infrastructure DevelopmentUnclassifiedIPv4310
AS43489JSC "RU-CENTER"UnclassifiedIPv4 IPv6112
AS42399JSC "RU-CENTER"UnclassifiedIPv492
AS60216Foundation for Assistance for Internet Technologies and Infrastructure DevelopmentUnclassifiedIPv420

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS201706SERVICEPIPE LLCUnclassifiedIPv42,233
AS5537JSC "RU-CENTER"HostingIPv4 IPv62,027
AS39494JSC "RU-CENTER"HostingIPv4 IPv61,502
AS199599Telecom-Birzha, LLCUnclassifiedIPv4 IPv6363
AS199472Foundation for Assistance for Internet Technologies and Infrastructure DevelopmentUnclassifiedIPv4310
AS43489JSC "RU-CENTER"UnclassifiedIPv4 IPv6112
AS42399JSC "RU-CENTER"UnclassifiedIPv492
AS44112SpaceWeb LtdUnclassifiedIPv462
AS47595JSC "RU-CENTER"UnclassifiedIPv452
AS6939Hurricane Electric LLCTransitIPv424

All 14 adjacent →

Provenance

Where this comes from

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