asn.dev

Observed topology

AS14615 ROCK-HILL-TELEPHONE

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS14615: 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
AS2711Spirit CommunicationsUnclassifiedIPv4 IPv615,475
AS174Cogent Communications, LLCTransitIPv4 IPv68,620
AS3356Level 3 Parent, LLCTransitIPv4 IPv67,591
AS24482SG.GSHostingIPv4 IPv6353

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS394755City of Rock Hill SCUnclassifiedIPv4236
AS62850OnTrack Systems LLCUnclassifiedIPv4 IPv6206
AS46218Comporium, IncUnclassifiedIPv696
AS3060York Technical CollegeEducationIPv459
AS3955Compucom SystemsUnclassifiedIPv459
AS398053Comporium, IncUnclassifiedIPv459
AS22065LPL FinancialUnclassifiedIPv418
AS395178Red Ventures, LLCUnclassifiedIPv46
AS33401Central Piedmont Community CollegeUnclassifiedIPv42

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS2711Spirit CommunicationsUnclassifiedIPv4 IPv615,596
AS174Cogent Communications, LLCTransitIPv4 IPv68,991
AS3356Level 3 Parent, LLCTransitIPv4 IPv67,831
AS24482SG.GSHostingIPv4 IPv6362
AS394755City of Rock Hill SCUnclassifiedIPv4236
AS62850OnTrack Systems LLCUnclassifiedIPv4 IPv6206
AS46218Comporium, IncUnclassifiedIPv696
AS3060York Technical CollegeEducationIPv459
AS3955Compucom SystemsUnclassifiedIPv459
AS398053Comporium, IncUnclassifiedIPv459

All 13 adjacent →

Provenance

Where this comes from

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