Network · data from 2026-11-12
AS200826 DAILY-SOL S.C DAILY SOLUTIONS S.R.L
Registry name: DAILY-SOL S.C DAILY SOLUTIONS S.R.L, RO · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS200826, 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.
| 91.231.7.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.238.186.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 91.240.149.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.240.150.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 91.247.240.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 178.157.78.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 2001:67c:2fb4::/48 | No ROA | RIR databaseRIPE | 335 53% |
| 91.234.241.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.234.242.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 2a03:8800:1::/48 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS200826 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: none7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.231.7.0/24 | No ROA covers it. Add a ROA for AS200826, maxLength 24. |
| ROA: none | 91.238.186.0/23 | No ROA covers it. Add a ROA for AS200826, maxLength 23. |
| ROA: none | 91.240.149.0/24 | No ROA covers it. Add a ROA for AS200826, maxLength 24. |
| ROA: none | 91.240.150.0/23 | No ROA covers it. Add a ROA for AS200826, maxLength 23. |
| ROA: none | 91.247.240.0/21 | No ROA covers it. Add a ROA for AS200826, maxLength 21. |
| ROA: none | 178.157.78.0/23 | No ROA covers it. Add a ROA for AS200826, maxLength 23. |
| ROA: none | 2001:67c:2fb4::/48 | No ROA covers it. Add a ROA for AS200826, maxLength 48. |
Route objects not announced
Every route object with origin AS200826 is announced.
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.