Network · data from 2026-11-12
AS206487 netvoz NEXVOLMAR S.L.
Registry name: netvoz NEXVOLMAR S.L., ES · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS206487, 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.
| 185.99.42.0/24 | Valid | Nonecovered by 185.99.40.0/22 | 523 78% |
| 185.176.180.0/23 | Valid | Nonecovered by 185.176.180.0/22 | 523 78% |
| 185.99.40.0/24 | Valid | Nonecovered by 185.99.40.0/22 | 521 77% |
| 185.176.183.0/24 | Valid | Nonecovered by 185.176.180.0/22 | 520 77% |
| 5.40.80.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 5.40.106.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 5.40.136.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 5.40.156.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 5.40.253.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 62.82.158.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 62.174.66.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 62.175.253.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.39.33.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.140.16.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 95.39.61.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 188.86.116.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 77.241.62.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS206487 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 30 are in fix.csv.
- Route object: none4
- Route object: not announced26
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.99.42.0/24 | No route object for it. A route object for 185.99.40.0/22 with origin AS206487 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206487 in the RIR database for the space. |
| Route object: none | 185.176.180.0/23 | No route object for it. A route object for 185.176.180.0/22 with origin AS206487 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206487 in the RIR database for the space. |
| Route object: none | 185.99.40.0/24 | No route object for it. A route object for 185.99.40.0/22 with origin AS206487 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206487 in the RIR database for the space. |
| Route object: none | 185.176.183.0/24 | No route object for it. A route object for 185.176.180.0/22 with origin AS206487 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206487 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS206487 whose prefix no peer sees AS206487 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.40.18.0/24 | RIPE | Valid |
| 5.40.41.0/24 | RIPE | Valid |
| 5.40.85.0/24 | RIPE | Valid |
| 5.40.138.0/24 | RIPE | Valid |
| 5.40.149.0/24 | RIPE | Valid |
| 5.40.244.0/24 | RIPE | Valid |
| 62.82.50.0/24 | RIPE | Valid |
| 62.82.51.0/24 | RIPE | Invalid: origin |
| 62.175.252.0/23 | RIPE | Invalid: origin |
| 62.175.252.0/24 | RIPE | Valid |
| 77.241.49.0/24 | RIPE | Valid |
| 82.159.153.0/24 | RIPE | Invalid: origin |
| 84.124.62.0/24 | RIPE | Invalid: origin |
| 89.39.34.0/24 | RIPE | Valid |
| 89.140.16.0/24 | RIPE | Valid |
| 89.140.17.0/24 | RIPE | Valid |
| 176.119.132.0/22 | RIPE | Invalid: origin |
| 185.99.40.0/22 | RIPE | No ROA |
| 185.176.180.0/22 | RIPE | No ROA |
| 185.185.64.0/22 | RIPE | No ROA |
| 185.255.149.0/24 | RIPE | No ROA |
| 194.49.0.0/24 | RIPE | Invalid: origin |
| 194.49.1.0/24 | RIPE | Invalid: origin |
| 194.49.2.0/23 | RIPE | Invalid: origin |
| 2a0b:3780::/32 | RIPE | Valid |
| 2a0d:a280::/29 | 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.