Network · data from 2026-11-12
AS28050 ADN Solutions
Registry name: AS28050 - ADN Solutions S.A. (Rokru Int.), CR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS28050, 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.
| 200.74.248.0/24 | Valid | Nonecovered by 200.74.248.0/21 | 671 100% |
| 200.74.250.0/24 | Valid | Nonecovered by 200.74.248.0/21 | 671 100% |
| 200.74.251.0/24 | Valid | Nonecovered by 200.74.248.0/21 | 671 100% |
| 200.74.253.0/24 | Valid | Nonecovered by 200.74.248.0/21 | 671 100% |
| 200.74.255.0/24 | Valid | Nonecovered by 200.74.248.0/21 | 671 100% |
| 200.74.249.0/24 | Valid | Nonecovered by 200.74.248.0/21 | 670 100% |
| 200.74.252.0/24 | Valid | Nonecovered by 200.74.248.0/21 | 670 100% |
| 200.74.254.0/24 | Valid | Nonecovered by 200.74.248.0/21 | 670 100% |
AS-SET
AS28050'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 9 are in fix.csv.
- Route object: none8
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 200.74.248.0/24 | No route object for it. A route object for 200.74.248.0/21 with origin AS28050 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28050 in the RIR database for the space. |
| Route object: none | 200.74.250.0/24 | No route object for it. A route object for 200.74.248.0/21 with origin AS28050 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28050 in the RIR database for the space. |
| Route object: none | 200.74.251.0/24 | No route object for it. A route object for 200.74.248.0/21 with origin AS28050 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28050 in the RIR database for the space. |
| Route object: none | 200.74.253.0/24 | No route object for it. A route object for 200.74.248.0/21 with origin AS28050 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28050 in the RIR database for the space. |
| Route object: none | 200.74.255.0/24 | No route object for it. A route object for 200.74.248.0/21 with origin AS28050 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28050 in the RIR database for the space. |
| Route object: none | 200.74.249.0/24 | No route object for it. A route object for 200.74.248.0/21 with origin AS28050 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28050 in the RIR database for the space. |
| Route object: none | 200.74.252.0/24 | No route object for it. A route object for 200.74.248.0/21 with origin AS28050 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28050 in the RIR database for the space. |
| Route object: none | 200.74.254.0/24 | No route object for it. A route object for 200.74.248.0/21 with origin AS28050 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28050 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS28050 whose prefix no peer sees AS28050 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 200.74.248.0/21 | RADB | 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.