Network · data from 2026-11-12
AS22937 SHELDON-AS-1 - ACT USA
Registry name: SHELDON-AS-1 - ACT USA, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS22937, 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.
| 74.121.0.0/21 | No ROA | RIR databaseALTDB, ARIN, NTTCOM | 671 100% |
| 74.121.4.0/22 | No ROA | RIR databaseALTDB, ARIN, NTTCOM | 671 100% |
| 208.83.96.0/21 | No ROA | RIR databaseALTDB, ARIN, NTTCOM | 671 100% |
| 208.83.98.0/23 | No ROA | RIR databaseALTDB, ARIN, NTTCOM | 671 100% |
| 2607:ff38::/32 | No ROA | RIR databaseALTDB, ARIN, NTTCOM | 635 100% |
| 2607:ff38::/48 | No ROA | RIR databaseALTDB, ARIN, NTTCOM | 635 100% |
| 2607:ff38:3::/48 | No ROA | RIR databaseALTDB, ARIN, NTTCOM | 635 100% |
AS-SET
AS22937 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 35 are in fix.csv.
- ROA: none7
- Route object: not announced28
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 74.121.0.0/21 | No ROA covers it. Add a ROA for AS22937, maxLength 21. |
| ROA: none | 74.121.4.0/22 | No ROA covers it. Add a ROA for AS22937, maxLength 22. |
| ROA: none | 208.83.96.0/21 | No ROA covers it. Add a ROA for AS22937, maxLength 21. |
| ROA: none | 208.83.98.0/23 | No ROA covers it. Add a ROA for AS22937, maxLength 23. |
| ROA: none | 2607:ff38::/32 | No ROA covers it. Add a ROA for AS22937, maxLength 32. |
| ROA: none | 2607:ff38::/48 | No ROA covers it. Add a ROA for AS22937, maxLength 48. |
| ROA: none | 2607:ff38:3::/48 | No ROA covers it. Add a ROA for AS22937, maxLength 48. |
Route objects not announced
Route objects with origin AS22937 whose prefix no peer sees AS22937 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 74.121.0.0/22 | ALTDB, ARIN, NTTCOM | No ROA |
| 74.121.0.0/23 | ALTDB, ARIN, NTTCOM | No ROA |
| 74.121.0.0/24 | ALTDB, ARIN, NTTCOM | No ROA |
| 74.121.1.0/24 | ALTDB, ARIN, NTTCOM | No ROA |
| 74.121.2.0/23 | ALTDB, ARIN, NTTCOM | No ROA |
| 74.121.2.0/24 | ALTDB, ARIN, NTTCOM | No ROA |
| 74.121.3.0/24 | ALTDB, ARIN, NTTCOM | No ROA |
| 74.121.4.0/23 | ALTDB, ARIN, NTTCOM | No ROA |
| 74.121.4.0/24 | ALTDB, ARIN, NTTCOM | No ROA |
| 74.121.5.0/24 | ALTDB, ARIN, NTTCOM | No ROA |
| 74.121.6.0/23 | ALTDB, ARIN, NTTCOM | No ROA |
| 74.121.6.0/24 | ALTDB, ARIN, NTTCOM | No ROA |
| 74.121.7.0/24 | ALTDB, ARIN, NTTCOM | No ROA |
| 208.83.96.0/22 | ALTDB, ARIN, NTTCOM | No ROA |
| 208.83.96.0/23 | ALTDB, ARIN, NTTCOM | No ROA |
| 208.83.96.0/24 | ALTDB, ARIN, NTTCOM | No ROA |
| 208.83.97.0/24 | ALTDB, ARIN, NTTCOM | No ROA |
| 208.83.98.0/24 | ALTDB, NTTCOM | No ROA |
| 208.83.99.0/24 | ALTDB, ARIN, NTTCOM | No ROA |
| 208.83.100.0/22 | ALTDB, ARIN, NTTCOM | No ROA |
| 208.83.100.0/23 | ALTDB, ARIN, NTTCOM | No ROA |
| 208.83.100.0/24 | ALTDB, ARIN, NTTCOM | No ROA |
| 208.83.101.0/24 | ALTDB, ARIN, NTTCOM | No ROA |
| 208.83.102.0/23 | ALTDB, ARIN, NTTCOM | No ROA |
| 208.83.102.0/24 | ALTDB, ARIN, NTTCOM | No ROA |
| 208.83.103.0/24 | ALTDB, ARIN, NTTCOM | No ROA |
| 2607:ff38:1::/48 | ALTDB, ARIN, NTTCOM | No ROA |
| 2607:ff38:2::/48 | ALTDB, ARIN, NTTCOM | 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.