Observed topology

AS10279 WCCL-AS - West Carolina Communications, LLC

Residential ARIN

Upstreams 2 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS10279: 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
AS1299	Arelion Sweden AB	Transit	IPv4	3,947
AS174	Cogent Communications, LLC	Transit	IPv4	3,788

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS22237	Technology Solutions of SC Inc.	Unclassified	IPv4	266
AS32186	FUJIFILM Manufacturing USA, Inc	Unclassified	IPv4	62
AS402290	Anderson County	Unclassified	IPv4	59
AS30518	Self Regional Healthcare	Unclassified	IPv4	31
AS62652	Anderson University	Unclassified	IPv4	30

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS1299	Arelion Sweden AB	Transit	IPv4	4,226
AS174	Cogent Communications, LLC	Transit	IPv4	3,957
AS22237	Technology Solutions of SC Inc.	Unclassified	IPv4	266
AS32186	FUJIFILM Manufacturing USA, Inc	Unclassified	IPv4	62
AS402290	Anderson County	Unclassified	IPv4	59
AS30518	Self Regional Healthcare	Unclassified	IPv4	31
AS62652	Anderson University	Unclassified	IPv4	30

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.