asn.dev

Observed topology

AS209854 CYBERZONEHUB

VPN RIPE

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS209854: 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
AS60068Datacamp LimitedHostingIPv4 IPv618,952
AS147049PacketHub S.A.UnclassifiedIPv4 IPv61,582
AS25369Hydra Communications LtdHostingIPv41,396
AS207137PacketHub S.A.VPNIPv4 IPv6773
AS9009M247 Europe SRLHostingIPv4 IPv6477
AS141039PacketHub S.A.UnclassifiedIPv4 IPv6315
AS136557Host Universal Pty LtdUnclassifiedIPv4295
AS174Cogent Communications, LLCTransitIPv4 IPv6221
AS6453TATA COMMUNICATIONS AMERICA INCTransitIPv4 IPv6178
AS9678HostingInside LTDHostingIPv4121

All 12 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS60068Datacamp LimitedHostingIPv4 IPv618,952
AS147049PacketHub S.A.UnclassifiedIPv4 IPv61,582
AS25369Hydra Communications LtdHostingIPv41,396
AS207137PacketHub S.A.VPNIPv4 IPv6773
AS9009M247 Europe SRLHostingIPv4 IPv6477
AS141039PacketHub S.A.UnclassifiedIPv4 IPv6315
AS136557Host Universal Pty LtdUnclassifiedIPv4295
AS174Cogent Communications, LLCTransitIPv4 IPv6221
AS6453TATA COMMUNICATIONS AMERICA INCTransitIPv4 IPv6178
AS9678HostingInside LTDHostingIPv4121

All 12 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.