Network · data from 2026-11-12
AS203695 ISP-AS Saypudinov Ayatula
Registry name: ISP-AS Saypudinov Ayatula, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS203695, 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.
| 46.8.240.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 188.130.175.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 46.8.240.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 46.8.243.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 46.8.245.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 46.8.246.0/24 | No ROA | RIR databaseRIPE | 672 100% |
AS-SET
AS203695 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 10 are in fix.csv.
- ROA: none6
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 46.8.240.0/21 | No ROA covers it. Add a ROA for AS203695, maxLength 21. |
| ROA: none | 188.130.175.0/24 | No ROA covers it. Add a ROA for AS203695, maxLength 24. |
| ROA: none | 46.8.240.0/24 | No ROA covers it. Add a ROA for AS203695, maxLength 24. |
| ROA: none | 46.8.243.0/24 | No ROA covers it. Add a ROA for AS203695, maxLength 24. |
| ROA: none | 46.8.245.0/24 | No ROA covers it. Add a ROA for AS203695, maxLength 24. |
| ROA: none | 46.8.246.0/24 | No ROA covers it. Add a ROA for AS203695, maxLength 24. |
Route objects not announced
Route objects with origin AS203695 whose prefix no peer sees AS203695 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 46.8.241.0/24 | RIPE | No ROA |
| 46.8.242.0/24 | RIPE | No ROA |
| 46.8.244.0/24 | RIPE | No ROA |
| 46.8.247.0/24 | RIPE | 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.