asn.dev

Observed topology

AS3801 MISNET

Hosting ARIN NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS3801: 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 IPv61,552
AS2914NTT America, Inc.TransitIPv4 IPv61,190
AS6939Hurricane Electric LLCTransitIPv4 IPv6620
AS19108OptimumUnclassifiedIPv4 IPv6337
AS30600MetronetResidentialIPv4 IPv6200

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS36610East Kentucky Network, LLC.UnclassifiedIPv4234
AS395024Pikeville Medical CenterUnclassifiedIPv456
AS400633Peoples Rural Telephone Cooperative Corporation, Inc.UnclassifiedIPv456
AS53848Mountain TelephoneUnclassifiedIPv420

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4 IPv61,711
AS2914NTT America, Inc.TransitIPv4 IPv61,314
AS6939Hurricane Electric LLCTransitIPv4 IPv6628
AS19108OptimumUnclassifiedIPv4 IPv6403
AS36610East Kentucky Network, LLC.UnclassifiedIPv4234
AS30600MetronetResidentialIPv4 IPv6209
AS395024Pikeville Medical CenterUnclassifiedIPv456
AS400633Peoples Rural Telephone Cooperative Corporation, Inc.UnclassifiedIPv456
AS53848Mountain TelephoneUnclassifiedIPv420

Provenance

Where this comes from

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