Network · data from 2026-11-12
AS52425 RELTID CV
Registry name: AS52425 - RELTID CV S.A., AR · PeeringDB
9IPv4 routes
100.0% RPKI valid · 33.3% with a route object
6IPv6 routes
100.0% RPKI valid · 0.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
12 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
3Route objects not announced
registered with origin AS52425, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS52425, 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.92.104.0/24 | Valid | Nonecovered by 190.92.104.0/22 | 667 99% |
| 190.92.105.0/24 | Valid | Nonecovered by 190.92.104.0/22 | 667 99% |
| 190.92.106.0/24 | Valid | Nonecovered by 190.92.104.0/22 | 667 99% |
| 190.92.107.0/24 | Valid | Nonecovered by 190.92.104.0/22 | 667 99% |
| 190.92.108.0/24 | Valid | Nonecovered by 190.92.108.0/23 | 667 99% |
| 190.92.109.0/24 | Valid | Nonecovered by 190.92.108.0/23 | 667 99% |
| 2803:be00:2000::/36 | Valid | Nonecovered by 2803:be00::/32 | 636 100% |
| 2803:be00::/36 | Valid | Nonecovered by 2803:be00::/32 | 633 100% |
| 2803:be00:200::/42 | Valid | Nonecovered by 2803:be00::/32 | 633 100% |
| 2803:be00:240::/42 | Valid | Nonecovered by 2803:be00::/32 | 633 100% |
| 2803:be00:280::/42 | Valid | Nonecovered by 2803:be00::/32 | 633 100% |
| 2803:be00:4000::/36 | Valid | Nonecovered by 2803:be00::/32 | 633 100% |
| 181.191.27.0/24 | Valid | RIR databaseLACNIC | 672 100% |
| 181.191.25.0/24 | Valid | RIR databaseLACNIC | 671 100% |
| 190.92.110.0/24 | Valid | RIR databaseLACNIC | 667 99% |
AS-SET
AS52425'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: none12
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 190.92.104.0/24 | No route object for it. A route object for 190.92.104.0/22 with origin AS52425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52425 in the RIR database for the space. |
| Route object: none | 190.92.105.0/24 | No route object for it. A route object for 190.92.104.0/22 with origin AS52425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52425 in the RIR database for the space. |
| Route object: none | 190.92.106.0/24 | No route object for it. A route object for 190.92.104.0/22 with origin AS52425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52425 in the RIR database for the space. |
| Route object: none | 190.92.107.0/24 | No route object for it. A route object for 190.92.104.0/22 with origin AS52425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52425 in the RIR database for the space. |
| Route object: none | 190.92.108.0/24 | No route object for it. A route object for 190.92.108.0/23 with origin AS52425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52425 in the RIR database for the space. |
| Route object: none | 190.92.109.0/24 | No route object for it. A route object for 190.92.108.0/23 with origin AS52425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52425 in the RIR database for the space. |
| Route object: none | 2803:be00:2000::/36 | No route object for it. A route object for 2803:be00::/32 with origin AS52425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52425 in the RIR database for the space. |
| Route object: none | 2803:be00::/36 | No route object for it. A route object for 2803:be00::/32 with origin AS52425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52425 in the RIR database for the space. |
| Route object: none | 2803:be00:200::/42 | No route object for it. A route object for 2803:be00::/32 with origin AS52425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52425 in the RIR database for the space. |
| Route object: none | 2803:be00:240::/42 | No route object for it. A route object for 2803:be00::/32 with origin AS52425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52425 in the RIR database for the space. |
| Route object: none | 2803:be00:280::/42 | No route object for it. A route object for 2803:be00::/32 with origin AS52425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52425 in the RIR database for the space. |
| Route object: none | 2803:be00:4000::/36 | No route object for it. A route object for 2803:be00::/32 with origin AS52425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52425 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS52425 whose prefix no peer sees AS52425 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 190.92.104.0/22 | LACNIC | Valid |
| 190.92.108.0/23 | LACNIC | Valid |
| 2803:be00::/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.