Network · data from 2026-11-12
AS60558 SECUREDSERVERS-EU PHOENIX NAP, LLC.
Registry name: SECUREDSERVERS-EU PHOENIX NAP, LLC., US · not in PeeringDB
29IPv4 routes
89.7% RPKI valid · 41.4% with a route object
4IPv6 routes
100.0% RPKI valid · 0.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
3No ROA
21 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
5Route objects not announced
registered with origin AS60558, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS60558, 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.
| 192.240.203.0/24 | No ROA | None | 672 100% |
| 192.240.211.0/24 | No ROA | None | 672 100% |
| 185.56.136.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 23.235.232.0/21 | Valid | None | 672 100% |
| 83.229.100.0/24 | Valid | Other origin only | 672 100% |
| 103.67.200.0/24 | Valid | None | 672 100% |
| 103.67.203.0/24 | Valid | None | 672 100% |
| 131.153.16.0/21 | Valid | None | 672 100% |
| 131.153.86.0/24 | Valid | None | 672 100% |
| 131.153.158.0/24 | Valid | None | 672 100% |
| 131.153.243.0/24 | Valid | None | 672 100% |
| 185.52.55.0/24 | Valid | Nonecovered by 185.52.52.0/22 | 672 100% |
| 185.62.36.0/22 | Valid | None | 672 100% |
| 192.240.230.0/24 | Valid | Nonecovered by 192.240.230.0/23 | 672 100% |
| 192.240.231.0/24 | Valid | Nonecovered by 192.240.230.0/23 | 672 100% |
| 192.240.232.0/24 | Valid | Nonecovered by 192.240.232.0/22 | 672 100% |
| 192.240.233.0/24 | Valid | Nonecovered by 192.240.232.0/22 | 672 100% |
| 192.240.234.0/24 | Valid | Nonecovered by 192.240.232.0/22 | 672 100% |
| 2a00:8860:100::/40 | Valid | None | 636 100% |
| 2a00:8860:10b::/48 | Valid | None | 636 100% |
| 2a00:8860:10d::/48 | Valid | None | 636 100% |
| 2a01:b960:2301::/48 | Valid | None | 636 100% |
| 23.235.232.0/24 | Valid | Other IRR onlyRIPE-NONAUTH | 672 100% |
| 37.140.238.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.140.239.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 125.253.79.0/24 | Valid | RIR databaseARIN | 672 100% |
| 163.5.194.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 185.28.188.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.28.189.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.28.190.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.28.191.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.52.52.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 192.240.192.0/22 | Valid | RIR databaseARIN | 672 100% |
AS-SET
AS60558 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.
- ROA: none3
- Route object: none21
- Route object: RIR1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 192.240.203.0/24 | No ROA covers it. Add a ROA for AS60558, maxLength 24. |
| Route object: none | 192.240.203.0/24 | No route object for it. Add a route object with origin AS60558 in the RIR database for the space. |
| ROA: none | 192.240.211.0/24 | No ROA covers it. Add a ROA for AS60558, maxLength 24. |
| Route object: none | 192.240.211.0/24 | No route object for it. Add a route object with origin AS60558 in the RIR database for the space. |
| ROA: none | 185.56.136.0/22 | No ROA covers it. Add a ROA for AS60558, maxLength 22. |
| Route object: none | 23.235.232.0/21 | No route object for it. Add a route object with origin AS60558 in the RIR database for the space. |
| Route object: none | 83.229.100.0/24 | Route objects for it name AS25228, AS29802. Add a route object with origin AS60558 in the RIR database for the space. |
| Route object: none | 103.67.200.0/24 | No route object for it. Add a route object with origin AS60558 in the RIR database for the space. |
| Route object: none | 103.67.203.0/24 | No route object for it. Add a route object with origin AS60558 in the RIR database for the space. |
| Route object: none | 131.153.16.0/21 | No route object for it. Add a route object with origin AS60558 in the RIR database for the space. |
| Route object: none | 131.153.86.0/24 | No route object for it. Add a route object with origin AS60558 in the RIR database for the space. |
| Route object: none | 131.153.158.0/24 | No route object for it. Add a route object with origin AS60558 in the RIR database for the space. |
| Route object: none | 131.153.243.0/24 | No route object for it. Add a route object with origin AS60558 in the RIR database for the space. |
| Route object: none | 185.52.55.0/24 | No route object for it. A route object for 185.52.52.0/22 with origin AS60558 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60558 in the RIR database for the space. |
| Route object: none | 185.62.36.0/22 | No route object for it. Add a route object with origin AS60558 in the RIR database for the space. |
| Route object: none | 192.240.230.0/24 | No route object for it. A route object for 192.240.230.0/23 with origin AS60558 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60558 in the RIR database for the space. |
| Route object: none | 192.240.231.0/24 | No route object for it. A route object for 192.240.230.0/23 with origin AS60558 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60558 in the RIR database for the space. |
| Route object: none | 192.240.232.0/24 | No route object for it. A route object for 192.240.232.0/22 with origin AS60558 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60558 in the RIR database for the space. |
| Route object: none | 192.240.233.0/24 | No route object for it. A route object for 192.240.232.0/22 with origin AS60558 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60558 in the RIR database for the space. |
| Route object: none | 192.240.234.0/24 | No route object for it. A route object for 192.240.232.0/22 with origin AS60558 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60558 in the RIR database for the space. |
| Route object: none | 2a00:8860:100::/40 | No route object for it. Add a route object with origin AS60558 in the RIR database for the space. |
| Route object: none | 2a00:8860:10b::/48 | No route object for it. Add a route object with origin AS60558 in the RIR database for the space. |
| Route object: none | 2a00:8860:10d::/48 | No route object for it. Add a route object with origin AS60558 in the RIR database for the space. |
| Route object: none | 2a01:b960:2301::/48 | No route object for it. Add a route object with origin AS60558 in the RIR database for the space. |
| Route object: RIR | 23.235.232.0/24 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS60558 whose prefix no peer sees AS60558 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.44.108.0/24 | RIPE-NONAUTH | No ROA |
| 185.28.188.0/22 | RIPE | No ROA |
| 192.240.230.0/23 | ARIN | Valid |
| 192.240.232.0/22 | ARIN | Valid |
| 198.244.32.0/22 | ALTDB | 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.