Network · data from 2026-11-12
AS52356 R&H International Telecom Services
Registry name: AS52356 - R&H International Telecom Services SA., CR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS52356, 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.14.152.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 190.14.153.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 190.14.154.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 190.14.155.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 181.41.154.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 2803:b140::/32 | Valid | RIR databaseLACNIC, RADB | 632 99% |
| 190.14.152.0/22 | Valid | RIR databaseLACNIC, RADB | 5 1%low visibility |
AS-SET
AS52356'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 5 are in fix.csv.
- Route object: RIR4
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 190.14.152.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.14.153.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.14.154.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.14.155.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS52356 whose prefix no peer sees AS52356 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 196.53.69.0/24 | RADB | No ROA |
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.