Network · data from 2026-11-12
AS29205 VERCOM VERCOM S.A.
Registry name: VERCOM VERCOM S.A., PL · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS29205, 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.100.228.0/22 | No ROA | None | 673 100% |
| 37.251.192.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 91.230.36.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.49.12.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.49.12.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.49.13.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.49.14.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.49.15.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.100.228.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.100.231.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.192.102.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.214.16.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 188.214.16.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.214.17.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.214.19.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.214.20.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.215.64.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.135.21.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.156.236.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 188.214.23.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS29205 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 20 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced18
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.100.228.0/22 | No ROA covers it. Add a ROA for AS29205, maxLength 22. |
| Route object: none | 185.100.228.0/22 | No route object for it. Add a route object with origin AS29205 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS29205 whose prefix no peer sees AS29205 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 37.251.192.0/24 | RIPE | Valid |
| 37.251.193.0/24 | RIPE | Valid |
| 37.251.194.0/24 | RIPE | Valid |
| 37.251.195.0/24 | RIPE | Valid |
| 37.251.196.0/24 | RIPE | Valid |
| 37.251.197.0/24 | RIPE | Valid |
| 37.251.198.0/24 | RIPE | Valid |
| 37.251.199.0/24 | RIPE | Valid |
| 45.156.236.0/22 | RIPE | Valid |
| 45.156.237.0/24 | RIPE | Valid |
| 45.156.238.0/24 | RIPE | Valid |
| 45.156.239.0/24 | RIPE | Valid |
| 91.230.36.0/24 | RIPE | Valid |
| 91.230.37.0/24 | RIPE | Valid |
| 188.214.18.0/24 | RIPE | Valid |
| 188.214.21.0/24 | RIPE | Valid |
| 188.214.22.0/24 | RIPE | Valid |
| 2a06:1980::/29 | RIPE | Valid |
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.