asn.dev

Observed topology

AS1003 ANDREWNET - andrewnet

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS1003: 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 IPv6175
AS807FORK SYSTEMSUnclassifiedIPv4 IPv6131
AS13335Cloudflare, Inc.HostingIPv670
AS52025ParadoxNetworks LimitedUnclassifiedIPv447
AS137409GSL Networks Pty LTDUnclassifiedIPv633
AS12186GVVMEUnclassifiedIPv631
AS20473The Constant Company, LLCHostingIPv65
AS205794JINZE YANGUnclassifiedIPv65
AS34927iFog GmbHHostingIPv4 IPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS211562andrewnet llcUnclassifiedIPv6252
AS215207Henrik Van TassellUnclassifiedIPv6105
AS63477Coniferous Systems, LLCUnclassifiedIPv4 IPv693

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6566
AS211562andrewnet llcUnclassifiedIPv6252
AS807FORK SYSTEMSUnclassifiedIPv4 IPv6131
AS215207Henrik Van TassellUnclassifiedIPv6105
AS52025ParadoxNetworks LimitedUnclassifiedIPv4 IPv694
AS63477Coniferous Systems, LLCUnclassifiedIPv4 IPv693
AS13335Cloudflare, Inc.HostingIPv670
AS137409GSL Networks Pty LTDUnclassifiedIPv633
AS12186GVVMEUnclassifiedIPv631
AS34927iFog GmbHHostingIPv4 IPv616

All 12 adjacent →

Provenance

Where this comes from

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