Network · data from 2026-11-12
AS264452 R & B Serviços de Telecomunicações
Registry name: AS264452 - R & B Servicos de Telecomunicacoes Ltda., BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS264452, 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.
| 132.255.48.0/24 | No ROA | Nonecovered by 132.255.48.0/22 | 665 99% |
| 132.255.48.0/22 | No ROA | Other IRR onlyRADB | 672 100% |
| 2804:1ee4::/32 | No ROA | Other IRR onlyRADB | 636 100% |
AS-SET
AS264452'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: none3
- Route object: none1
- Route object: RIR2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 132.255.48.0/24 | No ROA covers it. Add a ROA for AS264452, maxLength 24. |
| Route object: none | 132.255.48.0/24 | No route object for it. A route object for 132.255.48.0/22 with origin AS264452 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264452 in the RIR database for the space. |
| ROA: none | 132.255.48.0/22 | No ROA covers it. Add a ROA for AS264452, maxLength 22. |
| Route object: RIR | 132.255.48.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:1ee4::/32 | No ROA covers it. Add a ROA for AS264452, maxLength 32. |
| Route object: RIR | 2804:1ee4::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS264452 whose prefix no peer sees AS264452 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 132.55.48.0/22 | RADB | No ROA |
| 2804:1ee4:fe00::/40 | 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.