Observed topology

AS18671 PRTC-SC

Unclassified ARIN

Upstreams 3 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS18671: 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
AS16863	Home Telephone Company, Inc.	Unclassified	IPv4	801
AS2711	Spirit Communications	Unclassified	IPv4	770
AS26744	Planters Communications, LLC	Unclassified	IPv4	478

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS14480	County of Orangeburg	Unclassified	IPv4	422
AS398766	TriCoLink, Inc.	Unclassified	IPv4	92
AS23087	Communications Data Group	Unclassified	IPv4	58

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS26744	Planters Communications, LLC	Unclassified	IPv4	987
AS2711	Spirit Communications	Unclassified	IPv4	839
AS16863	Home Telephone Company, Inc.	Unclassified	IPv4	822
AS14480	County of Orangeburg	Unclassified	IPv4	422
AS398766	TriCoLink, Inc.	Unclassified	IPv4	119
AS23087	Communications Data Group	Unclassified	IPv4	58

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.