asn.dev

Observed topology

AS13781 ENERGYNET - Hopkinsville Electric System

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS13781: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv61,062
AS1299Arelion Sweden ABTransitIPv4138
AS6461Zayo BandwidthTransitIPv4 IPv690
AS3356Level 3 Parent, LLCTransitIPv438
AS40749CLARKSVILLE DEPARTMENT OF ELECTRICITYUnclassifiedIPv45

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS31867Schwartz Networks Limited Liability CompanyUnclassifiedIPv4 IPv61,072
AS14749Russellville Electric Plant BoardUnclassifiedIPv4 IPv673
AS401325Logan Aluminum Inc.UnclassifiedIPv414

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,974
AS31867Schwartz Networks Limited Liability CompanyUnclassifiedIPv4 IPv61,107
AS1299Arelion Sweden ABTransitIPv4 IPv6273
AS6461Zayo BandwidthTransitIPv4 IPv6162
AS3356Level 3 Parent, LLCTransitIPv4 IPv6101
AS14749Russellville Electric Plant BoardUnclassifiedIPv4 IPv673
AS40749CLARKSVILLE DEPARTMENT OF ELECTRICITYUnclassifiedIPv417
AS401325Logan Aluminum Inc.UnclassifiedIPv414

Provenance

Where this comes from

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