Network · data from 2026-11-12
AS52663 Turbo BSB Tecnologias em Rede
Registry name: AS52663 - Turbo BSB Tecnologias em Rede Ltda., BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS52663, 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.67.136.0/22 | No ROA | Nonecovered by 177.67.136.0/21 | 671 100% |
| 177.67.140.0/22 | No ROA | Nonecovered by 177.67.136.0/21 | 670 100% |
| 2804:49cc::/32 | No ROA | Other origin only | 634 100% |
| 177.67.136.0/21 | No ROA | Other IRR onlyRADB | 671 100% |
AS-SET
AS52663'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 8 are in fix.csv.
- ROA: none4
- Route object: none3
- Route object: RIR1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 177.67.136.0/22 | No ROA covers it. Add a ROA for AS52663, maxLength 22. |
| Route object: none | 177.67.136.0/22 | No route object for it. A route object for 177.67.136.0/21 with origin AS52663 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52663 in the RIR database for the space. |
| ROA: none | 177.67.140.0/22 | No ROA covers it. Add a ROA for AS52663, maxLength 22. |
| Route object: none | 177.67.140.0/22 | No route object for it. A route object for 177.67.136.0/21 with origin AS52663 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52663 in the RIR database for the space. |
| ROA: none | 2804:49cc::/32 | No ROA covers it. Add a ROA for AS52663, maxLength 32. |
| Route object: none | 2804:49cc::/32 | Route objects for it name AS270429. Add a route object with origin AS52663 in the RIR database for the space. |
| ROA: none | 177.67.136.0/21 | No ROA covers it. Add a ROA for AS52663, maxLength 21. |
| Route object: RIR | 177.67.136.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS52663 is announced.
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.