Cova incident

API Connection Issues Traceability (METRC and BioTrack)

Minor Resolved View vendor source →

Cova experienced a minor incident on January 31, 2026 affecting Traceability, lasting 1h 28m. The incident has been resolved; the full update timeline is below.

Started
Jan 31, 2026, 12:27 AM UTC
Resolved
Jan 31, 2026, 01:55 AM UTC
Duration
1h 28m
Detected by Pingoru
Jan 31, 2026, 12:27 AM UTC

Affected components

Traceability

Update timeline

  1. identified Jan 31, 2026, 12:27 AM UTC

    Our teams have identified an issue with API connectivity between Cova and METRC. We are investigating the issue and will post an update as we work toward resolution.

  2. identified Jan 31, 2026, 12:33 AM UTC

    We are continuing to work on a fix for this issue.

  3. identified Jan 31, 2026, 12:35 AM UTC

    This incident has been updated to apply to both BioTrack and METRC traceability services. Our teams are investigating and working to restore services. We will continue to provide updates.

  4. identified Jan 31, 2026, 12:54 AM UTC

    Our developers have identified the issue and are working on deploying a fix. METRC connectivity should be restored within 45 minutes. We will continue to provide updates.

  5. identified Jan 31, 2026, 01:37 AM UTC

    We are continuing to work to restore connectivity to traceability services and are close to deployment. We will provide notification once services are restored.

  6. monitoring Jan 31, 2026, 01:47 AM UTC

    Our teams have successfully deployed an update to the impacted services and API connectivity to both BioTrack and METRC traceability systems has been restored. Sales will be reprocessed and manifests and other services are working as usual. We will monitor the connection prior to closing out this incident.

  7. monitoring Jan 31, 2026, 01:47 AM UTC

    We are continuing to monitor for any further issues.

  8. resolved Jan 31, 2026, 01:55 AM UTC

    Traceability services have been fully restored and our teams will monitor to prevent any further disruptions. Thank you for your patience while we worked to resolve this incident.