asn.dev

Observed topology

AS56864 WELLSERVER-AS

Unclassified RIPE

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS56864: 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
AS202984Chernyshov Aleksandr AleksandrovichUnclassifiedIPv4251
AS12389PJSC RostelecomResidentialIPv4224
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv689
AS29226JSC MastertelUnclassifiedIPv442
AS199599Telecom-Birzha, LLCUnclassifiedIPv438
AS50673Serverius Holding B.V.UnclassifiedIPv414
AS6939Hurricane Electric LLCTransitIPv613
AS9002RETN LimitedUnclassifiedIPv4 IPv68
AS24482SG.GSHostingIPv4 IPv68
AS37721Virtual Technologies & SolutionsResidentialIPv47

All 14 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS211624Tetron LTDUnclassifiedIPv463
AS211404Tetron LTDUnclassifiedIPv461

Adjacency

Adjacent networks

All 16

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

ASNetworkTypeFamiliesPaths seen
AS202984Chernyshov Aleksandr AleksandrovichUnclassifiedIPv4251
AS12389PJSC RostelecomResidentialIPv4224
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6125
AS29226JSC MastertelUnclassifiedIPv481
AS199599Telecom-Birzha, LLCUnclassifiedIPv473
AS211624Tetron LTDUnclassifiedIPv463
AS211404Tetron LTDUnclassifiedIPv461
AS6939Hurricane Electric LLCTransitIPv4 IPv621
AS50673Serverius Holding B.V.UnclassifiedIPv414
AS9002RETN LimitedUnclassifiedIPv4 IPv610

All 16 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-26 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.