Network · data from 2026-11-12
AS28091 AS28091 - SIXMANAGER TECNOLOGIAS SPA
Registry name: AS28091 - SIXMANAGER TECNOLOGIAS SPA, CL · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS28091, 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.
| 190.2.88.0/24 | Valid | Nonecovered by 190.2.88.0/21 | 672 100% |
| 190.2.89.0/24 | Valid | Nonecovered by 190.2.88.0/21 | 672 100% |
| 190.2.90.0/24 | Valid | Nonecovered by 190.2.88.0/21 | 672 100% |
| 190.2.91.0/24 | Valid | Nonecovered by 190.2.88.0/21 | 672 100% |
| 190.2.92.0/24 | Valid | Nonecovered by 190.2.88.0/21 | 669 99% |
| 190.2.93.0/24 | Valid | Nonecovered by 190.2.88.0/21 | 669 99% |
| 190.2.94.0/24 | Valid | Nonecovered by 190.2.88.0/21 | 669 99% |
| 190.2.95.0/24 | Valid | Nonecovered by 190.2.88.0/21 | 669 99% |
AS-SET
AS28091 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 9 are in fix.csv.
- Route object: none8
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 190.2.88.0/24 | No route object for it. A route object for 190.2.88.0/21 with origin AS28091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28091 in the RIR database for the space. |
| Route object: none | 190.2.89.0/24 | No route object for it. A route object for 190.2.88.0/21 with origin AS28091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28091 in the RIR database for the space. |
| Route object: none | 190.2.90.0/24 | No route object for it. A route object for 190.2.88.0/21 with origin AS28091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28091 in the RIR database for the space. |
| Route object: none | 190.2.91.0/24 | No route object for it. A route object for 190.2.88.0/21 with origin AS28091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28091 in the RIR database for the space. |
| Route object: none | 190.2.92.0/24 | No route object for it. A route object for 190.2.88.0/21 with origin AS28091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28091 in the RIR database for the space. |
| Route object: none | 190.2.93.0/24 | No route object for it. A route object for 190.2.88.0/21 with origin AS28091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28091 in the RIR database for the space. |
| Route object: none | 190.2.94.0/24 | No route object for it. A route object for 190.2.88.0/21 with origin AS28091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28091 in the RIR database for the space. |
| Route object: none | 190.2.95.0/24 | No route object for it. A route object for 190.2.88.0/21 with origin AS28091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28091 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS28091 whose prefix no peer sees AS28091 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 190.2.88.0/21 | NTTCOM, RADB | 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.