Network · data from 2026-11-12
AS207046 redservicio XNET CORE SL
Registry name: redservicio XNET CORE SL, ES · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS207046, 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.
| 103.89.132.0/22 | No ROA | Other origin only | 673 100% |
| 178.212.225.0/24 | Valid | None | 673 100% |
| 185.221.16.0/23 | Valid | None | 673 100% |
| 185.224.220.0/22 | Valid | None | 673 100% |
| 185.227.206.0/24 | Valid | None | 673 100% |
| 185.227.207.0/24 | Valid | None | 673 100% |
| 185.249.204.0/22 | Valid | None | 673 100% |
| 194.113.28.0/22 | Valid | None | 673 100% |
| 194.146.220.0/22 | Valid | None | 673 100% |
| 185.247.5.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.247.6.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.247.7.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.249.52.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.250.182.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 80.71.155.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS207046 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 16 are in fix.csv.
- ROA: none1
- Route object: none9
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.89.132.0/22 | No ROA covers it. Add a ROA for AS207046, maxLength 22. |
| Route object: none | 103.89.132.0/22 | Route objects for it name AS201942. Add a route object with origin AS207046 in the RIR database for the space. |
| Route object: none | 178.212.225.0/24 | No route object for it. Add a route object with origin AS207046 in the RIR database for the space. |
| Route object: none | 185.221.16.0/23 | No route object for it. Add a route object with origin AS207046 in the RIR database for the space. |
| Route object: none | 185.224.220.0/22 | No route object for it. Add a route object with origin AS207046 in the RIR database for the space. |
| Route object: none | 185.227.206.0/24 | No route object for it. Add a route object with origin AS207046 in the RIR database for the space. |
| Route object: none | 185.227.207.0/24 | No route object for it. Add a route object with origin AS207046 in the RIR database for the space. |
| Route object: none | 185.249.204.0/22 | No route object for it. Add a route object with origin AS207046 in the RIR database for the space. |
| Route object: none | 194.113.28.0/22 | No route object for it. Add a route object with origin AS207046 in the RIR database for the space. |
| Route object: none | 194.146.220.0/22 | No route object for it. Add a route object with origin AS207046 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS207046 whose prefix no peer sees AS207046 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.126.52.0/22 | RIPE | Invalid: origin |
| 185.201.152.0/24 | RIPE | Invalid: origin |
| 185.201.153.0/24 | RIPE | Invalid: origin |
| 185.201.154.0/24 | RIPE | Invalid: origin |
| 185.201.155.0/24 | RIPE | Invalid: origin |
| 185.247.4.0/22 | 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.