asn.dev

Observed topology

AS23248 PPS - Paducah Power System

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS23248: 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 LLCTransitIPv4100
AS393444AccelecomUnclassifiedIPv636
AS6461Zayo BandwidthTransitIPv432

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS47095Murray Electric SystemUnclassifiedIPv4819
AS1818DIALOG TELECOMMUNICATIONS, INC.UnclassifiedIPv4483
AS22002Systems Solutions of Paducah, Inc.UnclassifiedIPv4294
AS1246Zito MediaUnclassifiedIPv4264
AS14760Murray State UniversityUnclassifiedIPv4162
AS11970e-Tel, LLCUnclassifiedIPv466
AS27197Princeton Electric Plant BoardUnclassifiedIPv466
AS31850Mission Conversion Services Alliance, LLCUnclassifiedIPv452
AS1360Mayfield Electric & Water SystemsUnclassifiedIPv432

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv42,139
AS47095Murray Electric SystemUnclassifiedIPv4819
AS1818DIALOG TELECOMMUNICATIONS, INC.UnclassifiedIPv4483
AS6461Zayo BandwidthTransitIPv4408
AS22002Systems Solutions of Paducah, Inc.UnclassifiedIPv4375
AS1246Zito MediaUnclassifiedIPv4264
AS14760Murray State UniversityUnclassifiedIPv4162
AS27197Princeton Electric Plant BoardUnclassifiedIPv4132
AS11970e-Tel, LLCUnclassifiedIPv4130
AS393444AccelecomUnclassifiedIPv4 IPv670

Provenance

Where this comes from

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