bgpreport

Network · data from 2026-11-12

AS272789 AS272789 - Gambero & Vieira Ltda

Registry name: AS272789 - Gambero & Vieira Ltda, BR · not in PeeringDB

0IPv4 routes
2IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
2No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
29Route objects not announced registered with origin AS272789, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS272789, 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.
2804:88b8:8000::/33 No ROA Other IRR onlyRADB 636 100% 67
2804:88b8::/32 No ROA Other IRR onlyRADB 632 99% 67

AS-SET

AS272789 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 33 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced29
ChangePrefix or setDetailFull-table peers
ROA: none2804:88b8:8000::/33No ROA covers it. Add a ROA for AS272789, maxLength 33.636 of 636
Route object: RIR2804:88b8:8000::/33Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2804:88b8::/32No ROA covers it. Add a ROA for AS272789, maxLength 32.632 of 636
Route object: RIR2804:88b8::/32Route object only in RADB. Add it in the RIR database for the space.632 of 636

Route objects not announced

Route objects with origin AS272789 whose prefix no peer sees AS272789 announce. Many are kept on purpose (backup routes, space announced only in some places).

2804:88b8::/33RADBNo ROA
2804:88b8::/34RADBNo ROA
2804:88b8::/35RADBNo ROA
2804:88b8::/36RADBNo ROA
2804:88b8:1000::/36RADBNo ROA
2804:88b8:2000::/35RADBNo ROA
2804:88b8:2000::/36RADBNo ROA
2804:88b8:3000::/36RADBNo ROA
2804:88b8:4000::/34RADBNo ROA
2804:88b8:4000::/35RADBNo ROA
2804:88b8:4000::/36RADBNo ROA
2804:88b8:5000::/36RADBNo ROA
2804:88b8:6000::/35RADBNo ROA
2804:88b8:6000::/36RADBNo ROA
2804:88b8:7000::/36RADBNo ROA
2804:88b8:8000::/34RADBNo ROA
2804:88b8:8000::/35RADBNo ROA
2804:88b8:8000::/36RADBNo ROA
2804:88b8:9000::/36RADBNo ROA
2804:88b8:a000::/35RADBNo ROA
2804:88b8:a000::/36RADBNo ROA
2804:88b8:b000::/36RADBNo ROA
2804:88b8:c000::/34RADBNo ROA
2804:88b8:c000::/35RADBNo ROA
2804:88b8:c000::/36RADBNo ROA
2804:88b8:d000::/36RADBNo ROA
2804:88b8:e000::/35RADBNo ROA
2804:88b8:e000::/36RADBNo ROA
2804:88b8:f000::/36RADBNo 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.