Network · data from 2026-11-12
AS270115 HUNA SISTEMAS
Registry name: AS270115 - HUNA SISTEMAS S. DE R.L. DE C.V., MX · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS270115, 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.
| 187.102.228.0/24 | Valid | Nonecovered by 187.102.228.0/23 | 673 100% |
AS-SET
AS270115'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 4 are in fix.csv.
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 187.102.228.0/24 | No route object for it. A route object for 187.102.228.0/23 with origin AS270115 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270115 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS270115 whose prefix no peer sees AS270115 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.65.142.0/24 | RADB | No ROA |
| 187.102.228.0/23 | LACNIC | Valid |
| 2806:3b7::/32 | LACNIC | 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.