asn.dev

Observed topology

AS33044 MEGAWIRE

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS33044: 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
AS7311Frontier Networks IncUnclassifiedIPv4258
AS174Cogent Communications, LLCTransitIPv4108
AS6939Hurricane Electric LLCTransitIPv631
AS22652Videotron LteeResidentialIPv4 IPv614
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv68
AS24482SG.GSHostingIPv4 IPv67
AS1403EBOXResidentialIPv62
AS20473The Constant Company, LLCHostingIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS46641Niagara Catholic District School BoardUnclassifiedIPv482
AS4508NeuStyleUnclassifiedIPv471

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS7311Frontier Networks IncUnclassifiedIPv4329
AS174Cogent Communications, LLCTransitIPv4177
AS46641Niagara Catholic District School BoardUnclassifiedIPv482
AS4508NeuStyleUnclassifiedIPv471
AS6939Hurricane Electric LLCTransitIPv4 IPv641
AS22652Videotron LteeResidentialIPv4 IPv616
AS24482SG.GSHostingIPv4 IPv68
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv68
AS1403EBOXResidentialIPv62
AS20473The Constant Company, LLCHostingIPv61

Provenance

Where this comes from

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