Network · data from 2026-11-12
AS34358 Cyber_Folks-RO-DC_FLO Cyber_Folks SRL
Registry name: Cyber_Folks-RO-DC_FLO Cyber_Folks SRL, RO · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS34358, 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.
| 85.120.58.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 80.96.84.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 37.251.128.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 37.251.160.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 37.251.248.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 77.81.164.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 85.120.35.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.121.136.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 89.32.44.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 89.34.107.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.35.173.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.35.204.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.36.128.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 89.36.128.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.36.129.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.36.130.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.36.132.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 89.36.134.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.36.135.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.38.248.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.38.249.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.38.250.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 89.38.252.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 89.42.11.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.45.192.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 91.208.142.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.250.247.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.119.227.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.24.29.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.24.48.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 94.24.72.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 94.24.76.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 94.24.78.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.95.8.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 176.223.166.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.171.184.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.171.185.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.171.187.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.212.111.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.214.142.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.215.48.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 193.239.130.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 193.242.120.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.156.42.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.156.44.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 217.156.103.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 37.251.248.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.180.200.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 128.0.46.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 37.251.255.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
AS-SET
AS34358 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: none2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 85.120.58.0/23 | No ROA covers it. Add a ROA for AS34358, maxLength 23. |
| ROA: none | 80.96.84.0/24 | No ROA covers it. Add a ROA for AS34358, maxLength 24. |
Route objects not announced
Route objects with origin AS34358 whose prefix no peer sees AS34358 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 37.251.254.0/24 | RIPE | Valid |
| 86.105.192.0/24 | RIPE | Valid |
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.