Network · data from 2026-11-12
AS205620 UNICOM-AS Unicom-Telecom d.o.o.
Registry name: UNICOM-AS Unicom-Telecom d.o.o., RS · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS205620, 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.211.64.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 193.27.24.0/22 | No ROA | RIR databaseRIPE | 670 100% |
| 185.211.64.0/23 | No ROA | RIR databaseRIPE | 254 38% |
| 185.211.66.0/23 | No ROA | RIR databaseRIPE | 254 38% |
| 185.211.64.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.211.65.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.211.66.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 193.27.24.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 193.27.25.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 193.27.26.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 193.27.27.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.211.67.0/24 | Valid | RIR databaseRIPE | 666 99% |
AS-SET
AS205620 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: none4
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.211.64.0/22 | No ROA covers it. Add a ROA for AS205620, maxLength 22. |
| ROA: none | 193.27.24.0/22 | No ROA covers it. Add a ROA for AS205620, maxLength 22. |
| ROA: none | 185.211.64.0/23 | No ROA covers it. Add a ROA for AS205620, maxLength 23. |
| ROA: none | 185.211.66.0/23 | No ROA covers it. Add a ROA for AS205620, maxLength 23. |
Route objects not announced
Route objects with origin AS205620 whose prefix no peer sees AS205620 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 193.27.24.0/23 | RIPE | No ROA |
| 193.27.26.0/23 | RIPE | No ROA |
| 2a10:3fc0::/48 | 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.