asn.dev

Observed topology

AS30286 THM

Unclassified ARIN Enterprise

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

Transit

Upstream networks

All 19

Networks observed carrying traffic for AS30286: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6603
AS2914NTT America, Inc.TransitIPv4 IPv6369
AS6939Hurricane Electric LLCTransitIPv4 IPv684
AS44735Nova hfUnclassifiedIPv4 IPv649
AS20562Broadband Hosting B.V.HostingIPv426
AS3356Level 3 Parent, LLCTransitIPv4 IPv615
AS24482SG.GSHostingIPv4 IPv67
AS14907Wikimedia Foundation Inc.HostingIPv4 IPv64
AS971PureVoltage Hosting Inc.UnclassifiedIPv43
AS2497Internet Initiative Japan Inc.UnclassifiedIPv42

All 19 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 19

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6603
AS2914NTT America, Inc.TransitIPv4 IPv6369
AS6939Hurricane Electric LLCTransitIPv4 IPv684
AS44735Nova hfUnclassifiedIPv4 IPv649
AS20562Broadband Hosting B.V.HostingIPv426
AS3356Level 3 Parent, LLCTransitIPv4 IPv615
AS24482SG.GSHostingIPv4 IPv67
AS14907Wikimedia Foundation Inc.HostingIPv4 IPv64
AS971PureVoltage Hosting Inc.UnclassifiedIPv43
AS2497Internet Initiative Japan Inc.UnclassifiedIPv42

All 19 adjacent →

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.