Network · data from 2026-11-12
AS51525 ASITLTD Informacionnuye technologiyi Ltd
Registry name: ASITLTD Informacionnuye technologiyi Ltd, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS51525, 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.
| 91.219.48.0/22 | No ROA | RIR databaseRADB, RIPE | 673 100% |
| 91.196.84.0/22 | No ROA | RIR databaseRADB, RIPE | 672 100% |
| 91.196.86.0/23 | No ROA | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS51525 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 7 are in fix.csv.
- ROA: none3
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.219.48.0/22 | No ROA covers it. Add a ROA for AS51525, maxLength 22. |
| ROA: none | 91.196.84.0/22 | No ROA covers it. Add a ROA for AS51525, maxLength 22. |
| ROA: none | 91.196.86.0/23 | No ROA covers it. Add a ROA for AS51525, maxLength 23. |
Route objects not announced
Route objects with origin AS51525 whose prefix no peer sees AS51525 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.196.84.0/23 | RIPE | No ROA |
| 91.219.48.0/23 | RIPE | No ROA |
| 91.219.48.0/24 | RIPE | No ROA |
| 91.219.50.0/23 | 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.