Observed topology

AS11976 FIDN - Fidelity Communication International Inc.

Residential ARIN

Upstreams 1 carry this network

Downstreams 7 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS11976: 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	23,942

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS399417	VortexOK.net LLC	Unclassified	IPv4	72
AS17286	Phelps County Regional Medical Center	Unclassified	IPv4	59
AS398902	Cass Regional Medical Center	Unclassified	IPv4	58
AS401521	Gray Media, Inc.	Unclassified	IPv4	55
AS5638	Brewer Science	Unclassified	IPv4	5
AS398162	Panola College	Unclassified	IPv4	2
AS27465	Net Vision Communications, LLC	Unclassified	IPv4	1

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS11492	CABLE ONE, INC.	Residential	IPv4	24,194
AS399417	VortexOK.net LLC	Unclassified	IPv4	72
AS17286	Phelps County Regional Medical Center	Unclassified	IPv4	59
AS398902	Cass Regional Medical Center	Unclassified	IPv4	58
AS401521	Gray Media, Inc.	Unclassified	IPv4	55
AS5638	Brewer Science	Unclassified	IPv4	5
AS398162	Panola College	Unclassified	IPv4	2
AS27465	Net Vision Communications, LLC	Unclassified	IPv4	1

Provenance

Where this comes from

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