Network · data from 2026-11-12
AS51653 PRESNET-AS PRESNET s.r.o.
Registry name: PRESNET-AS PRESNET s.r.o., SK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS51653, 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.
| 178.18.64.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 178.18.66.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 178.18.75.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 178.18.77.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.139.224.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 158.255.248.0/21 | No ROA | RIR databaseRIPE | 672 100% |
| 158.255.249.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 158.255.250.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 158.255.251.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 158.255.252.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 158.255.253.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 194.156.68.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 178.18.64.0/24 | No ROA | RIR databaseRIPE | 181 27% |
| 178.18.67.0/24 | No ROA | RIR databaseRIPE | 181 27% |
| 178.18.68.0/24 | No ROA | RIR databaseRIPE | 181 27% |
| 178.18.69.0/24 | No ROA | RIR databaseRIPE | 181 27% |
| 178.18.70.0/24 | No ROA | RIR databaseRIPE | 181 27% |
| 178.18.71.0/24 | No ROA | RIR databaseRIPE | 181 27% |
| 178.18.73.0/24 | No ROA | RIR databaseRIPE | 181 27% |
AS-SET
AS51653 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 25 are in fix.csv.
- ROA: none19
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 178.18.64.0/20 | No ROA covers it. Add a ROA for AS51653, maxLength 20. |
| ROA: none | 178.18.66.0/24 | No ROA covers it. Add a ROA for AS51653, maxLength 24. |
| ROA: none | 178.18.75.0/24 | No ROA covers it. Add a ROA for AS51653, maxLength 24. |
| ROA: none | 178.18.77.0/24 | No ROA covers it. Add a ROA for AS51653, maxLength 24. |
| ROA: none | 185.139.224.0/22 | No ROA covers it. Add a ROA for AS51653, maxLength 22. |
| ROA: none | 158.255.248.0/21 | No ROA covers it. Add a ROA for AS51653, maxLength 21. |
| ROA: none | 158.255.249.0/24 | No ROA covers it. Add a ROA for AS51653, maxLength 24. |
| ROA: none | 158.255.250.0/24 | No ROA covers it. Add a ROA for AS51653, maxLength 24. |
| ROA: none | 158.255.251.0/24 | No ROA covers it. Add a ROA for AS51653, maxLength 24. |
| ROA: none | 158.255.252.0/24 | No ROA covers it. Add a ROA for AS51653, maxLength 24. |
| ROA: none | 158.255.253.0/24 | No ROA covers it. Add a ROA for AS51653, maxLength 24. |
| ROA: none | 194.156.68.0/24 | No ROA covers it. Add a ROA for AS51653, maxLength 24. |
| ROA: none | 178.18.64.0/24 | No ROA covers it. Add a ROA for AS51653, maxLength 24. |
| ROA: none | 178.18.67.0/24 | No ROA covers it. Add a ROA for AS51653, maxLength 24. |
| ROA: none | 178.18.68.0/24 | No ROA covers it. Add a ROA for AS51653, maxLength 24. |
| ROA: none | 178.18.69.0/24 | No ROA covers it. Add a ROA for AS51653, maxLength 24. |
| ROA: none | 178.18.70.0/24 | No ROA covers it. Add a ROA for AS51653, maxLength 24. |
| ROA: none | 178.18.71.0/24 | No ROA covers it. Add a ROA for AS51653, maxLength 24. |
| ROA: none | 178.18.73.0/24 | No ROA covers it. Add a ROA for AS51653, maxLength 24. |
Route objects not announced
Route objects with origin AS51653 whose prefix no peer sees AS51653 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 158.255.248.0/24 | RIPE | No ROA |
| 158.255.254.0/24 | RIPE | No ROA |
| 158.255.255.0/24 | RIPE | No ROA |
| 178.18.78.0/24 | RIPE | No ROA |
| 195.62.16.0/23 | RIPE | No ROA |
| 195.62.17.0/24 | 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.