Network · data from 2026-11-12
AS219100 OPENADS-LIMITED OPENADS LIMITED
Registry name: OPENADS-LIMITED OPENADS LIMITED, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS219100, 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.
| 2a04:8cc0::/29 | Valid | None | 634 100% |
| 2a0d:36c0::/29 | Valid | None | 634 100% |
| 2a14:1bc0::/29 | Valid | None | 632 99% |
| 2a14:1d40::/29 | Valid | Other origin only | 632 99% |
AS-SET
AS219100 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 10 are in fix.csv.
- Route object: none4
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2a04:8cc0::/29 | No route object for it. Add a route object with origin AS219100 in the RIR database for the space. |
| Route object: none | 2a0d:36c0::/29 | No route object for it. Add a route object with origin AS219100 in the RIR database for the space. |
| Route object: none | 2a14:1bc0::/29 | No route object for it. Add a route object with origin AS219100 in the RIR database for the space. |
| Route object: none | 2a14:1d40::/29 | Route objects for it name AS212027. Add a route object with origin AS219100 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS219100 whose prefix no peer sees AS219100 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a0b:9800::/29 | RIPE | Valid |
| 2a0b:a280::/29 | RIPE | Valid |
| 2a0f:1180::/29 | RIPE | Valid |
| 2a0f:2380::/29 | RIPE | Valid |
| 2a0f:4680::/29 | RIPE | Valid |
| 2a0f:9fc0::/29 | RIPE | Valid |
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.