Network · data from 2026-11-12
AS271368 AS271368 - i9 Telecom LTDA
Registry name: AS271368 - i9 Telecom LTDA, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS271368, 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.
| 179.0.63.0/24 | No ROA | Nonecovered by 179.0.60.0/22 | 670 100% |
| 2804:7a64:2000::/35 | No ROA | Nonecovered by 2804:7a64::/32 | 634 100% |
| 2804:7a64:a000::/35 | No ROA | Nonecovered by 2804:7a64::/32 | 634 100% |
| 179.0.61.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 179.0.62.0/24 | No ROA | Other IRR onlyRADB | 669 99% |
AS-SET
AS271368 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 14 are in fix.csv.
- ROA: none5
- Route object: none3
- Route object: RIR2
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 179.0.63.0/24 | No ROA covers it. Add a ROA for AS271368, maxLength 24. |
| Route object: none | 179.0.63.0/24 | No route object for it. A route object for 179.0.60.0/22 with origin AS271368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271368 in the RIR database for the space. |
| ROA: none | 2804:7a64:2000::/35 | No ROA covers it. Add a ROA for AS271368, maxLength 35. |
| Route object: none | 2804:7a64:2000::/35 | No route object for it. A route object for 2804:7a64::/32 with origin AS271368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271368 in the RIR database for the space. |
| ROA: none | 2804:7a64:a000::/35 | No ROA covers it. Add a ROA for AS271368, maxLength 35. |
| Route object: none | 2804:7a64:a000::/35 | No route object for it. A route object for 2804:7a64::/32 with origin AS271368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271368 in the RIR database for the space. |
| ROA: none | 179.0.61.0/24 | No ROA covers it. Add a ROA for AS271368, maxLength 24. |
| Route object: RIR | 179.0.61.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 179.0.62.0/24 | No ROA covers it. Add a ROA for AS271368, maxLength 24. |
| Route object: RIR | 179.0.62.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS271368 whose prefix no peer sees AS271368 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 179.0.60.0/22 | RADB, TC | No ROA |
| 179.0.60.0/23 | RADB | No ROA |
| 179.0.60.0/24 | RADB | No ROA |
| 2804:7a64::/32 | RADB, TC | 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.