Network · data from 2026-11-12
AS265768 ELEVATE
Registry name: AS265768 - ELEVATE S.R.L., AR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS265768, 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.
| 131.196.2.0/24 | Valid | Nonecovered by 131.196.0.0/22 | 673 100% |
| 45.173.41.0/24 | Valid | Nonecovered by 45.173.40.0/22 | 671 100% |
| 45.173.42.0/24 | Valid | Nonecovered by 45.173.40.0/22 | 671 100% |
| 131.196.0.0/24 | Valid | Nonecovered by 131.196.0.0/22 | 671 100% |
| 131.196.1.0/24 | Valid | Nonecovered by 131.196.0.0/22 | 671 100% |
| 131.196.3.0/24 | Valid | Nonecovered by 131.196.0.0/22 | 670 100% |
| 45.173.43.0/24 | Valid | Nonecovered by 45.173.40.0/22 | 297 44% |
| 2803:a7c0:2::/48 | Valid | RIR databaseLACNIC | 636 100% |
AS-SET
AS265768'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 11 are in fix.csv.
- Route object: none7
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 131.196.2.0/24 | No route object for it. A route object for 131.196.0.0/22 with origin AS265768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265768 in the RIR database for the space. |
| Route object: none | 45.173.41.0/24 | No route object for it. A route object for 45.173.40.0/22 with origin AS265768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265768 in the RIR database for the space. |
| Route object: none | 45.173.42.0/24 | No route object for it. A route object for 45.173.40.0/22 with origin AS265768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265768 in the RIR database for the space. |
| Route object: none | 131.196.0.0/24 | No route object for it. A route object for 131.196.0.0/22 with origin AS265768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265768 in the RIR database for the space. |
| Route object: none | 131.196.1.0/24 | No route object for it. A route object for 131.196.0.0/22 with origin AS265768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265768 in the RIR database for the space. |
| Route object: none | 131.196.3.0/24 | No route object for it. A route object for 131.196.0.0/22 with origin AS265768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265768 in the RIR database for the space. |
| Route object: none | 45.173.43.0/24 | No route object for it. A route object for 45.173.40.0/22 with origin AS265768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265768 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS265768 whose prefix no peer sees AS265768 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.173.40.0/22 | LACNIC | Valid |
| 131.196.0.0/22 | LACNIC | Valid |
| 190.112.32.0/21 | LACNIC | Valid |
| 2803:94c0::/32 | LACNIC | 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.