Network · data from 2026-11-19
AS154931 Novalink Networks Incorporated
Registry name: NNI-AS-AP - Novalink Networks Incorporated, PH · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS154931, things to look at first. Visibility = full-table peers that see it, of 672 (IPv4) and 633 (IPv6) on 75 collectors. Also as routes.csv.
| 163.52.211.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 163.52.210.0/23 | Valid | RIR databaseAPNIC | 654 97% |
| 163.52.210.0/24 | Valid | RIR databaseAPNIC | 652 97% |
AS-SET
PeeringDB's irr_as_set for AS154931: APNIC::AS154931:AS-PROVIDER. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS154931 isn't in the set, or no route object for AS154931 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS154931 in it | Not covered |
|---|---|---|---|---|---|
| APNIC::AS154931:AS-PROVIDER | APNIC | 1 | 1 | No | 3 |
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 2 are in fix.csv.
- AS-SET: own ASN1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| AS-SET: own ASN | APNIC::AS154931:AS-PROVIDER | AS154931 isn't in AS154931:AS-PROVIDER (APNIC) once expanded. Add AS154931 to it. |
Route objects not announced
Route objects with origin AS154931 whose prefix no peer sees AS154931 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2402:7760::/32 | APNIC | Valid |
Routes: the 08:00 UTC snapshots of 2026-11-19 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.