Observed topology

AS63457 EMPIRE-CONNECT - Liberty Connect

Unclassified ARIN NSP

Upstreams 3 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 0

Upstream graph Who carries AS63457, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS63457 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS63457: 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.

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4	1,166
AS3356	Level 3 Parent, LLC	Transit	IPv4	176
AS174	Cogent Communications, LLC	Transit	IPv4	110

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS29696	Carthage Water and Electric	Unclassified	IPv4	407
AS33136	Ozark Fiber, LLC	Unclassified	IPv4	330
AS46756	Freeman Health System	Unclassified	IPv4	74
AS35932	Splash Wireless Internet, LLC	Unclassified	IPv4	66
AS396915	Net Vision Communications, LLC	Unclassified	IPv4	65

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4	1,908
AS29696	Carthage Water and Electric	Unclassified	IPv4	407
AS33136	Ozark Fiber, LLC	Unclassified	IPv4	330
AS3356	Level 3 Parent, LLC	Transit	IPv4	300
AS174	Cogent Communications, LLC	Transit	IPv4	190
AS46756	Freeman Health System	Unclassified	IPv4	74
AS35932	Splash Wireless Internet, LLC	Unclassified	IPv4	66
AS396915	Net Vision Communications, LLC	Unclassified	IPv4	65
AS62943	Missouri Network Alliance, LLC	Unclassified	IPv4	4

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.