bgpreport

Network · data from 2026-11-12

AS264350 AS264350 - Reboucas On Line Comunicacoes Ltda

Registry name: AS264350 - Reboucas On Line Comunicacoes Ltda, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264350, 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.

131.108.92.0/22 Valid Other IRR onlyALTDB, RADB 670 100% 67
131.108.94.0/23 Valid Other IRR onlyALTDB 670 100% 67
131.108.92.0/23 Valid Other IRR onlyALTDB 669 99% 67

AS-SET

AS264350 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 8 are in fix.csv.

  • Route object: RIR3
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: RIR131.108.92.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR131.108.94.0/23Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
Route object: RIR131.108.92.0/23Route object only in ALTDB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

131.108.92.0/24ALTDB, RADBValid
131.108.93.0/24ALTDB, RADBValid
131.108.94.0/24ALTDB, RADBValid
131.108.95.0/24ALTDB, RADBValid
2804:1d24::/32ALTDB, RADBValid

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.