Network · data from 2026-11-12
AS56710 MAXEN MAXEN TECHNOLOGIES S.L.
Registry name: MAXEN MAXEN TECHNOLOGIES S.L., ES · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS56710, 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.
| 178.237.144.0/20 | No ROA | RIR databaseRIPE | 669 99% |
AS-SET
AS56710 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 8 are in fix.csv.
- ROA: none1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 178.237.144.0/20 | No ROA covers it. Add a ROA for AS56710, maxLength 20. |
Route objects not announced
Route objects with origin AS56710 whose prefix no peer sees AS56710 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 178.237.144.0/21 | RIPE | No ROA |
| 178.237.144.0/22 | RIPE | No ROA |
| 178.237.148.0/24 | RIPE | No ROA |
| 178.237.149.0/24 | RIPE | No ROA |
| 178.237.150.0/23 | RIPE | No ROA |
| 178.237.152.0/22 | RIPE | No ROA |
| 178.237.156.0/22 | 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.