asn.dev

Observed topology

AS29988 RCC-RDC-AS

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS29988: 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
AS6461Zayo BandwidthTransitIPv45,756
AS577Bell CanadaMobileIPv42,509
AS812Rogers Communications Canada Inc.MobileIPv4872
AS7788Magma Communications Ltd.UnclassifiedIPv4719
AS6327Shaw CommunicationsResidentialIPv4289
AS852TELUS Communications Inc.ResidentialIPv4287
AS6939Hurricane Electric LLCTransitIPv498
AS394256Tech Futures Interactive Inc.UnclassifiedIPv414

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS22297Jelecos LLCUnclassifiedIPv4300
AS4361IDT CorporationUnclassifiedIPv459

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv45,939
AS577Bell CanadaMobileIPv42,606
AS812Rogers Communications Canada Inc.MobileIPv4894
AS7788Magma Communications Ltd.UnclassifiedIPv4721
AS852TELUS Communications Inc.ResidentialIPv4504
AS6327Shaw CommunicationsResidentialIPv4462
AS22297Jelecos LLCUnclassifiedIPv4300
AS16583Care Factor Computer Services IncUnclassifiedIPv4293
AS6939Hurricane Electric LLCTransitIPv4107
AS4361IDT CorporationUnclassifiedIPv459

All 12 adjacent →

Provenance

Where this comes from

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