Network · data from 2026-11-12
AS35470 XL Internet Services B.V.
Registry name: XL-AS Signet B.V., NL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS35470, 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.
| 193.108.234.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 83.96.201.0/24 | Valid | Nonecovered by 83.96.200.0/22 | 1 0%low visibility |
| 31.3.100.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.170.89.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.170.92.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 81.4.84.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 83.96.200.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 83.96.204.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 83.96.212.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 83.96.216.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 83.96.220.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 83.96.236.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 83.96.240.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 83.96.244.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 83.96.252.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 83.217.67.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 83.217.69.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.10.176.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 85.10.184.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 85.10.188.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 85.222.224.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 87.239.11.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.31.98.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 89.31.101.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.199.74.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.191.134.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.191.135.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 141.138.207.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.3.208.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.110.172.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.110.200.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.110.202.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.115.216.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.115.217.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.115.218.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.138.205.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.138.206.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 194.60.207.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.187.240.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 213.249.80.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.19.239.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.170.21.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.158.80.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 77.241.80.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 77.241.86.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a02:348:10::/44 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:348:20::/44 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:348:a8::/45 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:348:c0::/44 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:348:500::/40 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:348:600::/39 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:348:1200::/40 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:348:1700::/40 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:348:1800::/40 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:348:f000::/36 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:d0f::/44 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:348:5e6::/48 | Valid | RIR databaseRIPE | 1 0%low visibility |
AS-SET
AS35470'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 5 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 193.108.234.0/23 | No ROA covers it. Add a ROA for AS35470, maxLength 23. |
| Route object: none | 83.96.201.0/24 | No route object for it. A route object for 83.96.200.0/22 with origin AS35470 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35470 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS35470 whose prefix no peer sees AS35470 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 37.228.72.0/21 | RIPE | No ROA |
| 83.96.241.0/24 | RIPE | Valid |
| 83.96.245.0/24 | 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.