Network · data from 2026-11-12
AS262938 AS262938 - B3A COMUNICACAO LTDA
Registry name: AS262938 - B3A COMUNICACAO LTDA, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS262938, 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.129.196.0/24 | No ROA | Nonecovered by 177.129.196.0/22 | 670 100% |
| 177.129.198.0/24 | No ROA | Nonecovered by 177.129.196.0/22 | 670 100% |
| 177.129.199.0/24 | No ROA | Nonecovered by 177.129.196.0/22 | 670 100% |
| 177.129.196.0/22 | No ROA | Other IRR onlyRADB | 670 100% |
| 2804:e2c::/32 | No ROA | Other IRR onlyRADB | 635 100% |
AS-SET
AS262938 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 12 are in fix.csv.
- ROA: none5
- Route object: none3
- Route object: RIR2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 177.129.196.0/24 | No ROA covers it. Add a ROA for AS262938, maxLength 24. |
| Route object: none | 177.129.196.0/24 | No route object for it. A route object for 177.129.196.0/22 with origin AS262938 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262938 in the RIR database for the space. |
| ROA: none | 177.129.198.0/24 | No ROA covers it. Add a ROA for AS262938, maxLength 24. |
| Route object: none | 177.129.198.0/24 | No route object for it. A route object for 177.129.196.0/22 with origin AS262938 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262938 in the RIR database for the space. |
| ROA: none | 177.129.199.0/24 | No ROA covers it. Add a ROA for AS262938, maxLength 24. |
| Route object: none | 177.129.199.0/24 | No route object for it. A route object for 177.129.196.0/22 with origin AS262938 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262938 in the RIR database for the space. |
| ROA: none | 177.129.196.0/22 | No ROA covers it. Add a ROA for AS262938, maxLength 22. |
| Route object: RIR | 177.129.196.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:e2c::/32 | No ROA covers it. Add a ROA for AS262938, maxLength 32. |
| Route object: RIR | 2804:e2c::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS262938 whose prefix no peer sees AS262938 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2804:e2c::/33 | RADB | No ROA |
| 2804:e2c:8000::/33 | 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.