Network · data from 2026-11-12
AS269359 CANAA TELECOMUNICAÇÕES LTDA - ME
Registry name: AS269359 - CANAA TELECOMUNICACOES LTDA - ME, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS269359, 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.184.68.0/22 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 45.184.68.0/23 | Valid | Other IRR onlyTC | 671 100% |
| 45.184.70.0/23 | Valid | Other IRR onlyTC | 671 100% |
| 45.230.84.0/23 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 168.194.248.0/22 | Valid | Other IRR onlyRADB, TC | 667 99% |
| 168.194.248.0/23 | Valid | Other IRR onlyTC | 667 99% |
| 168.194.248.0/24 | Valid | Other IRR onlyTC | 667 99% |
| 168.194.249.0/24 | Valid | Other IRR onlyALTDB, TC | 667 99% |
| 168.194.250.0/23 | Valid | Other IRR onlyTC | 667 99% |
| 168.194.250.0/24 | Valid | Other IRR onlyTC | 667 99% |
| 168.194.251.0/24 | Valid | Other IRR onlyTC | 667 99% |
| 45.184.69.0/24 | Valid | Other IRR onlyTC | 664 99% |
| 45.184.68.0/24 | Valid | Other IRR onlyTC | 663 99% |
| 45.184.70.0/24 | Valid | Other IRR onlyTC | 663 99% |
| 45.184.71.0/24 | Valid | Other IRR onlyTC | 663 99% |
| 45.230.84.0/24 | Valid | Other IRR onlyTC | 663 99% |
| 45.230.85.0/24 | Valid | Other IRR onlyTC | 662 98% |
| 2804:6368::/33 | Valid | Other IRR onlyTC | 634 100% |
| 2804:6368::/34 | Valid | Other IRR onlyTC | 634 100% |
| 2804:6368::/36 | Valid | Other IRR onlyTC | 634 100% |
| 2804:6368:4000::/34 | Valid | Other IRR onlyTC | 634 100% |
| 2804:6368:8000::/33 | Valid | Other IRR onlyTC | 629 99% |
| 2804:6368::/42 | Valid | Other IRR onlyTC | 32 5%low visibility |
| 2804:6368:80::/42 | Valid | Other IRR onlyTC | 32 5%low visibility |
AS-SET
PeeringDB's irr_as_set for AS269359: AS269359:AS-CANAA-TELECOM. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS269359 isn't in the set, or no route object for AS269359 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS269359 in it | Not covered |
|---|---|---|---|---|---|
| AS269359:AS-CANAA-TELECOM | TC | 6 | 5 | Yes | 0 |
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 29 are in fix.csv.
- Route object: RIR24
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 45.184.68.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.184.68.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.184.70.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.230.84.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.194.248.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.194.248.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.194.248.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.194.249.0/24 | Route object only in ALTDB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.194.250.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.194.250.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.194.251.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.184.69.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.184.68.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.184.70.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.184.71.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.230.84.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.230.85.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6368::/33 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6368::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6368::/36 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6368:4000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6368:8000::/33 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6368::/42 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6368:80::/42 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS269359 whose prefix no peer sees AS269359 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2804:6368::/32 | RADB, TC | No ROA |
| 2804:6368:40::/42 | TC | Valid |
| 2804:6368:1000::/36 | TC | Valid |
| 2804:6368:8000::/34 | TC | Valid |
| 2804:6368:c000::/34 | TC | Valid |
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.