asn.dev

Observed topology

AS33920 AQL

Unclassified RIPE Enterprise

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

Transit

Upstream networks

All 22

Networks observed carrying traffic for AS33920: 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 IPv6107
AS2914NTT America, Inc.TransitIPv4 IPv684
AS6939Hurricane Electric LLCTransitIPv4 IPv676
AS174Cogent Communications, LLCTransitIPv4 IPv659
AS9002RETN LimitedUnclassifiedIPv4 IPv634
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv625
AS50304Blix Solutions ASUnclassifiedIPv416
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv69
AS24482SG.GSHostingIPv4 IPv69
AS29169GANDI SASHostingIPv4 IPv69

All 22 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS44504Andy DavidsonUnclassifiedIPv450

Adjacency

Adjacent networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6118
AS2914NTT America, Inc.TransitIPv4 IPv691
AS6939Hurricane Electric LLCTransitIPv4 IPv676
AS174Cogent Communications, LLCTransitIPv4 IPv670
AS44504Andy DavidsonUnclassifiedIPv450
AS9002RETN LimitedUnclassifiedIPv4 IPv638
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv628
AS50304Blix Solutions ASUnclassifiedIPv418
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv610
AS24482SG.GSHostingIPv4 IPv610

All 23 adjacent →

Provenance

Where this comes from

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