Network · data from 2026-11-12
AS41079 CF-GDA Cyber_Folks S.A.
Registry name: CF-GDA Cyber_Folks S.A., PL · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS41079, 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.
| 185.204.216.0/23 | Valid | Nonecovered by 185.204.216.0/22 | 672 100% |
| 185.204.218.0/23 | Valid | Nonecovered by 185.204.216.0/22 | 672 100% |
| 91.199.22.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.228.196.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 91.234.146.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.237.52.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.239.66.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 178.250.40.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 185.5.96.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.25.148.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.123.160.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.140.120.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.180.204.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.193.112.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.201.112.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.208.164.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.243.52.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 193.218.153.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.78.66.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 195.242.116.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 193.218.155.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.17.184.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 195.114.1.0/24 | Valid | RIR databaseRIPE | 660 98% |
| 193.218.154.0/24 | Valid | RIR databaseRIPE | 659 98% |
| 2a02:1778::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:1778:194::/48 | Valid | RIR databaseRIPE | 635 100% |
| 185.204.216.0/22 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS41079 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 27 are in fix.csv.
- Route object: none2
- Route object: not announced25
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.204.216.0/23 | No route object for it. A route object for 185.204.216.0/22 with origin AS41079 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41079 in the RIR database for the space. |
| Route object: none | 185.204.218.0/23 | No route object for it. A route object for 185.204.216.0/22 with origin AS41079 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41079 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS41079 whose prefix no peer sees AS41079 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 178.250.40.0/24 | RIPE | Valid |
| 178.250.41.0/24 | RIPE | Valid |
| 178.250.42.0/24 | RIPE | Valid |
| 178.250.43.0/24 | RIPE | Valid |
| 178.250.44.0/24 | RIPE | Valid |
| 178.250.45.0/24 | RIPE | Valid |
| 178.250.46.0/24 | RIPE | Valid |
| 178.250.47.0/24 | RIPE | Valid |
| 185.204.216.0/24 | RIPE | Valid |
| 185.204.217.0/24 | RIPE | Valid |
| 185.204.218.0/24 | RIPE | Valid |
| 185.204.219.0/24 | RIPE | Valid |
| 185.243.52.0/24 | RIPE | Valid |
| 185.243.53.0/24 | RIPE | Valid |
| 185.243.54.0/24 | RIPE | Valid |
| 185.243.55.0/24 | RIPE | Valid |
| 193.218.152.0/22 | RIPE | Valid |
| 193.218.152.0/24 | RIPE | Valid |
| 195.2.255.0/24 | RIPE | Invalid: origin |
| 195.114.0.0/23 | RIPE | Valid |
| 195.114.0.0/24 | RIPE | Valid |
| 195.242.116.0/24 | RIPE | Valid |
| 195.242.117.0/24 | RIPE | Valid |
| 2a02:1778::/32 | RIPE | Valid |
| 2a02:1778:195::/48 | RIPE | Invalid: maxLength |
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.