Network · data from 2026-11-12
AS205828 VAA-AS Vyshegorodtseva Alla Alekseevna
Registry name: VAA-AS Vyshegorodtseva Alla Alekseevna, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS205828, 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.
| 2a0d:b844::/32 | Invalid: origin | None | 2 0%low visibility |
| 2a12:6487::/32 | No ROA | None | 1 0%low visibility |
| 2a12:bc83::/32 | No ROA | None | 1 0%low visibility |
| 2a11:7d06::/32 | Valid | RIR databaseRIPE | 634 100% |
| 2a11:9641::/32 | Valid | RIR databaseRIPE | 634 100% |
| 2a11:bdc1::/32 | Valid | RIR databaseRIPE | 634 100% |
| 2a11:bdc2::/32 | Valid | RIR databaseRIPE | 634 100% |
| 2a12:e84::/32 | Valid | RIR databaseRIPE | 634 100% |
| 2a12:d804::/32 | Valid | RIR databaseRIPE | 634 100% |
| 2a12:f984::/32 | Valid | RIR databaseRIPE | 634 100% |
| 2a11:eac4::/32 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
AS205828 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 8 are in fix.csv.
- ROA: origin1
- ROA: none2
- Route object: none3
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2a0d:b844::/32 | ROAs covering it name AS34567, not AS205828. If AS205828 should announce it, add a ROA for AS205828. |
| Route object: none | 2a0d:b844::/32 | No route object for it. Add a route object with origin AS205828 in the RIR database for the space. |
| ROA: none | 2a12:6487::/32 | No ROA covers it. Add a ROA for AS205828, maxLength 32. |
| Route object: none | 2a12:6487::/32 | No route object for it. Add a route object with origin AS205828 in the RIR database for the space. |
| ROA: none | 2a12:bc83::/32 | No ROA covers it. Add a ROA for AS205828, maxLength 32. |
| Route object: none | 2a12:bc83::/32 | No route object for it. Add a route object with origin AS205828 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS205828 whose prefix no peer sees AS205828 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a11:b4c3::/32 | RIPE | No ROA |
| 2a12:cf85::/32 | 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.