Network · data from 2026-11-12
AS52894 AS52894 - Klisa Net Telecomunicacoes e Multimidia LTDA ME
Registry name: AS52894 - Klisa Net Telecomunicacoes e Multimidia LTDA ME, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS52894, 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.
| 186.250.164.0/22 | No ROA | Other IRR onlyRADB | 671 100% |
| 186.250.164.0/23 | No ROA | Other IRR onlyRADB | 671 100% |
AS-SET
AS52894 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 7 are in fix.csv.
- ROA: none2
- Route object: RIR2
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 186.250.164.0/22 | No ROA covers it. Add a ROA for AS52894, maxLength 22. |
| Route object: RIR | 186.250.164.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 186.250.164.0/23 | No ROA covers it. Add a ROA for AS52894, maxLength 23. |
| Route object: RIR | 186.250.164.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS52894 whose prefix no peer sees AS52894 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 186.250.165.0/24 | RADB | No ROA |
| 186.250.166.0/24 | RADB | No ROA |
| 2804:a90::/32 | 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.