Network · data from 2026-11-12
AS204592 COSMOS-AS Cosmos Wireless Ltd
Registry name: COSMOS-AS Cosmos Wireless Ltd, GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS204592, 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.
| 45.155.122.0/24 | Valid | Nonecovered by 45.155.122.0/23 | 671 100% |
| 45.155.123.0/24 | Valid | Other origin onlycovered by 45.155.122.0/23 | 671 100% |
| 185.230.112.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.230.113.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.230.114.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.230.115.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS204592 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 5 are in fix.csv.
- Route object: none2
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 45.155.122.0/24 | No route object for it. A route object for 45.155.122.0/23 with origin AS204592 covers it (filters allowing more-specifics accept it). Add a route object with origin AS204592 in the RIR database for the space. |
| Route object: none | 45.155.123.0/24 | Route objects for it name AS199631. A route object for 45.155.122.0/23 with origin AS204592 covers it (filters allowing more-specifics accept it). Add a route object with origin AS204592 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS204592 whose prefix no peer sees AS204592 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.155.122.0/23 | RIPE | Valid |
| 82.114.44.0/24 | RIPE | Valid |
| 82.114.45.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.