asn.dev

Observed topology

AS214707 RCELL

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS214707: 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
AS174Cogent Communications, LLCTransitIPv4 IPv61,195
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6867
AS200612Gulf Bridge International Inc.UnclassifiedIPv4 IPv6380
AS201996Sofia Connect EADUnclassifiedIPv4266
AS6939Hurricane Electric LLCTransitIPv440
AS24482SG.GSHostingIPv45
AS33891Core-Backbone GmbHHostingIPv45
AS37721Virtual Technologies & SolutionsResidentialIPv45
AS49673Truenetwork LLCUnclassifiedIPv45
AS50629LWLcom GmbHUnclassifiedIPv45

All 13 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv61,195
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6867
AS200612Gulf Bridge International Inc.UnclassifiedIPv4 IPv6380
AS201996Sofia Connect EADUnclassifiedIPv4266
AS6939Hurricane Electric LLCTransitIPv440
AS24482SG.GSHostingIPv45
AS33891Core-Backbone GmbHHostingIPv45
AS37721Virtual Technologies & SolutionsResidentialIPv45
AS49673Truenetwork LLCUnclassifiedIPv45
AS50629LWLcom GmbHUnclassifiedIPv45

All 13 adjacent →

Provenance

Where this comes from

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