Network · data from 2026-11-12
AS147176 NZ Network Enterprise AS147176
Registry name: NNECL-AS-AP - NZ Network Enterprise Co., Ltd., TH · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS147176, 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.
| 45.195.152.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 154.83.25.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 45.201.27.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 102.129.138.0/24 | Valid | RIR databaseAFRINIC, RADB | 673 100% |
| 103.174.190.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.174.191.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 151.244.248.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 154.16.66.0/24 | Valid | RIR databaseAFRINIC, RADB | 673 100% |
| 154.16.156.0/24 | Valid | RIR databaseAFRINIC, RADB | 673 100% |
| 191.96.93.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 45.201.0.0/24 | Valid | RIR databaseAFRINIC, RADB | 672 100% |
| 45.201.9.0/24 | Valid | RIR databaseAFRINIC, RADB | 672 100% |
| 154.84.153.0/24 | Valid | RIR databaseAFRINIC, RADB | 672 100% |
| 154.197.69.0/24 | Valid | RIR databaseAFRINIC, RADB | 672 100% |
| 154.197.102.0/24 | Valid | RIR databaseAFRINIC, RADB | 672 100% |
| 154.197.116.0/24 | Valid | RIR databaseAFRINIC, RADB | 672 100% |
| 154.212.139.0/24 | Valid | RIR databaseAFRINIC, RADB | 672 100% |
| 154.215.14.0/24 | Valid | RIR databaseAFRINIC, RADB | 672 100% |
| 154.197.124.0/24 | Valid | RIR databaseAFRINIC, RADB | 670 100% |
| 2001:df7:d280::/48 | Valid | RIR databaseAPNIC | 632 99% |
| 2a13:9500:81::/48 | Valid | RIR databaseRIPE | 630 99% |
AS-SET
PeeringDB's irr_as_set for AS147176: APNIC::AS-NNECL-TH. 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 (AS147176 isn't in the set, or no route object for AS147176 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 | AS147176 in it | Not covered | |
|---|---|---|---|---|---|---|
| APNIC::AS-NNECL-TH | In no IRR database read today. | |||||
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: RIR3
- AS-SET: not found1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 45.195.152.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 154.83.25.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.201.27.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: not found | APNIC::AS-NNECL-TH | PeeringDB names APNIC::AS-NNECL-TH; no IRR database read has it. |
Route objects not announced
Route objects with origin AS147176 whose prefix no peer sees AS147176 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.201.1.0/24 | AFRINIC | Invalid: origin |
| 138.252.93.0/24 | APNIC | Valid |
| 154.16.55.0/24 | AFRINIC | Invalid: origin |
| 154.208.140.0/24 | AFRINIC | Invalid: origin |
| 2001:df6:3e40::/48 | APNIC | Valid |
| 2a13:9500:d4::/48 | RADB, 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.