Network · data from 2026-11-12
AS136049 FILAPAC-AS-AP - FIL Asia Holdings Pte Limited
Registry name: FILAPAC-AS-AP - FIL Asia Holdings Pte Limited, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS136049, 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.
| 192.223.128.0/24 | No ROA | RIR databaseARIN, RADB | 673 100% |
| 103.80.220.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 103.80.221.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
AS-SET
AS136049 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.
- ROA: none1
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 192.223.128.0/24 | No ROA covers it. Add a ROA for AS136049, maxLength 24. |
Route objects not announced
Route objects with origin AS136049 whose prefix no peer sees AS136049 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.223.129.0/24 | ARIN | No ROA |
| 192.223.144.0/24 | ARIN, RADB | No ROA |
| 192.223.146.0/24 | ARIN | No ROA |
| 192.223.155.0/24 | ARIN | No ROA |
| 2001:df7:1600::/48 | RADB | No ROA |
| 2001:df7:1600:1::/64 | RADB | No ROA |
| 2001:df7:1600:2::/64 | RADB | No ROA |
| 2401:a6c0:1::/48 | APNIC, RADB | No ROA |
| 2401:a6c0:2::/48 | APNIC, 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.