Network · data from 2026-11-12
AS34859 ZYNLINE-AS ZYN LINE LLC
Registry name: ZYNLINE-AS ZYN LINE LLC, UA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS34859, 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.184.228.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.184.229.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.184.230.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 212.46.54.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 217.28.131.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 94.137.93.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS34859 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 5 are in fix.csv.
- ROA: none5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.184.228.0/24 | No ROA covers it. Add a ROA for AS34859, maxLength 24. |
| ROA: none | 91.184.229.0/24 | No ROA covers it. Add a ROA for AS34859, maxLength 24. |
| ROA: none | 91.184.230.0/23 | No ROA covers it. Add a ROA for AS34859, maxLength 23. |
| ROA: none | 212.46.54.0/24 | No ROA covers it. Add a ROA for AS34859, maxLength 24. |
| ROA: none | 217.28.131.0/24 | No ROA covers it. Add a ROA for AS34859, maxLength 24. |
Route objects not announced
Every route object with origin AS34859 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.