asn.dev

Observed topology

AS53755 IOFLOOD

Hosting ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS53755: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv67,113
AS174Cogent Communications, LLCTransitIPv41,482
AS143151GSERVERS, LLCHostingIPv41,119
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4707
AS3257GTT Communications Inc.TransitIPv4 IPv6373
AS53767iCastCenterHostingIPv4167

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS402799WawaCloudUnclassifiedIPv4 IPv6361
AS399114HyonixHostingIPv4325
AS397966ReadyDedis, LLCUnclassifiedIPv465

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv67,710
AS174Cogent Communications, LLCTransitIPv41,526
AS143151GSERVERS, LLCHostingIPv41,130
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4770
AS3257GTT Communications Inc.TransitIPv4 IPv6398
AS402799WawaCloudUnclassifiedIPv4 IPv6361
AS399114HyonixHostingIPv4325
AS53767iCastCenterHostingIPv4178
AS397966ReadyDedis, LLCUnclassifiedIPv465

Provenance

Where this comes from

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