asn.dev

Observed topology

AS12167 LIGHTWAVE-DALLAS - LightWave Networks

Unclassified ARIN Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS12167: 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 IPv6154
AS6939Hurricane Electric LLCTransitIPv4 IPv6139
AS12042FidiumResidentialIPv459
AS6461Zayo BandwidthTransitIPv450
AS46450Pilot Fiber, Inc.ResidentialIPv4 IPv625
AS13649Flexential Colorado Corp.HostingIPv410
AS14907Wikimedia Foundation Inc.HostingIPv4 IPv63
AS971PureVoltage Hosting Inc.UnclassifiedIPv42
AS25091IP-Max SAUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS402084AES Services LLCUnclassifiedIPv4 IPv6102

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6225
AS1299Arelion Sweden ABTransitIPv4 IPv6166
AS402084AES Services LLCUnclassifiedIPv4 IPv6102
AS12042FidiumResidentialIPv459
AS6461Zayo BandwidthTransitIPv450
AS46450Pilot Fiber, Inc.ResidentialIPv4 IPv625
AS13649Flexential Colorado Corp.HostingIPv410
AS14907Wikimedia Foundation Inc.HostingIPv4 IPv65
AS971PureVoltage Hosting Inc.UnclassifiedIPv43
AS25091IP-Max SAUnclassifiedIPv62

Provenance

Where this comes from

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