Network · data from 2026-11-12
AS44585 EFOR Efor Global Technology SL
Registry name: EFOR Efor Global Technology SL, ES · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS44585, 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.
| 93.92.232.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 93.92.232.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 93.92.233.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 93.92.234.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 93.92.234.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 93.92.235.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 46.30.16.0/21 | No ROA | RIR databaseRIPE | 672 100% |
| 93.92.236.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 93.92.236.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 93.92.237.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 93.92.238.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 93.92.239.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 93.92.232.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 185.63.28.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 195.55.174.0/24 | Valid | RIR databaseRIPE | 619 92% |
| 195.55.205.0/24 | Valid | RIR databaseRIPE | 619 92% |
AS-SET
AS44585 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 31 are in fix.csv.
- ROA: none14
- Route object: not announced17
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 93.92.232.0/23 | No ROA covers it. Add a ROA for AS44585, maxLength 23. |
| ROA: none | 93.92.232.0/24 | No ROA covers it. Add a ROA for AS44585, maxLength 24. |
| ROA: none | 93.92.233.0/24 | No ROA covers it. Add a ROA for AS44585, maxLength 24. |
| ROA: none | 93.92.234.0/23 | No ROA covers it. Add a ROA for AS44585, maxLength 23. |
| ROA: none | 93.92.234.0/24 | No ROA covers it. Add a ROA for AS44585, maxLength 24. |
| ROA: none | 93.92.235.0/24 | No ROA covers it. Add a ROA for AS44585, maxLength 24. |
| ROA: none | 46.30.16.0/21 | No ROA covers it. Add a ROA for AS44585, maxLength 21. |
| ROA: none | 93.92.236.0/22 | No ROA covers it. Add a ROA for AS44585, maxLength 22. |
| ROA: none | 93.92.236.0/24 | No ROA covers it. Add a ROA for AS44585, maxLength 24. |
| ROA: none | 93.92.237.0/24 | No ROA covers it. Add a ROA for AS44585, maxLength 24. |
| ROA: none | 93.92.238.0/24 | No ROA covers it. Add a ROA for AS44585, maxLength 24. |
| ROA: none | 93.92.239.0/24 | No ROA covers it. Add a ROA for AS44585, maxLength 24. |
| ROA: none | 93.92.232.0/22 | No ROA covers it. Add a ROA for AS44585, maxLength 22. |
| ROA: none | 185.63.28.0/22 | No ROA covers it. Add a ROA for AS44585, maxLength 22. |
Route objects not announced
Route objects with origin AS44585 whose prefix no peer sees AS44585 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 46.30.16.0/22 | RIPE | No ROA |
| 46.30.16.0/23 | RIPE | No ROA |
| 46.30.16.0/24 | RIPE | No ROA |
| 46.30.17.0/24 | RIPE | No ROA |
| 46.30.18.0/23 | RIPE | No ROA |
| 46.30.18.0/24 | RIPE | No ROA |
| 46.30.19.0/24 | RIPE | No ROA |
| 46.30.20.0/22 | RIPE | No ROA |
| 46.30.20.0/23 | RIPE | No ROA |
| 46.30.20.0/24 | RIPE | No ROA |
| 46.30.21.0/24 | RIPE | No ROA |
| 46.30.22.0/23 | RIPE | No ROA |
| 46.30.22.0/24 | RIPE | No ROA |
| 46.30.23.0/24 | RIPE | No ROA |
| 93.92.232.0/21 | RIPE | No ROA |
| 93.92.236.0/23 | RIPE | No ROA |
| 93.92.238.0/23 | RIPE | No ROA |
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.