Network · data from 2026-11-12
AS215929 datacampus Data Campus Limited
Registry name: datacampus Data Campus Limited, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS215929, 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.
| 92.118.36.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 2a14:981::/34 | No ROA | RIR databaseRIPE | 635 100% |
| 2a14:980:8000::/34 | No ROA | RIR databaseRIPE | 629 99% |
| 2a14:980::/34 | No ROA | RIR databaseRIPE | 2 0%low visibility |
| 62.164.177.0/24 | Valid | None | 673 100% |
| 45.142.195.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.24.211.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.13.212.0/24 | Valid | RIR databaseRIPE | 665 99% |
AS-SET
AS215929 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 7 are in fix.csv.
- ROA: none4
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 92.118.36.0/24 | No ROA covers it. Add a ROA for AS215929, maxLength 24. |
| ROA: none | 2a14:981::/34 | No ROA covers it. Add a ROA for AS215929, maxLength 34. |
| ROA: none | 2a14:980:8000::/34 | No ROA covers it. Add a ROA for AS215929, maxLength 34. |
| ROA: none | 2a14:980::/34 | No ROA covers it. Add a ROA for AS215929, maxLength 34. |
| Route object: none | 62.164.177.0/24 | No route object for it. Add a route object with origin AS215929 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS215929 whose prefix no peer sees AS215929 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a14:980:4000::/34 | RIPE | No ROA |
| 2a14:981:8000::/34 | RIPE | 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.