Network · data from 2026-11-12
AS23531 SUNRISE-BANKS - Sunrise Banks
Registry name: SUNRISE-BANKS - Sunrise Banks, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS23531, 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.
| 50.227.234.0/24 | Invalid: maxLength | None | 27 4%low visibility |
| 205.142.66.0/23 | No ROA | Other IRR onlyRADB | 673 100% |
| 50.227.234.0/23 | Valid | None | 2 0%low visibility |
AS-SET
AS23531 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 5 are in fix.csv.
- ROA: maxLength1
- ROA: none1
- Route object: none2
- Route object: RIR1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 50.227.234.0/24 | ROA 50.227.234.0/23 AS23531 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 50.227.234.0/24. |
| Route object: none | 50.227.234.0/24 | No route object for it. Add a route object with origin AS23531 in the RIR database for the space. |
| ROA: none | 205.142.66.0/23 | No ROA covers it. Add a ROA for AS23531, maxLength 23. |
| Route object: RIR | 205.142.66.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 50.227.234.0/23 | No route object for it. Add a route object with origin AS23531 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS23531 is announced.
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.