asn.dev

Observed topology

AS48031 XServerCloud Ivanov Vitaliy Sergeevich

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS48031: 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
AS9002RETN LimitedUnclassifiedIPv4 IPv619,191
AS5405Inter.link GmbHUnclassifiedIPv4 IPv610,055
AS8772Netassist International EOODUnclassifiedIPv4 IPv62,600
AS29632Netassist International EOODUnclassifiedIPv4 IPv61,164
AS3255LLC EKSINTECHUnclassifiedIPv4 IPv6383

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS136258BrainStorm Network, IncUnclassifiedIPv4 IPv6194

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9002RETN LimitedUnclassifiedIPv4 IPv619,214
AS5405Inter.link GmbHUnclassifiedIPv4 IPv610,123
AS8772Netassist International EOODUnclassifiedIPv4 IPv62,619
AS29632Netassist International EOODUnclassifiedIPv4 IPv61,171
AS3255LLC EKSINTECHUnclassifiedIPv4 IPv6460
AS136258BrainStorm Network, IncUnclassifiedIPv4 IPv6194

Provenance

Where this comes from

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