Network · data from 2026-11-12
AS206818 zilean ZILEAN SOLUTIONS, SOCIEDAD LIMITADA
Registry name: zilean ZILEAN SOLUTIONS, SOCIEDAD LIMITADA, ES · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS206818, 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.
| 2a12:e8c0::/29 | No ROA | None | 630 99% |
| 5.59.112.0/22 | No ROA | RIR databaseRIPE | 670 100% |
| 5.59.192.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 91.216.210.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.158.126.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS206818 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 4 are in fix.csv.
- ROA: none3
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a12:e8c0::/29 | No ROA covers it. Add a ROA for AS206818, maxLength 29. |
| Route object: none | 2a12:e8c0::/29 | No route object for it. Add a route object with origin AS206818 in the RIR database for the space. |
| ROA: none | 5.59.112.0/22 | No ROA covers it. Add a ROA for AS206818, maxLength 22. |
| ROA: none | 5.59.192.0/24 | No ROA covers it. Add a ROA for AS206818, maxLength 24. |
Route objects not announced
Every route object with origin AS206818 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.