Network · data from 2026-11-12
AS20900 InterMeDiaSud
Registry name: AS-IMSNETORKS IMS Networks SAS, FR · PeeringDB
29IPv4 routes
72.4% RPKI valid · 55.2% with a route object
1IPv6 routes
100.0% RPKI valid · 0.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
8No ROA
14 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
15Route objects not announced
registered with origin AS20900, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS20900, 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.
| 137.129.9.0/24 | No ROA | Nonecovered by 137.129.0.0/16 | 670 100% |
| 137.129.15.0/24 | No ROA | Nonecovered by 137.129.0.0/16 | 670 100% |
| 137.129.43.0/24 | No ROA | Nonecovered by 137.129.0.0/16 | 670 100% |
| 137.129.63.0/24 | No ROA | Nonecovered by 137.129.0.0/16 | 670 100% |
| 137.129.232.0/23 | No ROA | Nonecovered by 137.129.0.0/16 | 670 100% |
| 137.129.234.0/23 | No ROA | Nonecovered by 137.129.0.0/16 | 670 100% |
| 137.129.236.0/23 | No ROA | Nonecovered by 137.129.0.0/16 | 670 100% |
| 137.129.0.0/16 | No ROA | RIR databaseRIPE | 670 100% |
| 91.214.114.0/23 | Valid | None | 673 100% |
| 185.182.252.0/24 | Valid | Nonecovered by 185.182.252.0/22 | 673 100% |
| 213.190.88.0/24 | Valid | Nonecovered by 213.190.64.0/19 | 673 100% |
| 78.159.132.0/23 | Valid | Nonecovered by 78.159.132.0/22 | 670 100% |
| 78.159.134.0/23 | Valid | Nonecovered by 78.159.132.0/22 | 670 100% |
| 213.190.69.0/24 | Valid | Nonecovered by 213.190.64.0/19 | 670 100% |
| 2001:1b08::/32 | Valid | None | 605 95% |
| 31.217.232.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 31.217.233.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.231.175.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.182.252.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 194.4.7.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.4.13.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.190.64.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 213.190.64.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.190.65.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.11.208.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 78.159.132.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 176.111.246.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 194.4.10.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 194.4.12.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 213.190.76.0/24 | Valid | RIR databaseRIPE | 670 100% |
AS-SET
AS20900'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 37 are in fix.csv.
- ROA: none8
- Route object: none14
- Route object: not announced15
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 137.129.9.0/24 | No ROA covers it. Add a ROA for AS20900, maxLength 24. |
| Route object: none | 137.129.9.0/24 | No route object for it. A route object for 137.129.0.0/16 with origin AS20900 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20900 in the RIR database for the space. |
| ROA: none | 137.129.15.0/24 | No ROA covers it. Add a ROA for AS20900, maxLength 24. |
| Route object: none | 137.129.15.0/24 | No route object for it. A route object for 137.129.0.0/16 with origin AS20900 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20900 in the RIR database for the space. |
| ROA: none | 137.129.43.0/24 | No ROA covers it. Add a ROA for AS20900, maxLength 24. |
| Route object: none | 137.129.43.0/24 | No route object for it. A route object for 137.129.0.0/16 with origin AS20900 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20900 in the RIR database for the space. |
| ROA: none | 137.129.63.0/24 | No ROA covers it. Add a ROA for AS20900, maxLength 24. |
| Route object: none | 137.129.63.0/24 | No route object for it. A route object for 137.129.0.0/16 with origin AS20900 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20900 in the RIR database for the space. |
| ROA: none | 137.129.232.0/23 | No ROA covers it. Add a ROA for AS20900, maxLength 23. |
| Route object: none | 137.129.232.0/23 | No route object for it. A route object for 137.129.0.0/16 with origin AS20900 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20900 in the RIR database for the space. |
| ROA: none | 137.129.234.0/23 | No ROA covers it. Add a ROA for AS20900, maxLength 23. |
| Route object: none | 137.129.234.0/23 | No route object for it. A route object for 137.129.0.0/16 with origin AS20900 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20900 in the RIR database for the space. |
| ROA: none | 137.129.236.0/23 | No ROA covers it. Add a ROA for AS20900, maxLength 23. |
| Route object: none | 137.129.236.0/23 | No route object for it. A route object for 137.129.0.0/16 with origin AS20900 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20900 in the RIR database for the space. |
| ROA: none | 137.129.0.0/16 | No ROA covers it. Add a ROA for AS20900, maxLength 16. |
| Route object: none | 91.214.114.0/23 | No route object for it. Add a route object with origin AS20900 in the RIR database for the space. |
| Route object: none | 185.182.252.0/24 | No route object for it. A route object for 185.182.252.0/22 with origin AS20900 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20900 in the RIR database for the space. |
| Route object: none | 213.190.88.0/24 | No route object for it. A route object for 213.190.64.0/19 with origin AS20900 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20900 in the RIR database for the space. |
| Route object: none | 78.159.132.0/23 | No route object for it. A route object for 78.159.132.0/22 with origin AS20900 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20900 in the RIR database for the space. |
| Route object: none | 78.159.134.0/23 | No route object for it. A route object for 78.159.132.0/22 with origin AS20900 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20900 in the RIR database for the space. |
| Route object: none | 213.190.69.0/24 | No route object for it. A route object for 213.190.64.0/19 with origin AS20900 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20900 in the RIR database for the space. |
| Route object: none | 2001:1b08::/32 | No route object for it. Add a route object with origin AS20900 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS20900 whose prefix no peer sees AS20900 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 78.159.148.0/24 | RIPE | Valid |
| 91.214.114.0/24 | RIPE | Valid |
| 91.214.115.0/24 | RIPE | Valid |
| 91.238.150.0/23 | RIPE | No ROA |
| 91.240.78.0/23 | RIPE | No ROA |
| 91.240.78.0/24 | RIPE | Invalid: origin |
| 91.240.79.0/24 | RIPE | Invalid: origin |
| 193.57.84.0/22 | RIPE | No ROA |
| 193.57.132.0/22 | RIPE | No ROA |
| 194.4.11.0/24 | RIPE | No ROA |
| 195.78.82.0/24 | RIPE | No ROA |
| 195.242.221.0/24 | RIPE | No ROA |
| 195.242.222.0/24 | RIPE | No ROA |
| 213.190.91.0/24 | RIPE | Valid |
| 2001:1b08::/48 | RIPE | Valid |
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.