Medical devices, healthcare technology and the business of care
FDA RECALL RECORD · Z-0324-2027

VeriSeq Onsite Server V2 REF: 20047000 Recall

VeriSeq Onsite Server V2 REF: 20047000

FDA recall Class II

Ongoing

FDA lists this Class II recall for VeriSeq Onsite Server V2 REF: 20047000. Review the affected identifiers, reported reason and manufacturer instructions below.

Recall at a glance

Recall number
Z-0324-2027
Recall classification
Class II
Enforcement status
Ongoing
Initiation date
May 8, 2024
FDA report date
Nov 11, 2026
Quantity in commerce
201 units
Distribution
See key details
FDA cause
Labeling design

What is being recalled?

VeriSeq Onsite Server V2 REF: 20047000

Affected model & UDI checker

Search the exact identifiers published for Z-0324-2027.

The lookup covers structured identifiers listed on this page. A full UDI may also contain lot or serial information; a GTIN match alone does not check those conditions.

Affected products

Model / catalog numberProductLot scope reportedUDI / GTIN
20047000VeriSeq Onsite Server V2 REF: 20047000Check source noticeNot specified
FDA code information

All Lots/UDI: N/A

View the original FDA recall notice

Why was this product recalled?

(Retrospectively reported) Cybersecurity vulnerability identified in communication protocol between the customer-provided infrastructure (network storage, servers, or computers) and in vitro diagnostic devices which may result in compromised data transmission.

These are potential consequences described in the source. The recall reason does not establish how many injuries or incidents occurred.

What actions did Illumina, Inc. take?

On May 8, 2024, Illumina, Inc. issued a Urgent Medical Device Recall via email. Illumina ask consignees to take the following 1. Download & read this Cybersecurity Guidance document. The full hyperlink is below. https://support.illumina.com/support-content/cyberguidance.html 2. For Each Product Connected to the Customer Network: work with your internal IT department to determine which secure protocol works best in your environment and to implement the appropriate configuration change. Note: a change to the network protocol affects both Dx and RUO modes simultaneously therefore there is no need to boot into each mode separately to take the necessary action. 3. Complete and return the Verification Form after carrying out all the steps in the instructions provided on your specific product(s) identified as affected in Table 1.

Read the manufacturer action recorded by FDA

Recall timeline

  1. Recall initiated by firm

  2. FDA notice posted

  3. FDA classification recorded

  4. FDA enforcement report date

Related FDA submissions

No submission number with an exact verified relationship is linked in the retrieved recall notice.

FDA’s notice explicitly links the submission numbers shown here. Read each filing for its own recorded device and scope.

Source and update history

  1. FDA enforcement data

    First stored snapshot of this source.

  2. FDA device-recall notice

    First stored snapshot of this source.

The history starts with the versions held by MedtechLedger. Earlier source changes are not reconstructed. Official dates and recorded status come from FDA; page summaries describe the source information.

Our data sources and methodology