Network · data from 2026-11-12
AS269588 AS269588 - CELERIUM TELECOMUNICACOES
Registry name: AS269588 - CELERIUM TELECOMUNICACOES, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS269588, 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.
| 45.189.132.0/23 | No ROA | Other IRR onlyRADB | 672 100% |
| 45.189.133.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 45.189.132.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 2804:66e0::/33 | No ROA | Other IRR onlyRADB | 636 100% |
| 2804:66e0::/34 | No ROA | Other IRR onlyRADB | 636 100% |
| 2804:66e0:4000::/34 | No ROA | Other IRR onlyRADB | 636 100% |
AS-SET
AS269588 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 44 are in fix.csv.
- ROA: none6
- Route object: RIR6
- Route object: not announced32
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.189.132.0/23 | No ROA covers it. Add a ROA for AS269588, maxLength 23. |
| Route object: RIR | 45.189.132.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 45.189.133.0/24 | No ROA covers it. Add a ROA for AS269588, maxLength 24. |
| Route object: RIR | 45.189.133.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 45.189.132.0/24 | No ROA covers it. Add a ROA for AS269588, maxLength 24. |
| Route object: RIR | 45.189.132.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:66e0::/33 | No ROA covers it. Add a ROA for AS269588, maxLength 33. |
| Route object: RIR | 2804:66e0::/33 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:66e0::/34 | No ROA covers it. Add a ROA for AS269588, maxLength 34. |
| Route object: RIR | 2804:66e0::/34 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:66e0:4000::/34 | No ROA covers it. Add a ROA for AS269588, maxLength 34. |
| Route object: RIR | 2804:66e0:4000::/34 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS269588 whose prefix no peer sees AS269588 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.189.132.0/22 | RADB | No ROA |
| 45.189.134.0/23 | RADB | No ROA |
| 45.189.134.0/24 | RADB | No ROA |
| 45.189.135.0/24 | RADB | No ROA |
| 2804:66e0::/32 | RADB | No ROA |
| 2804:66e0::/35 | RADB | No ROA |
| 2804:66e0::/36 | RADB | No ROA |
| 2804:66e0:1000::/36 | RADB | No ROA |
| 2804:66e0:2000::/35 | RADB | No ROA |
| 2804:66e0:2000::/36 | RADB | No ROA |
| 2804:66e0:3000::/36 | RADB | No ROA |
| 2804:66e0:4000::/35 | RADB | No ROA |
| 2804:66e0:4000::/36 | RADB | No ROA |
| 2804:66e0:5000::/36 | RADB | No ROA |
| 2804:66e0:6000::/35 | RADB | No ROA |
| 2804:66e0:6000::/36 | RADB | No ROA |
| 2804:66e0:7000::/36 | RADB | No ROA |
| 2804:66e0:8000::/33 | RADB | No ROA |
| 2804:66e0:8000::/34 | RADB | No ROA |
| 2804:66e0:8000::/35 | RADB | No ROA |
| 2804:66e0:8000::/36 | RADB | No ROA |
| 2804:66e0:9000::/36 | RADB | No ROA |
| 2804:66e0:a000::/35 | RADB | No ROA |
| 2804:66e0:a000::/36 | RADB | No ROA |
| 2804:66e0:b000::/36 | RADB | No ROA |
| 2804:66e0:c000::/34 | RADB | No ROA |
| 2804:66e0:c000::/35 | RADB | No ROA |
| 2804:66e0:c000::/36 | RADB | No ROA |
| 2804:66e0:d000::/36 | RADB | No ROA |
| 2804:66e0:e000::/35 | RADB | No ROA |
| 2804:66e0:e000::/36 | RADB | No ROA |
| 2804:66e0:f000::/36 | RADB | 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.