Network · data from 2026-11-12
AS142647 Nasstec Airnet
Registry name: NAN-AS-AP - Nasstec Airnet Networks Private Limited, PK · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS142647, 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.
| 103.66.149.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.149.32.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.186.76.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.186.77.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 151.158.47.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 160.30.142.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 165.101.118.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 165.101.119.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 45.115.42.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 45.115.43.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 103.149.33.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 103.173.7.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 103.66.148.0/24 | Valid | RIR databaseAPNIC | 667 99% |
| 2001:df6:9b40::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 151.158.46.0/24 | Valid | RIR databaseAPNIC | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS142647: AS142647:AS-PEERS. 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 (AS142647 isn't in the set, or no route object for AS142647 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 | AS142647 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS142647:AS-PEERS | 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 4 are in fix.csv.
- AS-SET: not found1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| AS-SET: not found | AS142647:AS-PEERS | PeeringDB names AS142647:AS-PEERS; no IRR database read has it. |
Route objects not announced
Route objects with origin AS142647 whose prefix no peer sees AS142647 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.173.6.0/24 | APNIC | Valid |
| 103.186.76.0/23 | RADB | No ROA |
| 160.30.143.0/24 | 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.