Network · data from 2026-11-12
AS267453 AS267453 - Neticabo Telecom Ltda - ME
Registry name: AS267453 - Neticabo Telecom Ltda - ME, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS267453, 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.
| 181.191.48.0/22 | No ROA | Other IRR onlyTC | 669 99% |
| 181.191.48.0/23 | No ROA | Other IRR onlyTC | 2 0%low visibility |
| 181.191.48.0/24 | No ROA | Other IRR onlyTC | 2 0%low visibility |
| 181.191.49.0/24 | No ROA | Other IRR onlyTC | 2 0%low visibility |
| 181.191.50.0/23 | No ROA | Other IRR onlyTC | 2 0%low visibility |
| 181.191.50.0/24 | No ROA | Other IRR onlyTC | 2 0%low visibility |
| 181.191.51.0/24 | No ROA | Other IRR onlyTC | 2 0%low visibility |
AS-SET
AS267453 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 19 are in fix.csv.
- ROA: none7
- Route object: RIR7
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 181.191.48.0/22 | No ROA covers it. Add a ROA for AS267453, maxLength 22. |
| Route object: RIR | 181.191.48.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 181.191.48.0/23 | No ROA covers it. Add a ROA for AS267453, maxLength 23. |
| Route object: RIR | 181.191.48.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 181.191.48.0/24 | No ROA covers it. Add a ROA for AS267453, maxLength 24. |
| Route object: RIR | 181.191.48.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 181.191.49.0/24 | No ROA covers it. Add a ROA for AS267453, maxLength 24. |
| Route object: RIR | 181.191.49.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 181.191.50.0/23 | No ROA covers it. Add a ROA for AS267453, maxLength 23. |
| Route object: RIR | 181.191.50.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 181.191.50.0/24 | No ROA covers it. Add a ROA for AS267453, maxLength 24. |
| Route object: RIR | 181.191.50.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 181.191.51.0/24 | No ROA covers it. Add a ROA for AS267453, maxLength 24. |
| Route object: RIR | 181.191.51.0/24 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS267453 whose prefix no peer sees AS267453 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 179.48.200.0/22 | RADB | No ROA |
| 191.36.253.0/24 | RADB | No ROA |
| 191.36.255.0/24 | RADB | No ROA |
| 2804:41bc::/32 | TC | No ROA |
| 2804:41bc::/36 | 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.