Network · data from 2026-11-12
AS263698 TRANSDATELECOM
Registry name: AS263698 - TRANSDATELECOM S.A, CR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS263698, 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.
| 191.102.37.0/24 | Valid | Nonecovered by 191.102.36.0/22 | 669 99% |
| 191.102.36.0/24 | Valid | Nonecovered by 191.102.36.0/22 | 663 99% |
| 191.102.38.0/24 | Valid | Nonecovered by 191.102.36.0/22 | 663 99% |
| 191.102.39.0/24 | Valid | Nonecovered by 191.102.36.0/22 | 663 99% |
| 190.113.84.0/24 | Valid | Nonecovered by 190.113.84.0/23 | 659 98% |
| 190.113.85.0/24 | Valid | Nonecovered by 190.113.84.0/23 | 659 98% |
AS-SET
AS263698'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 10 are in fix.csv.
- Route object: none6
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 191.102.37.0/24 | No route object for it. A route object for 191.102.36.0/22 with origin AS263698 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263698 in the RIR database for the space. |
| Route object: none | 191.102.36.0/24 | No route object for it. A route object for 191.102.36.0/22 with origin AS263698 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263698 in the RIR database for the space. |
| Route object: none | 191.102.38.0/24 | No route object for it. A route object for 191.102.36.0/22 with origin AS263698 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263698 in the RIR database for the space. |
| Route object: none | 191.102.39.0/24 | No route object for it. A route object for 191.102.36.0/22 with origin AS263698 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263698 in the RIR database for the space. |
| Route object: none | 190.113.84.0/24 | No route object for it. A route object for 190.113.84.0/23 with origin AS263698 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263698 in the RIR database for the space. |
| Route object: none | 190.113.85.0/24 | No route object for it. A route object for 190.113.84.0/23 with origin AS263698 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263698 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS263698 whose prefix no peer sees AS263698 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 190.113.84.0/23 | LACNIC | Valid |
| 190.113.87.0/24 | RADB | No ROA |
| 191.102.36.0/22 | LACNIC, RADB | Valid |
| 2803:aa80::/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.