Network · data from 2026-11-12
AS61221 IVALUA NET
Registry name: IVALUA-AS IVALUA SAS, FR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61221, 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.
| 5.252.144.0/23 | Valid | Nonecovered by 5.252.144.0/22 | 673 100% |
| 5.252.146.0/23 | Valid | Nonecovered by 5.252.144.0/22 | 673 100% |
| 185.14.244.0/23 | Valid | Nonecovered by 185.14.244.0/22 | 673 100% |
| 5.252.144.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.252.145.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.252.146.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.252.147.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.14.244.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.14.245.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.14.246.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.14.246.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.14.247.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS61221's PeeringDB record names no 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 14 are in fix.csv.
- Route object: none3
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 5.252.144.0/23 | No route object for it. A route object for 5.252.144.0/22 with origin AS61221 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61221 in the RIR database for the space. |
| Route object: none | 5.252.146.0/23 | No route object for it. A route object for 5.252.144.0/22 with origin AS61221 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61221 in the RIR database for the space. |
| Route object: none | 185.14.244.0/23 | No route object for it. A route object for 185.14.244.0/22 with origin AS61221 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61221 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS61221 whose prefix no peer sees AS61221 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.252.144.0/22 | RIPE | No ROA |
| 185.14.244.0/22 | RIPE | No ROA |
| 2a03:b840::/32 | RIPE | No ROA |
| 2a03:b840:2::/48 | RIPE | Valid |
| 2a03:b840:3::/48 | RIPE | Valid |
| 2a03:b840:3:1::/64 | RIPE | Valid |
| 2a03:b840:12::/48 | RIPE | Valid |
| 2a03:b840:13::/48 | RIPE | Valid |
| 2a03:b840:100::/48 | RIPE | Valid |
| 2a03:b840:101::/56 | RIPE | No ROA |
| 2a03:b840:102::/48 | 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.