Network · data from 2026-11-12
AS262648 BRAVA TELECOMUNICACOES PONTES E LACERDA
Registry name: AS262648 - BRAVA TELECOMUNICACOES PONTES E LACERDA LTDA - EPP, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS262648, 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.87.56.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 177.87.61.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 177.87.58.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 177.87.59.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 177.87.60.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 177.87.62.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 2804:76c::/32 | No ROA | Other IRR onlyRADB | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS262648: AS-262648. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS262648 isn't in the set, or no route object for AS262648 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS262648 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-262648 | In no IRR database read today. | |||||
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 20 are in fix.csv.
- ROA: none7
- Route object: RIR7
- AS-SET: not found1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 177.87.56.0/24 | No ROA covers it. Add a ROA for AS262648, maxLength 24. |
| Route object: RIR | 177.87.56.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 177.87.61.0/24 | No ROA covers it. Add a ROA for AS262648, maxLength 24. |
| Route object: RIR | 177.87.61.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 177.87.58.0/24 | No ROA covers it. Add a ROA for AS262648, maxLength 24. |
| Route object: RIR | 177.87.58.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 177.87.59.0/24 | No ROA covers it. Add a ROA for AS262648, maxLength 24. |
| Route object: RIR | 177.87.59.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 177.87.60.0/24 | No ROA covers it. Add a ROA for AS262648, maxLength 24. |
| Route object: RIR | 177.87.60.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 177.87.62.0/24 | No ROA covers it. Add a ROA for AS262648, maxLength 24. |
| Route object: RIR | 177.87.62.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:76c::/32 | No ROA covers it. Add a ROA for AS262648, maxLength 32. |
| Route object: RIR | 2804:76c::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: not found | AS-262648 | PeeringDB names AS-262648; no IRR database read has it. |
Route objects not announced
Route objects with origin AS262648 whose prefix no peer sees AS262648 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 177.87.56.0/21 | RADB | No ROA |
| 177.87.57.0/24 | RADB | No ROA |
| 177.87.63.0/24 | ALTDB, RADB | No ROA |
| 2804:76c::/39 | RADB | No ROA |
| 2804:76c:200::/39 | 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.