Network · data from 2026-11-12
AS29649 Limes sp. z o.o.
Registry name: LIMES-AS Limes sp. z o.o., PL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS29649, 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.
| 89.206.0.0/18 | No ROA | RIR databaseRIPE | 673 100% |
| 188.252.0.0/17 | No ROA | RIR databaseRIPE | 673 100% |
| 193.107.212.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 193.110.228.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 195.64.150.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 2a03:9300::/32 | No ROA | RIR databaseRIPE | 636 100% |
| 185.162.96.0/22 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS29649's PeeringDB record names no 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 9 are in fix.csv.
- ROA: none6
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 89.206.0.0/18 | No ROA covers it. Add a ROA for AS29649, maxLength 18. |
| ROA: none | 188.252.0.0/17 | No ROA covers it. Add a ROA for AS29649, maxLength 17. |
| ROA: none | 193.107.212.0/22 | No ROA covers it. Add a ROA for AS29649, maxLength 22. |
| ROA: none | 193.110.228.0/22 | No ROA covers it. Add a ROA for AS29649, maxLength 22. |
| ROA: none | 195.64.150.0/23 | No ROA covers it. Add a ROA for AS29649, maxLength 23. |
| ROA: none | 2a03:9300::/32 | No ROA covers it. Add a ROA for AS29649, maxLength 32. |
Route objects not announced
Route objects with origin AS29649 whose prefix no peer sees AS29649 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 93.157.152.0/21 | RIPE | No ROA |
| 193.104.50.0/24 | RIPE | No ROA |
| 2a10:f781:10:b3a7::/64 | 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.