asn.dev

Observed topology

AS33164 AS-IRISTEL

Unclassified ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS33164: 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
AS13335Cloudflare, Inc.HostingIPv4643
AS1299Arelion Sweden ABTransitIPv4278
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4147
AS3257GTT Communications Inc.TransitIPv460
AS174Cogent Communications, LLCTransitIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS54191Ice Wireless Inc.UnclassifiedIPv4236
AS4877ADYA INC.UnclassifiedIPv459
AS401500Karrier One Inc.UnclassifiedIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS13335Cloudflare, Inc.HostingIPv4643
AS1299Arelion Sweden ABTransitIPv4632
AS54191Ice Wireless Inc.UnclassifiedIPv4236
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4147
AS3257GTT Communications Inc.TransitIPv460
AS4877ADYA INC.UnclassifiedIPv459
AS401500Karrier One Inc.UnclassifiedIPv459
AS174Cogent Communications, LLCTransitIPv41

Provenance

Where this comes from

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