asn.dev

Observed topology

AS2722 C-LIGHT

Unclassified ARIN Educational/Research

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS2722: 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
AS2721CULR, LLCUnclassifiedIPv4 IPv6185
AS20115Charter Communications LLCResidentialIPv462
AS10490Georgia Institute of TechnologyEducationIPv4 IPv658
AS2711Spirit CommunicationsUnclassifiedIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS12148Clemson UniversityUnclassifiedIPv4 IPv6155
AS397680The School District of Pickens County, South CarolinaUnclassifiedIPv462
AS396213USC UpstateUnclassifiedIPv434
AS46924Bob Jones UniversityUnclassifiedIPv4 IPv617

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS2721CULR, LLCUnclassifiedIPv4 IPv6436
AS12148Clemson UniversityUnclassifiedIPv4 IPv6286
AS10490Georgia Institute of TechnologyEducationIPv4 IPv6271
AS20115Charter Communications LLCResidentialIPv462
AS397680The School District of Pickens County, South CarolinaUnclassifiedIPv462
AS396213USC UpstateUnclassifiedIPv434
AS46924Bob Jones UniversityUnclassifiedIPv4 IPv617
AS2711Spirit CommunicationsUnclassifiedIPv48

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.