Skip to content

Reef TARecalls & reported problems across all models

Seaspine Orthopedics Corporation · 2 models in the FDA device registry

Data updated Oct 16, 2026 from official FDA records · Editorial policy

1 open recall names at least one Reef TA model. Check whether yours is affected in the recall details, and contact the manufacturer or your healthcare provider.

Adverse event reports
0
Deaths reported
0
Injuries reported
0
Recalls
1

We found 2 models of Reef TA by Seaspine Orthopedics Corporation in the FDA's device registry (GUDID). None of them is named in an adverse event report in our data.

1 FDA recall record name at least one of these models by its device identifier, 1 still open.

Reports come from manufacturers, hospitals and patients and are not verified by the FDA. A report does not prove the device caused the event. Widely used products collect more reports, so totals can't be used to compare products or estimate failure rates. Only reports that name a model's exact device identifier are counted. What reports can and can't tell you · How this data works

Reef TA recalls

FDA recall records that name at least one of these models by its device identifier, newest first. Each recall usually covers specific models or lots, so check the details.

  1. Aug 6, 2025Open, Classified

    Inserter, used as part of a system with an intervertebral body fusion device, may contribute to difficulty disengaging the implant or improper implant positioning, which may may lead to prolonged surgery, intraoperative revision, and may require the use of alternate instrumentation. Devices may also have incorrect UDI-DI marking.

    Z-2554-2025 · Root cause: Device Design · names 2 of these models · Recall details · FDA record ↗

Reef TA models

2 models, most reported first. Each model has its own page with its reports, recalls and device details.

Other Seaspine Orthopedics Corporation products

All Seaspine Orthopedics Corporation devices →

Sources and updates

How reports and recalls are matched · Editorial policy · Report an error on this page