Network · data from 2026-11-12
AS52390 Administradora de Redes, S.A.
Registry name: AS52390 - Administradora de Redes, S.A., HN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS52390, 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.
| 2803:5600::/32 | No ROA | Other origin only | 636 100% |
AS-SET
AS52390'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 5 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2803:5600::/32 | No ROA covers it. Add a ROA for AS52390, maxLength 32. |
| Route object: none | 2803:5600::/32 | Route objects for it name AS27932, AS264719. Add a route object with origin AS52390 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS52390 whose prefix no peer sees AS52390 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 190.123.24.0/21 | ALTDB, NTTCOM, RADB, RIPE-NONAUTH | No ROA |
| 200.75.184.0/21 | RADB | No ROA |
| 2803:740::/32 | 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.