asn.dev

Observed topology

AS12033 ASN-AT-12033

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS12033: 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 IPv6380
AS1299Arelion Sweden ABTransitIPv4 IPv665
AS174Cogent Communications, LLCTransitIPv4 IPv637
AS34927iFog GmbHHostingIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS16856Blessing HospitalUnclassifiedIPv4126
AS36667Phibro Animal Health CorporationUnclassifiedIPv4 IPv699
AS62920Prairie Power, Inc.UnclassifiedIPv455
AS393892Mid Century CommunicationsUnclassifiedIPv414

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6605
AS16856Blessing HospitalUnclassifiedIPv4126
AS1299Arelion Sweden ABTransitIPv4 IPv6104
AS36667Phibro Animal Health CorporationUnclassifiedIPv4 IPv699
AS174Cogent Communications, LLCTransitIPv4 IPv668
AS62920Prairie Power, Inc.UnclassifiedIPv455
AS393892Mid Century CommunicationsUnclassifiedIPv416
AS34927iFog GmbHHostingIPv62

Provenance

Where this comes from

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