Network · data from 2026-11-12
AS31590 RACKHOSTING-AS Rackhosting.com ApS
Registry name: RACKHOSTING-AS Rackhosting.com ApS, DK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS31590, 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.110.80.0/23 | No ROA | Nonecovered by 185.110.80.0/22 | 673 100% |
| 185.110.82.0/23 | No ROA | Nonecovered by 185.110.80.0/22 | 673 100% |
| 77.247.64.0/22 | Valid | Nonecovered by 77.247.64.0/20 | 673 100% |
| 77.247.68.0/22 | Valid | Nonecovered by 77.247.64.0/20 | 673 100% |
| 77.247.72.0/22 | Valid | Nonecovered by 77.247.64.0/20 | 673 100% |
| 77.247.76.0/22 | Valid | Nonecovered by 77.247.64.0/20 | 673 100% |
| 194.150.108.0/23 | Valid | Nonecovered by 194.150.108.0/22 | 673 100% |
| 194.150.110.0/23 | Valid | Nonecovered by 194.150.108.0/22 | 673 100% |
| 185.121.60.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 194.242.40.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a02:4de0::/32 | Valid | RIR databaseRIPE | 635 100% |
| 185.121.60.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS31590 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 13 are in fix.csv.
- ROA: none2
- Route object: none8
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.110.80.0/23 | No ROA covers it. Add a ROA for AS31590, maxLength 23. |
| Route object: none | 185.110.80.0/23 | No route object for it. A route object for 185.110.80.0/22 with origin AS31590 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31590 in the RIR database for the space. |
| ROA: none | 185.110.82.0/23 | No ROA covers it. Add a ROA for AS31590, maxLength 23. |
| Route object: none | 185.110.82.0/23 | No route object for it. A route object for 185.110.80.0/22 with origin AS31590 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31590 in the RIR database for the space. |
| Route object: none | 77.247.64.0/22 | No route object for it. A route object for 77.247.64.0/20 with origin AS31590 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31590 in the RIR database for the space. |
| Route object: none | 77.247.68.0/22 | No route object for it. A route object for 77.247.64.0/20 with origin AS31590 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31590 in the RIR database for the space. |
| Route object: none | 77.247.72.0/22 | No route object for it. A route object for 77.247.64.0/20 with origin AS31590 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31590 in the RIR database for the space. |
| Route object: none | 77.247.76.0/22 | No route object for it. A route object for 77.247.64.0/20 with origin AS31590 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31590 in the RIR database for the space. |
| Route object: none | 194.150.108.0/23 | No route object for it. A route object for 194.150.108.0/22 with origin AS31590 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31590 in the RIR database for the space. |
| Route object: none | 194.150.110.0/23 | No route object for it. A route object for 194.150.108.0/22 with origin AS31590 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31590 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS31590 whose prefix no peer sees AS31590 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 77.247.64.0/20 | RIPE | No ROA |
| 185.110.80.0/22 | RIPE | No ROA |
| 194.150.108.0/22 | 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.