Network · data from 2026-11-12
AS59771 RB RIYAD BANK
Registry name: RB RIYAD BANK, SA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS59771, 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.
| 2001:678:39c::/48 | Valid | Other origin only | 636 100% |
| 185.205.24.0/22 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 185.205.24.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 185.205.25.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 185.205.26.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 185.205.27.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.105.119.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 195.85.224.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 2a00:1560:d::/48 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
AS59771 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 1 are in fix.csv.
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2001:678:39c::/48 | Route objects for it name AS29684. Add a route object with origin AS59771 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS59771 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.