Network · data from 2026-11-12
AS20417 STABILISERVERS
Registry name: STABILISERVERS - StabiliServers, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS20417, 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.
| 38.135.34.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 2605:e480:11::/48 | No ROA | Other IRR onlyALTDB | 633 100% |
| 23.128.28.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 2602:f7d1::/48 | Valid | RIR databaseARIN | 634 100% |
AS-SET
AS20417's PeeringDB record names no 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 6 are in fix.csv.
- ROA: none2
- Route object: RIR2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.135.34.0/24 | No ROA covers it. Add a ROA for AS20417, maxLength 24. |
| Route object: RIR | 38.135.34.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2605:e480:11::/48 | No ROA covers it. Add a ROA for AS20417, maxLength 48. |
| Route object: RIR | 2605:e480:11::/48 | Route object only in ALTDB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS20417 whose prefix no peer sees AS20417 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 184.184.122.0/24 | RADB | Valid |
| 2602:f7d1::/40 | ARIN, RADB | 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.