Network · data from 2026-11-12
AS263777 COOPERATIVA TELEFONICA Y OSPA DE TOSTADO
Registry name: AS263777 - COOPERATIVA TELEFONICA Y OSPA DE TOSTADO LDA., AR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS263777, 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.
| 138.204.6.0/24 | Valid | Nonecovered by 138.204.4.0/22 | 672 100% |
| 138.204.7.0/24 | Valid | Nonecovered by 138.204.4.0/22 | 672 100% |
| 168.227.254.0/24 | Valid | Nonecovered by 168.227.252.0/22 | 672 100% |
| 168.227.255.0/24 | Valid | Nonecovered by 168.227.252.0/22 | 672 100% |
| 170.239.33.0/24 | Valid | Nonecovered by 170.239.32.0/22 | 672 100% |
| 170.239.34.0/24 | Valid | Nonecovered by 170.239.32.0/22 | 672 100% |
| 170.239.35.0/24 | Valid | Nonecovered by 170.239.32.0/22 | 672 100% |
| 190.227.188.0/23 | Valid | Nonecovered by 190.227.188.0/22 | 671 100% |
| 190.228.44.0/24 | Valid | Nonecovered by 190.228.44.0/23 | 671 100% |
| 190.228.45.0/24 | Valid | Nonecovered by 190.228.44.0/23 | 671 100% |
| 138.204.4.0/23 | Valid | Nonecovered by 138.204.4.0/22 | 670 100% |
| 170.239.32.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 168.227.252.0/22 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 170.239.32.0/22 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 190.122.94.0/24 | Valid | RIR databaseALTDB, LACNIC | 671 100% |
| 190.227.188.0/22 | Valid | RIR databaseLACNIC | 671 100% |
| 190.228.44.0/23 | Valid | RIR databaseLACNIC | 671 100% |
| 138.204.4.0/22 | Valid | RIR databaseLACNIC, RADB | 670 100% |
AS-SET
AS263777'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 17 are in fix.csv.
- Route object: none11
- Route object: RIR1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 138.204.6.0/24 | No route object for it. A route object for 138.204.4.0/22 with origin AS263777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263777 in the RIR database for the space. |
| Route object: none | 138.204.7.0/24 | No route object for it. A route object for 138.204.4.0/22 with origin AS263777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263777 in the RIR database for the space. |
| Route object: none | 168.227.254.0/24 | No route object for it. A route object for 168.227.252.0/22 with origin AS263777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263777 in the RIR database for the space. |
| Route object: none | 168.227.255.0/24 | No route object for it. A route object for 168.227.252.0/22 with origin AS263777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263777 in the RIR database for the space. |
| Route object: none | 170.239.33.0/24 | No route object for it. A route object for 170.239.32.0/22 with origin AS263777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263777 in the RIR database for the space. |
| Route object: none | 170.239.34.0/24 | No route object for it. A route object for 170.239.32.0/22 with origin AS263777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263777 in the RIR database for the space. |
| Route object: none | 170.239.35.0/24 | No route object for it. A route object for 170.239.32.0/22 with origin AS263777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263777 in the RIR database for the space. |
| Route object: none | 190.227.188.0/23 | No route object for it. A route object for 190.227.188.0/22 with origin AS263777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263777 in the RIR database for the space. |
| Route object: none | 190.228.44.0/24 | No route object for it. A route object for 190.228.44.0/23 with origin AS263777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263777 in the RIR database for the space. |
| Route object: none | 190.228.45.0/24 | No route object for it. A route object for 190.228.44.0/23 with origin AS263777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263777 in the RIR database for the space. |
| Route object: none | 138.204.4.0/23 | No route object for it. A route object for 138.204.4.0/22 with origin AS263777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263777 in the RIR database for the space. |
| Route object: RIR | 170.239.32.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS263777 whose prefix no peer sees AS263777 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 138.204.4.0/24 | RADB | Valid |
| 168.227.252.0/24 | RADB | Valid |
| 2802:2240::/32 | RADB | No ROA |
| 2803:2240::/32 | LACNIC, RADB | Valid |
| 2803:2240::/48 | 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.