Network · data from 2026-11-12
AS59187 NEEVCLOUD.COM
Registry name: NEEVAI-AS-IN - NEEVAI SUPERCLOUD PVT LTD, IN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS59187, 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.
| 154.221.35.0/24 | No ROA | Other origin onlycovered by 154.221.34.0/23 | 671 100% |
| 154.221.32.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 154.221.33.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 154.221.34.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 156.238.97.0/24 | No ROA | RIR databaseAFRINIC, RADB | 672 100% |
| 156.238.98.0/24 | No ROA | RIR databaseAFRINIC, RADB | 672 100% |
| 156.238.99.0/24 | No ROA | RIR databaseAFRINIC, RADB | 672 100% |
| 156.238.100.0/24 | No ROA | RIR databaseAFRINIC, RADB | 670 100% |
| 103.192.198.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.192.199.0/24 | Valid | RIR databaseAPNIC | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS59187: AS-NEEVCLOUD. 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 (AS59187 isn't in the set, or no route object for AS59187 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 | AS59187 in it | Not covered |
|---|---|---|---|---|---|
| AS-NEEVCLOUD | ARIN | 0 | 1 | No | 10 |
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 17 are in fix.csv.
- ROA: none8
- Route object: none1
- Route object: RIR3
- AS-SET: own ASN1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 154.221.35.0/24 | No ROA covers it. Add a ROA for AS59187, maxLength 24. |
| Route object: none | 154.221.35.0/24 | Route objects for it name AS132839, AS134548. A route object for 154.221.34.0/23 with origin AS59187 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59187 in the RIR database for the space. |
| ROA: none | 154.221.32.0/24 | No ROA covers it. Add a ROA for AS59187, maxLength 24. |
| Route object: RIR | 154.221.32.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 154.221.33.0/24 | No ROA covers it. Add a ROA for AS59187, maxLength 24. |
| Route object: RIR | 154.221.33.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 154.221.34.0/24 | No ROA covers it. Add a ROA for AS59187, maxLength 24. |
| Route object: RIR | 154.221.34.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 156.238.97.0/24 | No ROA covers it. Add a ROA for AS59187, maxLength 24. |
| ROA: none | 156.238.98.0/24 | No ROA covers it. Add a ROA for AS59187, maxLength 24. |
| ROA: none | 156.238.99.0/24 | No ROA covers it. Add a ROA for AS59187, maxLength 24. |
| ROA: none | 156.238.100.0/24 | No ROA covers it. Add a ROA for AS59187, maxLength 24. |
| AS-SET: own ASN | AS-NEEVCLOUD | AS59187 isn't in AS-NEEVCLOUD (ARIN) once expanded. Add AS59187 to it. |
Route objects not announced
Route objects with origin AS59187 whose prefix no peer sees AS59187 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.192.198.0/23 | APNIC | Valid |
| 154.221.32.0/22 | RADB | No ROA |
| 154.221.32.0/23 | RADB | No ROA |
| 154.221.34.0/23 | 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.