bgpreport

Network · data from 2026-11-12

AS28194 R & F BASSAN COMÉRCIO SERVIÇOS E SISTEMA

Registry name: AS28194 - R & F BASSAN COMERCIO SERVICOS E SISTEMA LTDA - ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28194, 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:34b4::/32 No ROA Other origin only 362 57% 67
187.33.63.0/24 Valid Other IRR onlyALTDB, RADB 671 100% 67
187.33.56.0/21 Valid Other IRR onlyALTDB, RADB 670 100% 66
187.33.56.0/22 Valid Other IRR onlyALTDB 669 99% 66
187.33.60.0/22 Valid Other IRR onlyALTDB 669 99% 66
2804:4390::/33 Valid Other IRR onlyALTDB 635 100% 67
2804:4390:8000::/33 Valid Other IRR onlyALTDB 635 100% 67
2804:4390::/32 Valid Other IRR onlyALTDB, RADB 629 99% 67

AS-SET

AS28194'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 24 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: RIR7
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: none2804:34b4::/32No ROA covers it. Add a ROA for AS28194, maxLength 32.362 of 636
Route object: none2804:34b4::/32Route objects for it name AS265474. Add a route object with origin AS28194 in the RIR database for the space.362 of 636
Route object: RIR187.33.63.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.33.56.0/21Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR187.33.56.0/22Route object only in ALTDB. Add it in the RIR database for the space.669 of 673
Route object: RIR187.33.60.0/22Route object only in ALTDB. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:4390::/33Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:4390:8000::/33Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:4390::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.629 of 636

Route objects not announced

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

187.33.56.0/23ALTDBValid
187.33.56.0/24ALTDB, RADBValid
187.33.57.0/24ALTDBValid
187.33.58.0/23ALTDBValid
187.33.58.0/24ALTDBValid
187.33.59.0/24ALTDBValid
187.33.60.0/23ALTDBValid
187.33.60.0/24ALTDBValid
187.33.61.0/24ALTDBValid
187.33.62.0/23ALTDBValid
187.33.62.0/24ALTDBValid
2804:4390::/34ALTDBValid
2804:4390:4000::/34ALTDBValid
2804:4390:8000::/34ALTDBValid
2804:4390:c000::/34ALTDBValid

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.