Network · data from 2026-11-12
AS52495 Cotel Ltda.
Registry name: AS52495 - Cotel Ltda., BO · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS52495, 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.
| 190.103.64.0/22 | Valid | Nonecovered by 190.103.64.0/21 | 666 99% |
| 190.103.72.0/22 | Valid | Nonecovered by 190.103.72.0/21 | 666 99% |
| 190.109.224.0/21 | Valid | Nonecovered by 190.109.224.0/20 | 666 99% |
| 190.109.240.0/21 | Valid | Nonecovered by 190.109.240.0/20 | 666 99% |
| 190.103.68.0/22 | Valid | Other IRR onlyRADB | 666 99% |
| 190.103.76.0/22 | Valid | Other IRR onlyRADB | 666 99% |
| 190.109.232.0/21 | Valid | Other IRR onlyRADB | 666 99% |
| 190.109.248.0/21 | Valid | Other IRR onlyRADB | 666 99% |
AS-SET
AS52495'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 15 are in fix.csv.
- Route object: none4
- Route object: RIR4
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 190.103.64.0/22 | No route object for it. A route object for 190.103.64.0/21 with origin AS52495 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52495 in the RIR database for the space. |
| Route object: none | 190.103.72.0/22 | No route object for it. A route object for 190.103.72.0/21 with origin AS52495 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52495 in the RIR database for the space. |
| Route object: none | 190.109.224.0/21 | No route object for it. A route object for 190.109.224.0/20 with origin AS52495 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52495 in the RIR database for the space. |
| Route object: none | 190.109.240.0/21 | No route object for it. A route object for 190.109.240.0/20 with origin AS52495 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52495 in the RIR database for the space. |
| Route object: RIR | 190.103.68.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.103.76.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.109.232.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.109.248.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS52495 whose prefix no peer sees AS52495 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 190.103.64.0/20 | LACNIC, RADB | Valid |
| 190.103.64.0/21 | RADB | Valid |
| 190.103.72.0/21 | RADB | Valid |
| 190.109.224.0/19 | LACNIC, RADB | Valid |
| 190.109.224.0/20 | RADB | Valid |
| 190.109.240.0/20 | RADB | Valid |
| 2803:fa00::/32 | LACNIC, RADB | 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.