Network · data from 2026-11-12
AS212147 Proactivity Group
Registry name: PGHK-AS Proactivity Group Limited, HK · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS212147, 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.
| 194.26.137.0/24 | No ROA | Other origin only | 2 0%low visibility |
| 195.43.134.0/24 | No ROA | None | 2 0%low visibility |
| 217.179.229.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.179.228.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.179.230.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2400:b3a0:e3::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2400:b3a0:e1::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:b3a0:e2::/48 | Valid | RIR databaseAPNIC | 635 100% |
AS-SET
AS212147's PeeringDB record names no 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 5 are in fix.csv.
- ROA: none2
- Route object: none2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 194.26.137.0/24 | No ROA covers it. Add a ROA for AS212147, maxLength 24. |
| Route object: none | 194.26.137.0/24 | Route objects for it name AS398343. Add a route object with origin AS212147 in the RIR database for the space. |
| ROA: none | 195.43.134.0/24 | No ROA covers it. Add a ROA for AS212147, maxLength 24. |
| Route object: none | 195.43.134.0/24 | No route object for it. Add a route object with origin AS212147 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS212147 whose prefix no peer sees AS212147 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2400:b3a0:e4::/48 | APNIC | 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.