asn.dev

Observed topology

AS36224 HCLTA94085

Unclassified ARIN

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

Transit

Upstream networks

All 27

Networks observed carrying traffic for AS36224: 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
AS702Verizon BusinessUnclassifiedIPv41,507
AS7018AT&T Enterprises, LLCResidentialIPv4819
AS2386AT&T Enterprises, LLCUnclassifiedIPv4708
AS701Verizon BusinessResidentialIPv4564
AS703Verizon BusinessUnclassifiedIPv4521
AS2856British Telecommunications LimitedResidentialIPv4236
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4186
AS25180Exponential-E Ltd.UnclassifiedIPv4116
AS30848UNIDATA S.p.A.UnclassifiedIPv4116
AS54004Cablevision Lightpath LLCUnclassifiedIPv4 IPv6110

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS24084PLOT NO: 3A, SECTOR 126, SEZ, NOIDAUnclassifiedIPv4420

Adjacency

Adjacent networks

All 29

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

ASNetworkTypeFamiliesPaths seen
AS702Verizon BusinessUnclassifiedIPv41,507
AS7018AT&T Enterprises, LLCResidentialIPv4819
AS703Verizon BusinessUnclassifiedIPv4729
AS2386AT&T Enterprises, LLCUnclassifiedIPv4708
AS701Verizon BusinessResidentialIPv4564
AS24084PLOT NO: 3A, SECTOR 126, SEZ, NOIDAUnclassifiedIPv4420
AS2856British Telecommunications LimitedResidentialIPv4236
AS4637Telstra GlobalUnclassifiedIPv4212
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4186
AS25180Exponential-E Ltd.UnclassifiedIPv4116

Provenance

Where this comes from

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