Network · data from 2026-11-12
AS208172 PV-HOSTED Proton AG
Registry name: PV-HOSTED Proton AG, CH · not in PeeringDB
93IPv4 routes
100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
0 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
8Route objects not announced
registered with origin AS208172, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS208172, 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.
| 153.75.53.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 72.251.210.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 72.251.211.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 80.47.32.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 80.47.33.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 80.47.34.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 80.47.35.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 80.47.38.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 80.47.39.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 80.47.42.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.82.74.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.82.75.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 134.82.78.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 153.75.49.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 153.75.50.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 153.75.51.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 153.75.52.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 153.75.61.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 159.26.104.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 159.26.105.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 159.26.106.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 159.26.107.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 159.26.108.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 159.26.110.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 159.26.111.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 159.26.112.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 159.26.113.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 159.26.114.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 159.26.115.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 159.26.117.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 159.26.118.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 159.26.121.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 159.26.123.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 159.26.124.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 159.26.125.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 159.26.127.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 205.147.17.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 205.147.19.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 205.147.27.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 205.147.28.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 205.147.30.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 205.147.31.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 72.251.209.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 72.251.212.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 72.251.213.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 72.251.214.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 72.251.216.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 72.251.222.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 80.47.44.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 80.47.45.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 80.47.50.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 153.75.60.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 159.26.96.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 159.26.98.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 159.26.99.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 159.26.100.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 159.26.101.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 159.26.102.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 205.147.16.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 205.147.18.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 72.251.208.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 72.251.217.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 72.251.219.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 80.47.36.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 80.47.37.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 80.47.47.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 80.47.48.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 80.47.49.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 134.82.69.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 134.82.71.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 134.82.79.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 153.75.48.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 159.26.109.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 159.26.116.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 205.147.29.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 72.251.218.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 80.47.51.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 81.27.86.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 134.82.77.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 159.26.122.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 72.251.220.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 72.251.221.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 134.82.68.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 134.82.70.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 134.82.73.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 159.26.97.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 159.26.103.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 159.26.120.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 159.26.126.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 205.147.22.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 72.251.215.0/24 | Valid | RIR databaseRIPE | 667 99% |
| 80.47.46.0/24 | Valid | RIR databaseRIPE | 667 99% |
| 159.26.119.0/24 | Valid | RIR databaseRIPE | 667 99% |
AS-SET
AS208172 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 8 are in fix.csv.
- Route object: not announced8
Route objects not announced
Route objects with origin AS208172 whose prefix no peer sees AS208172 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 80.47.40.0/24 | RIPE | Valid |
| 80.47.41.0/24 | RIPE | Valid |
| 80.47.43.0/24 | RIPE | Valid |
| 134.82.76.0/24 | RIPE | No ROA |
| 205.147.20.0/24 | RIPE | Valid |
| 205.147.21.0/24 | RIPE | Valid |
| 205.147.23.0/24 | RIPE | Valid |
| 205.147.26.0/24 | RIPE | Invalid: origin |
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.