asn.dev

Observed topology

AS33544 WILINE - WiLine Networks Inc.

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS33544: 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
AS174Cogent Communications, LLCTransitIPv4 IPv61,973
AS6461Zayo BandwidthTransitIPv4 IPv61,318
AS3356Level 3 Parent, LLCTransitIPv4 IPv6341
AS6939Hurricane Electric LLCTransitIPv4135

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS16920Wind River Systems, Inc.UnclassifiedIPv4 IPv6132
AS20144ICANNUnclassifiedIPv4 IPv689
AS22729Peterson Farms, Inc.UnclassifiedIPv662
AS27500ICANNUnclassifiedIPv4 IPv662
AS23154Sanmina-SCI CorporationUnclassifiedIPv459
AS40700WiLine Networks Inc.UnclassifiedIPv458
AS395377-Reserved AS-UnclassifiedIPv424

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv62,102
AS6461Zayo BandwidthTransitIPv4 IPv61,570
AS3356Level 3 Parent, LLCTransitIPv4 IPv6446
AS6939Hurricane Electric LLCTransitIPv4135
AS16920Wind River Systems, Inc.UnclassifiedIPv4 IPv6132
AS20144ICANNUnclassifiedIPv4 IPv689
AS22729Peterson Farms, Inc.UnclassifiedIPv662
AS27500ICANNUnclassifiedIPv4 IPv662
AS23154Sanmina-SCI CorporationUnclassifiedIPv459
AS40700WiLine Networks Inc.UnclassifiedIPv458

All 11 adjacent →

Provenance

Where this comes from

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