Network · data from 2026-11-12
AS210403 LWS Groupe LWS SARL
Registry name: LWS Groupe LWS SARL, FR · not in PeeringDB
46IPv4 routes
100.0% RPKI valid · 87.0% with a route object
10IPv6 routes
90.0% RPKI valid · 70.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
1No ROA
9 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
23Route objects not announced
registered with origin AS210403, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS210403, 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.
| 2a00:7ee0:2000::/36 | No ROA | RIR databaseRIPE | 635 100% |
| 180.149.196.0/24 | Valid | Nonecovered by 180.149.196.0/22 | 673 100% |
| 180.149.197.0/24 | Valid | Nonecovered by 180.149.196.0/22 | 673 100% |
| 180.149.198.0/24 | Valid | Nonecovered by 180.149.196.0/22 | 673 100% |
| 180.149.199.0/24 | Valid | Nonecovered by 180.149.196.0/22 | 673 100% |
| 195.110.34.0/24 | Valid | Nonecovered by 195.110.34.0/23 | 673 100% |
| 195.110.35.0/24 | Valid | Nonecovered by 195.110.34.0/23 | 673 100% |
| 2a00:7ee0:40::/48 | Valid | Nonecovered by 2a00:7ee0:40::/44 | 635 100% |
| 2a00:7ee0:41::/48 | Valid | Nonecovered by 2a00:7ee0:40::/44 | 635 100% |
| 2a00:7ee0:3000::/36 | Valid | None | 635 100% |
| 31.207.32.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.207.33.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.207.34.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.207.35.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.207.36.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.207.37.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.207.38.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.207.39.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.138.45.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.138.58.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.199.179.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.216.107.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.234.194.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.234.195.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.98.129.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.98.131.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.98.136.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.98.137.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.98.138.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.135.132.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.170.12.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.170.13.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.170.14.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.170.15.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.238.116.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 192.162.68.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 192.162.69.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 192.162.70.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 192.162.71.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.37.145.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.203.239.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.126.193.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.156.132.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.156.133.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.156.134.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.156.135.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.255.195.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 83.229.19.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.98.128.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.98.139.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 2a00:7ee0::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a00:7ee0:1::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a00:7ee0:2::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a00:7ee0:8::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a00:7ee0:9::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a00:7ee0:4000::/36 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS210403 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 33 are in fix.csv.
- ROA: none1
- Route object: none9
- Route object: not announced23
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a00:7ee0:2000::/36 | No ROA covers it. Add a ROA for AS210403, maxLength 36. |
| Route object: none | 180.149.196.0/24 | No route object for it. A route object for 180.149.196.0/22 with origin AS210403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS210403 in the RIR database for the space. |
| Route object: none | 180.149.197.0/24 | No route object for it. A route object for 180.149.196.0/22 with origin AS210403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS210403 in the RIR database for the space. |
| Route object: none | 180.149.198.0/24 | No route object for it. A route object for 180.149.196.0/22 with origin AS210403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS210403 in the RIR database for the space. |
| Route object: none | 180.149.199.0/24 | No route object for it. A route object for 180.149.196.0/22 with origin AS210403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS210403 in the RIR database for the space. |
| Route object: none | 195.110.34.0/24 | No route object for it. A route object for 195.110.34.0/23 with origin AS210403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS210403 in the RIR database for the space. |
| Route object: none | 195.110.35.0/24 | No route object for it. A route object for 195.110.34.0/23 with origin AS210403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS210403 in the RIR database for the space. |
| Route object: none | 2a00:7ee0:40::/48 | No route object for it. A route object for 2a00:7ee0:40::/44 with origin AS210403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS210403 in the RIR database for the space. |
| Route object: none | 2a00:7ee0:41::/48 | No route object for it. A route object for 2a00:7ee0:40::/44 with origin AS210403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS210403 in the RIR database for the space. |
| Route object: none | 2a00:7ee0:3000::/36 | No route object for it. Add a route object with origin AS210403 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS210403 whose prefix no peer sees AS210403 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 31.207.32.0/21 | RIPE | No ROA |
| 78.24.248.0/21 | RIPE | Valid |
| 78.24.248.0/24 | RIPE | Valid |
| 78.24.249.0/24 | RIPE | Valid |
| 78.24.250.0/24 | RIPE | Valid |
| 78.24.251.0/24 | RIPE | Valid |
| 78.24.252.0/24 | RIPE | Valid |
| 78.24.253.0/24 | RIPE | Valid |
| 78.24.254.0/24 | RIPE | Valid |
| 78.24.255.0/24 | RIPE | Valid |
| 79.170.232.0/21 | RIPE | No ROA |
| 91.234.194.0/23 | RIPE | No ROA |
| 180.149.196.0/22 | RIPE | No ROA |
| 185.98.128.0/23 | RIPE | No ROA |
| 185.98.136.0/22 | RIPE | No ROA |
| 192.162.68.0/22 | RIPE | No ROA |
| 195.110.34.0/23 | RIPE | No ROA |
| 213.156.132.0/22 | RIPE | Valid |
| 2a00:7ee0:3::/48 | RIPE | No ROA |
| 2a00:7ee0:a::/48 | RIPE | No ROA |
| 2a00:7ee0:b::/48 | RIPE | No ROA |
| 2a00:7ee0:c::/46 | RIPE | No ROA |
| 2a00:7ee0:40::/44 | 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.