asn.dev

Observed topology

AS27400 CLEARFLY

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS27400: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6182
AS1299Arelion Sweden ABTransitIPv4 IPv6157
AS13335Cloudflare, Inc.HostingIPv4102
AS9002RETN LimitedUnclassifiedIPv4 IPv619
AS6939Hurricane Electric LLCTransitIPv612
AS24482SG.GSHostingIPv4 IPv69
AS3130RGnet OUUnclassifiedIPv48
AS34927iFog GmbHHostingIPv48
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv67
AS293ESnetUnclassifiedIPv46

All 11 upstreams →

Transit

Downstream networks

inferred

Networks for which AS27400 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 11

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6182
AS1299Arelion Sweden ABTransitIPv4 IPv6157
AS13335Cloudflare, Inc.HostingIPv4102
AS9002RETN LimitedUnclassifiedIPv4 IPv619
AS6939Hurricane Electric LLCTransitIPv612
AS24482SG.GSHostingIPv4 IPv69
AS3130RGnet OUUnclassifiedIPv48
AS34927iFog GmbHHostingIPv48
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv67
AS293ESnetUnclassifiedIPv46

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