Network · data from 2026-11-12
AS26716 NETCRACKER - NetCracker Technology, Corporation
Registry name: NETCRACKER - NetCracker Technology, Corporation, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS26716, 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.
| 162.248.80.0/24 | No ROA | Other IRR onlyALTDB | 673 100% |
| 162.248.81.0/24 | No ROA | Other IRR onlyALTDB | 673 100% |
| 162.248.82.0/24 | No ROA | Other IRR onlyALTDB | 673 100% |
| 162.255.141.0/24 | No ROA | Other IRR onlyALTDB, RIPE-NONAUTH | 672 100% |
| 135.84.44.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 162.255.140.0/24 | No ROA | RIR databaseALTDB, ARIN | 673 100% |
| 198.49.86.0/24 | No ROA | RIR databaseARIN, RADB | 673 100% |
| 162.255.142.0/24 | No ROA | RIR databaseALTDB, ARIN, RIPE-NONAUTH | 671 100% |
| 2620:aa:4000::/48 | No ROA | RIR databaseARIN | 635 100% |
AS-SET
AS26716 isn't in PeeringDB, where networks name their AS-SET.
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: none9
- Route object: RIR4
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 162.248.80.0/24 | No ROA covers it. Add a ROA for AS26716, maxLength 24. |
| Route object: RIR | 162.248.80.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 162.248.81.0/24 | No ROA covers it. Add a ROA for AS26716, maxLength 24. |
| Route object: RIR | 162.248.81.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 162.248.82.0/24 | No ROA covers it. Add a ROA for AS26716, maxLength 24. |
| Route object: RIR | 162.248.82.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 162.255.141.0/24 | No ROA covers it. Add a ROA for AS26716, maxLength 24. |
| Route object: RIR | 162.255.141.0/24 | Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 135.84.44.0/24 | No ROA covers it. Add a ROA for AS26716, maxLength 24. |
| ROA: none | 162.255.140.0/24 | No ROA covers it. Add a ROA for AS26716, maxLength 24. |
| ROA: none | 198.49.86.0/24 | No ROA covers it. Add a ROA for AS26716, maxLength 24. |
| ROA: none | 162.255.142.0/24 | No ROA covers it. Add a ROA for AS26716, maxLength 24. |
| ROA: none | 2620:aa:4000::/48 | No ROA covers it. Add a ROA for AS26716, maxLength 48. |
Route objects not announced
Route objects with origin AS26716 whose prefix no peer sees AS26716 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 63.116.6.0/24 | RADB | No ROA |
| 162.248.80.0/22 | RADB | No ROA |
| 162.255.140.0/22 | RADB | No ROA |
| 162.255.175.0/24 | RIPE-NONAUTH | 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.