asn.dev

Observed topology

AS30170 OPTICFUSION

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS30170: 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
AS6461Zayo BandwidthTransitIPv4 IPv6176
AS18530Isomedia, Inc.HostingIPv4 IPv634

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS33569ALLHOSTSHOP.COMHostingIPv4531
AS399310South Sound 911UnclassifiedIPv4228
AS53283Litware LLCUnclassifiedIPv4 IPv6208
AS393387Port of TacomaUnclassifiedIPv4118
AS397465Skynet BroadbandUnclassifiedIPv457
AS27225TrueBlue, Inc.UnclassifiedIPv440

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4 IPv61,269
AS33569ALLHOSTSHOP.COMHostingIPv4531
AS399310South Sound 911UnclassifiedIPv4228
AS53283Litware LLCUnclassifiedIPv4 IPv6208
AS18530Isomedia, Inc.HostingIPv4 IPv6207
AS393387Port of TacomaUnclassifiedIPv4118
AS397465Skynet BroadbandUnclassifiedIPv457
AS27225TrueBlue, Inc.UnclassifiedIPv440

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.