Observed topology
AS198831 HOLYCLOUD HOLYCLOUD
Hosting RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS198831: 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.
Transit
Downstream networks
Networks for which AS198831 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS213535 | YottaSrc | Hosting | IPv4 IPv6 | 1,005 |
| AS210699 | WEDEPLOY SAS | Hosting | IPv4 IPv6 | 331 |
| AS216075 | Association ZENYX | Unclassified | IPv4 IPv6 | 154 |
| AS200489 | Arkya Networks SAS | Unclassified | IPv4 IPv6 | 131 |
| AS207449 | LEBREUILLY Jeremy trading as Hostinity | Unclassified | IPv4 IPv6 | 130 |
| AS207300 | Stephane Blondeau | Unclassified | IPv4 IPv6 | 122 |
| AS216147 | Association FreshPerf | Unclassified | IPv4 IPv6 | 97 |
| AS215784 | luc ruiz trading as ONEHEBERGE | Unclassified | IPv4 IPv6 | 96 |
| AS200063 | Tanguy DELMER | Unclassified | IPv4 IPv6 | 94 |
| AS207708 | Benjamin ELIAS | Unclassified | IPv4 IPv6 | 94 |
Adjacency
Adjacent networks
Every AS seen directly next to AS198831 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS399486 | 12651980 CANADA INC. | Hosting | IPv4 IPv6 | 4,597 |
| AS213535 | YottaSrc | Hosting | IPv4 IPv6 | 1,005 |
| AS62000 | SERVERD SAS | Hosting | IPv4 IPv6 | 823 |
| AS210699 | WEDEPLOY SAS | Hosting | IPv4 IPv6 | 331 |
| AS203446 | SMARTNET Germany GmbH | Unclassified | IPv4 IPv6 | 277 |
| AS216075 | Association ZENYX | Unclassified | IPv4 IPv6 | 154 |
| AS200489 | Arkya Networks SAS | Unclassified | IPv4 IPv6 | 131 |
| AS207449 | LEBREUILLY Jeremy trading as Hostinity | Unclassified | IPv4 IPv6 | 130 |
| AS207300 | Stephane Blondeau | Unclassified | IPv4 IPv6 | 122 |
| AS216147 | Association FreshPerf | Unclassified | IPv4 IPv6 | 97 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-30 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.49M 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.