Observed topology

AS17310 BVU-2

Unclassified ARIN Cable/DSL/ISP

Upstreams 1 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS17310: 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
AS26479	Point Broadband Fiber Holding, LLC	Residential	IPv4	643

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS23453	NEW PEOPLES BANK, INC	Unclassified	IPv4	58
AS26111	Erwin Utilities	Unclassified	IPv4	58
AS32104	Wellmont Health System	Unclassified	IPv4	42
AS21654	Apogee Telecom Inc.	Unclassified	IPv4	16
AS33444	Tazewell County	Unclassified	IPv4	3

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS26479	Point Broadband Fiber Holding, LLC	Residential	IPv4	820
AS23453	NEW PEOPLES BANK, INC	Unclassified	IPv4	58
AS26111	Erwin Utilities	Unclassified	IPv4	58
AS32104	Wellmont Health System	Unclassified	IPv4	42
AS21654	Apogee Telecom Inc.	Unclassified	IPv4	16
AS33444	Tazewell County	Unclassified	IPv4	3

Provenance

Where this comes from

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