Network · data from 2026-11-12
AS137120 Nas Internet Services
Registry name: NASNET-AS-IN - Nas Internet Services Private Limited, IN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS137120, 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.206.100.0/24 | No ROA | RIR databaseAPNIC | 672 100% |
| 103.206.102.0/24 | No ROA | RIR databaseAPNIC | 672 100% |
| 103.206.103.0/24 | No ROA | RIR databaseAPNIC | 672 100% |
| 202.9.120.0/24 | No ROA | RIR databaseAPNIC | 672 100% |
| 202.9.122.0/24 | No ROA | RIR databaseAPNIC | 672 100% |
| 202.9.123.0/24 | No ROA | RIR databaseAPNIC | 672 100% |
| 45.115.176.0/24 | No ROA | RIR databaseAPNIC | 671 100% |
| 14.102.189.0/24 | No ROA | RIR databaseAPNIC | 670 100% |
AS-SET
PeeringDB's irr_as_set for AS137120: AS137120:AS-NASNET. 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 (AS137120 isn't in the set, or no route object for AS137120 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 | AS137120 in it | Not covered |
|---|---|---|---|---|---|
| AS137120:AS-NASNET | APNIC | 35 | 3 | Yes | 0 |
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: none8
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.206.100.0/24 | No ROA covers it. Add a ROA for AS137120, maxLength 24. |
| ROA: none | 103.206.102.0/24 | No ROA covers it. Add a ROA for AS137120, maxLength 24. |
| ROA: none | 103.206.103.0/24 | No ROA covers it. Add a ROA for AS137120, maxLength 24. |
| ROA: none | 202.9.120.0/24 | No ROA covers it. Add a ROA for AS137120, maxLength 24. |
| ROA: none | 202.9.122.0/24 | No ROA covers it. Add a ROA for AS137120, maxLength 24. |
| ROA: none | 202.9.123.0/24 | No ROA covers it. Add a ROA for AS137120, maxLength 24. |
| ROA: none | 45.115.176.0/24 | No ROA covers it. Add a ROA for AS137120, maxLength 24. |
| ROA: none | 14.102.189.0/24 | No ROA covers it. Add a ROA for AS137120, maxLength 24. |
Route objects not announced
Route objects with origin AS137120 whose prefix no peer sees AS137120 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.87.47.0/24 | APNIC | No ROA |
| 103.119.167.0/24 | APNIC | Invalid: origin |
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.