asn.dev

Observed topology

AS13692 DFN-ASN-1 - Douglas FastNet

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS13692: 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 IPv6969
AS20055Wholesail networks LLCResidentialIPv4 IPv6604
AS6939Hurricane Electric LLCTransitIPv4190

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS33509Cascade Access, LLCUnclassifiedIPv4189
AS14431Umpqua Community CollegeUnclassifiedIPv4112
AS401036Friendowment, LLCUnclassifiedIPv4 IPv680
AS62909FIRST COMMUNITY CREDIT UNIONUnclassifiedIPv420

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4 IPv61,179
AS20055Wholesail networks LLCResidentialIPv4 IPv6798
AS6939Hurricane Electric LLCTransitIPv4190
AS33509Cascade Access, LLCUnclassifiedIPv4189
AS14431Umpqua Community CollegeUnclassifiedIPv4112
AS401036Friendowment, LLCUnclassifiedIPv4 IPv680
AS62909FIRST COMMUNITY CREDIT UNIONUnclassifiedIPv420
AS36012HUNTER COMMUNICATIONSUnclassifiedIPv43

Provenance

Where this comes from

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