Network · data from 2026-11-12
AS263008 UNI TELECOMUNICACOES
Registry name: AS263008 - RIO CABLE CORPORATE LTDA - ME, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS263008, 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.226.208.0/21 | No ROA | Other IRR onlyRADB, TC | 670 100% |
| 186.226.208.0/23 | No ROA | Other IRR onlyRADB | 112 17% |
| 186.226.208.0/24 | No ROA | Other IRR onlyRADB | 112 17% |
| 186.226.209.0/24 | No ROA | Other IRR onlyRADB | 112 17% |
| 186.226.210.0/23 | No ROA | Other IRR onlyRADB | 112 17% |
| 186.226.210.0/24 | No ROA | Other IRR onlyRADB | 112 17% |
| 186.226.211.0/24 | No ROA | Other IRR onlyRADB | 112 17% |
| 186.226.212.0/24 | No ROA | Other IRR onlyRADB | 112 17% |
| 186.226.213.0/24 | No ROA | Other IRR onlyRADB | 112 17% |
| 186.226.215.0/24 | No ROA | Other IRR onlyRADB | 112 17% |
| 186.226.214.0/24 | No ROA | Other IRR onlyRADB | 111 16% |
AS-SET
AS263008'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 25 are in fix.csv.
- ROA: none11
- Route object: RIR11
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 186.226.208.0/21 | No ROA covers it. Add a ROA for AS263008, maxLength 21. |
| Route object: RIR | 186.226.208.0/21 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 186.226.208.0/23 | No ROA covers it. Add a ROA for AS263008, maxLength 23. |
| Route object: RIR | 186.226.208.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 186.226.208.0/24 | No ROA covers it. Add a ROA for AS263008, maxLength 24. |
| Route object: RIR | 186.226.208.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 186.226.209.0/24 | No ROA covers it. Add a ROA for AS263008, maxLength 24. |
| Route object: RIR | 186.226.209.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 186.226.210.0/23 | No ROA covers it. Add a ROA for AS263008, maxLength 23. |
| Route object: RIR | 186.226.210.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 186.226.210.0/24 | No ROA covers it. Add a ROA for AS263008, maxLength 24. |
| Route object: RIR | 186.226.210.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 186.226.211.0/24 | No ROA covers it. Add a ROA for AS263008, maxLength 24. |
| Route object: RIR | 186.226.211.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 186.226.212.0/24 | No ROA covers it. Add a ROA for AS263008, maxLength 24. |
| Route object: RIR | 186.226.212.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 186.226.213.0/24 | No ROA covers it. Add a ROA for AS263008, maxLength 24. |
| Route object: RIR | 186.226.213.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 186.226.215.0/24 | No ROA covers it. Add a ROA for AS263008, maxLength 24. |
| Route object: RIR | 186.226.215.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 186.226.214.0/24 | No ROA covers it. Add a ROA for AS263008, maxLength 24. |
| Route object: RIR | 186.226.214.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS263008 whose prefix no peer sees AS263008 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 186.226.208.0/22 | RADB | No ROA |
| 186.226.212.0/22 | RADB | No ROA |
| 2804:9fc::/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.