Network · data from 2026-11-12
AS273854 AS273854 - TELEMAS SOCIEDAD ANONIMA
Registry name: AS273854 - TELEMAS SOCIEDAD ANONIMA, UY · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS273854, 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.
| 181.103.64.0/22 | Valid | Nonecovered by 181.103.64.0/20 | 670 100% |
| 181.103.68.0/22 | Valid | Nonecovered by 181.103.64.0/20 | 670 100% |
| 181.103.72.0/22 | Valid | Nonecovered by 181.103.64.0/20 | 670 100% |
| 181.103.76.0/22 | Valid | Nonecovered by 181.103.64.0/20 | 670 100% |
| 181.103.80.0/24 | Valid | Nonecovered by 181.103.80.0/20 | 670 100% |
| 181.103.81.0/24 | Valid | Nonecovered by 181.103.80.0/20 | 670 100% |
| 181.103.82.0/23 | Valid | Nonecovered by 181.103.80.0/20 | 670 100% |
| 181.103.84.0/22 | Valid | Nonecovered by 181.103.80.0/20 | 670 100% |
| 181.103.85.0/24 | Valid | Nonecovered by 181.103.80.0/20 | 670 100% |
| 181.103.86.0/23 | Valid | Nonecovered by 181.103.80.0/20 | 670 100% |
| 181.103.88.0/24 | Valid | Nonecovered by 181.103.80.0/20 | 670 100% |
| 2803:1550:200::/40 | Valid | Nonecovered by 2803:1550::/32 | 636 100% |
| 2803:1550:300::/40 | Valid | Nonecovered by 2803:1550::/32 | 636 100% |
| 2803:1550:400::/40 | Valid | Nonecovered by 2803:1550::/32 | 636 100% |
| 2803:1550:500::/40 | Valid | Nonecovered by 2803:1550::/32 | 635 100% |
AS-SET
AS273854 isn't in PeeringDB, where networks name their 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 19 are in fix.csv.
- Route object: none15
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 181.103.64.0/22 | No route object for it. A route object for 181.103.64.0/20 with origin AS273854 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273854 in the RIR database for the space. |
| Route object: none | 181.103.68.0/22 | No route object for it. A route object for 181.103.64.0/20 with origin AS273854 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273854 in the RIR database for the space. |
| Route object: none | 181.103.72.0/22 | No route object for it. A route object for 181.103.64.0/20 with origin AS273854 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273854 in the RIR database for the space. |
| Route object: none | 181.103.76.0/22 | No route object for it. A route object for 181.103.64.0/20 with origin AS273854 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273854 in the RIR database for the space. |
| Route object: none | 181.103.80.0/24 | No route object for it. A route object for 181.103.80.0/20 with origin AS273854 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273854 in the RIR database for the space. |
| Route object: none | 181.103.81.0/24 | No route object for it. A route object for 181.103.80.0/20 with origin AS273854 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273854 in the RIR database for the space. |
| Route object: none | 181.103.82.0/23 | No route object for it. A route object for 181.103.80.0/20 with origin AS273854 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273854 in the RIR database for the space. |
| Route object: none | 181.103.84.0/22 | No route object for it. A route object for 181.103.80.0/20 with origin AS273854 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273854 in the RIR database for the space. |
| Route object: none | 181.103.85.0/24 | No route object for it. A route object for 181.103.80.0/20 with origin AS273854 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273854 in the RIR database for the space. |
| Route object: none | 181.103.86.0/23 | No route object for it. A route object for 181.103.80.0/20 with origin AS273854 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273854 in the RIR database for the space. |
| Route object: none | 181.103.88.0/24 | No route object for it. A route object for 181.103.80.0/20 with origin AS273854 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273854 in the RIR database for the space. |
| Route object: none | 2803:1550:200::/40 | No route object for it. A route object for 2803:1550::/32 with origin AS273854 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273854 in the RIR database for the space. |
| Route object: none | 2803:1550:300::/40 | No route object for it. A route object for 2803:1550::/32 with origin AS273854 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273854 in the RIR database for the space. |
| Route object: none | 2803:1550:400::/40 | No route object for it. A route object for 2803:1550::/32 with origin AS273854 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273854 in the RIR database for the space. |
| Route object: none | 2803:1550:500::/40 | No route object for it. A route object for 2803:1550::/32 with origin AS273854 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273854 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS273854 whose prefix no peer sees AS273854 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 181.103.64.0/20 | LACNIC | Valid |
| 181.103.68.0/24 | LACNIC | Valid |
| 181.103.80.0/20 | LACNIC | Valid |
| 2803:1550::/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.