Network · data from 2026-11-12
AS43794 AS_AEMS Euronext Technologies SAS
Registry name: AS_AEMS Euronext Technologies SAS, FR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS43794, 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.
| 212.107.68.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 212.197.238.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 212.197.236.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 212.107.68.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 212.107.68.0/24 | No ROA | RIR databaseRIPE | 3 0%low visibility |
| 212.107.69.0/24 | No ROA | RIR databaseRIPE | 3 0%low visibility |
| 212.197.238.0/24 | No ROA | RIR databaseRIPE | 3 0%low visibility |
| 212.197.239.0/24 | No ROA | RIR databaseRIPE | 3 0%low visibility |
AS-SET
AS43794 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 21 are in fix.csv.
- ROA: none8
- Route object: not announced13
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 212.107.68.0/23 | No ROA covers it. Add a ROA for AS43794, maxLength 23. |
| ROA: none | 212.197.238.0/23 | No ROA covers it. Add a ROA for AS43794, maxLength 23. |
| ROA: none | 212.197.236.0/22 | No ROA covers it. Add a ROA for AS43794, maxLength 22. |
| ROA: none | 212.107.68.0/22 | No ROA covers it. Add a ROA for AS43794, maxLength 22. |
| ROA: none | 212.107.68.0/24 | No ROA covers it. Add a ROA for AS43794, maxLength 24. |
| ROA: none | 212.107.69.0/24 | No ROA covers it. Add a ROA for AS43794, maxLength 24. |
| ROA: none | 212.197.238.0/24 | No ROA covers it. Add a ROA for AS43794, maxLength 24. |
| ROA: none | 212.197.239.0/24 | No ROA covers it. Add a ROA for AS43794, maxLength 24. |
Route objects not announced
Route objects with origin AS43794 whose prefix no peer sees AS43794 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 156.48.52.0/23 | RIPE | No ROA |
| 156.48.52.0/24 | RIPE | No ROA |
| 156.48.53.0/24 | RIPE | No ROA |
| 156.48.54.0/23 | RIPE | No ROA |
| 156.48.54.0/24 | RIPE | No ROA |
| 156.48.55.0/24 | RIPE | No ROA |
| 156.48.56.0/23 | RIPE | No ROA |
| 156.48.56.0/24 | RIPE | No ROA |
| 156.48.57.0/24 | RIPE | No ROA |
| 212.197.236.0/23 | RIPE | No ROA |
| 212.197.236.0/24 | RIPE | No ROA |
| 212.197.237.0/24 | RIPE | No ROA |
| 213.90.198.0/24 | 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.