Observed topology
AS212378 AS212378 7b0e5f3b-e21d-4182-9744-576bbfbbf0b8
Hosting RIPE Network Services
Transit
Upstream networks
Networks observed carrying traffic for AS212378: 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 |
|---|---|---|---|---|
| AS34927 | iFog GmbH | Hosting | IPv4 IPv6 | 88 |
| AS20473 | The Constant Company, LLC | Hosting | IPv4 IPv6 | 61 |
| AS53356 | Free Range Cloud Hosting Inc. | Hosting | IPv4 IPv6 | 35 |
| AS835 | GoCodeIT Inc | Unclassified | IPv4 IPv6 | 15 |
| AS152900 | Onidel Pty Ltd | Unclassified | IPv4 | 2 |
| AS263702 | GRUPO ZGH SPA | Hosting | IPv4 | 1 |
| AS400212 | VergeTel Group LLC | Unclassified | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS212378 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
Every AS seen directly next to AS212378 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS34927 | iFog GmbH | Hosting | IPv4 IPv6 | 88 |
| AS20473 | The Constant Company, LLC | Hosting | IPv4 IPv6 | 61 |
| AS53356 | Free Range Cloud Hosting Inc. | Hosting | IPv4 IPv6 | 35 |
| AS835 | GoCodeIT Inc | Unclassified | IPv4 IPv6 | 15 |
| AS152900 | Onidel Pty Ltd | Unclassified | IPv4 | 2 |
| AS263702 | GRUPO ZGH SPA | Hosting | IPv4 | 1 |
| AS400212 | VergeTel Group LLC | Unclassified | IPv4 | 1 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-01 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.48M 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.