Network · data from 2026-11-12
AS44043 Cyber_Folks-RO-DC_CLJ Cyber_Folks SRL
Registry name: Cyber_Folks-RO-DC_CLJ Cyber_Folks SRL, RO · not in PeeringDB
53IPv4 routes
79.2% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
11No ROA
0 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS44043, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS44043, 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.
| 92.118.156.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 92.118.157.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 92.118.159.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 95.214.132.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 95.214.133.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 95.214.134.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 95.214.135.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.236.84.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.236.85.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.236.86.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.236.87.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 31.14.12.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.14.13.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.14.14.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.14.15.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.14.22.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.14.23.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 46.102.249.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.36.131.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.44.47.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.44.120.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.44.138.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.44.139.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.46.7.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.195.28.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.195.29.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.200.120.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 92.114.94.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 92.114.95.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.176.104.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.176.105.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.126.200.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.126.201.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.126.202.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.126.203.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.223.120.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 176.223.122.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 176.223.124.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 176.223.126.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.92.192.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.92.193.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.92.194.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.92.195.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.212.156.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.213.20.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 188.215.244.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 188.215.250.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 188.240.2.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 188.240.235.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.241.183.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.102.218.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 80.97.21.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 80.97.162.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS44043 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 11 are in fix.csv.
- ROA: none11
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 92.118.156.0/24 | No ROA covers it. Add a ROA for AS44043, maxLength 24. |
| ROA: none | 92.118.157.0/24 | No ROA covers it. Add a ROA for AS44043, maxLength 24. |
| ROA: none | 92.118.159.0/24 | No ROA covers it. Add a ROA for AS44043, maxLength 24. |
| ROA: none | 95.214.132.0/24 | No ROA covers it. Add a ROA for AS44043, maxLength 24. |
| ROA: none | 95.214.133.0/24 | No ROA covers it. Add a ROA for AS44043, maxLength 24. |
| ROA: none | 95.214.134.0/24 | No ROA covers it. Add a ROA for AS44043, maxLength 24. |
| ROA: none | 95.214.135.0/24 | No ROA covers it. Add a ROA for AS44043, maxLength 24. |
| ROA: none | 185.236.84.0/24 | No ROA covers it. Add a ROA for AS44043, maxLength 24. |
| ROA: none | 185.236.85.0/24 | No ROA covers it. Add a ROA for AS44043, maxLength 24. |
| ROA: none | 185.236.86.0/24 | No ROA covers it. Add a ROA for AS44043, maxLength 24. |
| ROA: none | 185.236.87.0/24 | No ROA covers it. Add a ROA for AS44043, maxLength 24. |
Route objects not announced
Every route object with origin AS44043 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.