Network · data from 2026-11-12
AS207158 WORLDCDN Clouvider Limited
Registry name: WORLDCDN Clouvider Limited, GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS207158, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 143.14.192.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 178.83.200.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
AS-SET
AS207158 isn't in PeeringDB, where networks name their AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 6 are in fix.csv.
- ROA: origin2
- Route object: none2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 143.14.192.0/24 | ROAs covering it name AS834, not AS207158. If AS207158 should announce it, add a ROA for AS207158. |
| Route object: none | 143.14.192.0/24 | Route objects for it name AS834. Add a route object with origin AS207158 in the RIR database for the space. |
| ROA: origin | 178.83.200.0/24 | ROAs covering it name AS834, not AS207158. If AS207158 should announce it, add a ROA for AS207158. |
| Route object: none | 178.83.200.0/24 | Route objects for it name AS834. Add a route object with origin AS207158 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS207158 whose prefix no peer sees AS207158 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 31.6.33.0/24 | RADB | No ROA |
| 147.90.17.0/24 | RADB | No ROA |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.