Network · data from 2026-11-12
AS52624 AS52624 - WEB TELECOMUNICACOES LTDA
Registry name: AS52624 - WEB TELECOMUNICACOES LTDA, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS52624, 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.
| 177.124.140.0/22 | No ROA | Other IRR onlyRADB, TC | 672 100% |
| 186.251.92.0/22 | No ROA | Other IRR onlyRADB, TC | 672 100% |
| 177.124.142.0/23 | No ROA | Other IRR onlyRADB | 121 18% |
| 186.251.92.0/23 | No ROA | Other IRR onlyRADB | 121 18% |
| 186.251.94.0/23 | No ROA | Other IRR onlyRADB | 121 18% |
| 177.124.140.0/23 | No ROA | Other IRR onlyRADB | 120 18% |
AS-SET
AS52624 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 22 are in fix.csv.
- ROA: none6
- Route object: RIR6
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 177.124.140.0/22 | No ROA covers it. Add a ROA for AS52624, maxLength 22. |
| Route object: RIR | 177.124.140.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 186.251.92.0/22 | No ROA covers it. Add a ROA for AS52624, maxLength 22. |
| Route object: RIR | 186.251.92.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 177.124.142.0/23 | No ROA covers it. Add a ROA for AS52624, maxLength 23. |
| Route object: RIR | 177.124.142.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 186.251.92.0/23 | No ROA covers it. Add a ROA for AS52624, maxLength 23. |
| Route object: RIR | 186.251.92.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 186.251.94.0/23 | No ROA covers it. Add a ROA for AS52624, maxLength 23. |
| Route object: RIR | 186.251.94.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 177.124.140.0/23 | No ROA covers it. Add a ROA for AS52624, maxLength 23. |
| Route object: RIR | 177.124.140.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS52624 whose prefix no peer sees AS52624 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 177.124.140.0/24 | RADB | No ROA |
| 177.124.141.0/24 | RADB | No ROA |
| 177.124.142.0/24 | RADB | No ROA |
| 177.124.142.128/25 | RADB | No ROA |
| 177.124.143.0/24 | RADB | No ROA |
| 186.251.92.0/24 | RADB | No ROA |
| 186.251.93.0/24 | RADB | No ROA |
| 186.251.94.0/24 | ALTDB, RADB | No ROA |
| 186.251.95.0/24 | RADB | No ROA |
| 2804:d68::/32 | RADB, TC | 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.