Network · data from 2026-11-12
AS205820 VDCBY-AS Unitary enterprise A1
Registry name: VDCBY-AS Unitary enterprise A1, BY · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS205820, 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.
| 185.183.120.0/24 | Valid | Nonecovered by 185.183.120.0/22 | 671 100% |
| 185.183.121.0/24 | Valid | Nonecovered by 185.183.120.0/22 | 671 100% |
| 46.53.196.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 46.53.209.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 128.140.254.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 178.163.224.0/19 | Valid | RIR databaseRIPE | 670 100% |
| 178.163.230.0/23 | Valid | RIR databaseRIPE | 670 100% |
| 185.183.120.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 185.204.116.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 2a0a:f241::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a0a:f240::/29 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS205820 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.
- Route object: none2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.183.120.0/24 | No route object for it. A route object for 185.183.120.0/22 with origin AS205820 covers it (filters allowing more-specifics accept it). Add a route object with origin AS205820 in the RIR database for the space. |
| Route object: none | 185.183.121.0/24 | No route object for it. A route object for 185.183.120.0/22 with origin AS205820 covers it (filters allowing more-specifics accept it). Add a route object with origin AS205820 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS205820 whose prefix no peer sees AS205820 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.204.116.0/24 | RIPE | Invalid: maxLength |
| 185.204.117.0/24 | RIPE | Invalid: maxLength |
| 185.204.118.0/24 | RIPE | Invalid: maxLength |
| 185.204.119.0/24 | RIPE | Invalid: maxLength |
| 2a07:f600:4010::/48 | RIPE | No ROA |
| 2a0a:f240::/48 | RIPE | Invalid: maxLength |
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.