asn.dev

Observed topology

AS57814 Cloud9 Cloud 9 Ltd.

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS57814: 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
AS3223Voxility LLPHostingIPv4814
AS35805JSC "Silknet"UnclassifiedIPv4609
AS20771Caucasus Online Ltd.UnclassifiedIPv4 IPv6222
AS34797System Net LtdUnclassifiedIPv467
AS49628LLC SkytelUnclassifiedIPv456
AS16010Magticom Ltd.UnclassifiedIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS210850SysNet LLCUnclassifiedIPv4177
AS56966Foodservice LTDUnclassifiedIPv4131
AS211517LLC WildberriesUnclassifiedIPv4 IPv6123
AS201651Superbet 2014, LtdUnclassifiedIPv462
AS210580Internet Exchange Association of GeorgiaUnclassifiedIPv460
AS202223Odrex Software LLCUnclassifiedIPv452

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS3223Voxility LLPHostingIPv41,177
AS35805JSC "Silknet"UnclassifiedIPv4 IPv6794
AS20771Caucasus Online Ltd.UnclassifiedIPv4 IPv6307
AS210850SysNet LLCUnclassifiedIPv4177
AS56966Foodservice LTDUnclassifiedIPv4131
AS211517LLC WildberriesUnclassifiedIPv4 IPv6123
AS49628LLC SkytelUnclassifiedIPv473
AS34797System Net LtdUnclassifiedIPv469
AS201651Superbet 2014, LtdUnclassifiedIPv462
AS210580Internet Exchange Association of GeorgiaUnclassifiedIPv460

Provenance

Where this comes from

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