Network · data from 2026-11-12
AS271822 INNO FIBER INFI CIA
Registry name: AS271822 - INNO FIBER INFI CIA LTDA, EC · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS271822, 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.
| 186.209.213.0/24 | Valid | Nonecovered by 186.209.212.0/22 | 672 100% |
| 186.209.212.0/24 | Valid | Nonecovered by 186.209.212.0/22 | 671 100% |
| 186.209.215.0/24 | Valid | Nonecovered by 186.209.212.0/22 | 671 100% |
| 2803:810::/36 | Valid | Nonecovered by 2803:810::/32 | 633 100% |
| 2803:810:2021::/48 | Valid | Nonecovered by 2803:810::/32 | 633 100% |
| 2803:810:f000::/36 | Valid | Nonecovered by 2803:810::/32 | 633 100% |
| 186.209.214.0/24 | Valid | Nonecovered by 186.209.212.0/22 | 20 3%low visibility |
| 186.209.212.0/22 | Valid | Other IRR onlyRADB | 668 99% |
| 2803:810::/32 | Valid | Other IRR onlyRADB | 633 100% |
AS-SET
AS271822'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: none7
- Route object: RIR2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 186.209.213.0/24 | No route object for it. A route object for 186.209.212.0/22 with origin AS271822 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271822 in the RIR database for the space. |
| Route object: none | 186.209.212.0/24 | No route object for it. A route object for 186.209.212.0/22 with origin AS271822 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271822 in the RIR database for the space. |
| Route object: none | 186.209.215.0/24 | No route object for it. A route object for 186.209.212.0/22 with origin AS271822 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271822 in the RIR database for the space. |
| Route object: none | 2803:810::/36 | No route object for it. A route object for 2803:810::/32 with origin AS271822 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271822 in the RIR database for the space. |
| Route object: none | 2803:810:2021::/48 | No route object for it. A route object for 2803:810::/32 with origin AS271822 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271822 in the RIR database for the space. |
| Route object: none | 2803:810:f000::/36 | No route object for it. A route object for 2803:810::/32 with origin AS271822 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271822 in the RIR database for the space. |
| Route object: none | 186.209.214.0/24 | No route object for it. A route object for 186.209.212.0/22 with origin AS271822 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271822 in the RIR database for the space. |
| Route object: RIR | 186.209.212.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2803:810::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS271822 is announced.
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.