Observed topology

AS22646 HARCOM1 - Hargray Communications Group, Inc.

Residential ARIN Cable/DSL/ISP

Upstreams 1 carry this network

Downstreams 7 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS22646: 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
AS11492	CABLE ONE, INC.	Residential	IPv4	26,840

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS400511	Clearwave Communications	Unclassified	IPv4	288
AS23418	The Darien Telephone Co. Inc.	Unclassified	IPv4	134
AS395206	Rotary Corporation	Unclassified	IPv4	57
AS14505	ISLC, Inc.	Unclassified	IPv4	49
AS399877	Sea Pines Resort, LLC	Unclassified	IPv4	34
AS397460	Beaufort County Government	Unclassified	IPv4	5
AS397392	BJWSA	Unclassified	IPv4	4

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS11492	CABLE ONE, INC.	Residential	IPv4	27,411
AS400511	Clearwave Communications	Unclassified	IPv4	288
AS23418	The Darien Telephone Co. Inc.	Unclassified	IPv4	134
AS395206	Rotary Corporation	Unclassified	IPv4	57
AS14505	ISLC, Inc.	Unclassified	IPv4	49
AS399877	Sea Pines Resort, LLC	Unclassified	IPv4	34
AS397460	Beaufort County Government	Unclassified	IPv4	5
AS397392	BJWSA	Unclassified	IPv4	4

Provenance

Where this comes from

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