Observed topology
AS212321 PCALACARTE
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS212321: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 93 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 49 |
| AS9002 | RETN Limited | Unclassified | IPv6 | 6 |
| AS6696 | VERIXI SA | Unclassified | IPv4 IPv6 | 4 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 4 |
| AS50628 | Leonix Telecom SAS | Unclassified | IPv4 IPv6 | 4 |
| AS25091 | IP-Max SA | Unclassified | IPv6 | 3 |
| AS12779 | IT.Gate S.p.A. | Unclassified | IPv4 | 1 |
| AS20766 | Association "Gitoyen" | Unclassified | IPv4 | 1 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS212321 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS218696 | ERIC HOFFMANN | Unclassified | IPv6 | 36 |
Adjacency
Adjacent networks
Every AS seen directly next to AS212321 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 122 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 52 |
| AS218696 | ERIC HOFFMANN | Unclassified | IPv6 | 36 |
| AS9002 | RETN Limited | Unclassified | IPv6 | 7 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 5 |
| AS50628 | Leonix Telecom SAS | Unclassified | IPv4 IPv6 | 5 |
| AS6696 | VERIXI SA | Unclassified | IPv4 IPv6 | 4 |
| AS25091 | IP-Max SA | Unclassified | IPv6 | 4 |
| AS12779 | IT.Gate S.p.A. | Unclassified | IPv4 | 1 |
| AS20766 | Association "Gitoyen" | Unclassified | IPv4 | 1 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-21 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.