Network · data from 2026-11-12
AS214454 PoloNetwork-Limited-AS PoloNetwork Limited
Registry name: PoloNetwork-Limited-AS PoloNetwork Limited, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS214454, 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.
| 2a12:e100:30::/44 | Valid | Other IRR onlyRADB | 636 100% |
| 2a14:7580:2100::/40 | Valid | RIR databaseRIPE | 636 100% |
| 2a14:7580:27a0::/44 | Valid | RIR databaseRIPE | 634 100% |
| 2a14:7580:2a30::/44 | Valid | RIR databaseRIPE | 634 100% |
| 2a14:7580:22f0::/44 | Valid | RIR databaseRIPE | 632 99% |
| 2a14:7580:2900::/40 | Valid | RIR databaseRIPE | 632 99% |
| 2a14:7580:2bf0::/44 | Valid | RIR databaseRIPE | 632 99% |
| 2a14:7580:2e00::/40 | Valid | RIR databaseRIPE | 632 99% |
| 2a14:7580:2ab0::/44 | Valid | RIR databaseRIPE | 631 99% |
| 2a14:7580:2b30::/44 | Valid | RIR databaseRIPE | 631 99% |
| 2a14:7580:2b70::/44 | Valid | RIR databaseRIPE | 631 99% |
| 2a14:7580:2000::/40 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS214454 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 3 are in fix.csv.
- Route object: RIR1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 2a12:e100:30::/44 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS214454 whose prefix no peer sees AS214454 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.49.61.0/24 | APNIC | Valid |
| 2a14:7580:2000::/36 | RADB | 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.