Opal Security incident

Service Degradation

Minor Resolved View vendor source →

Opal Security experienced a minor incident on February 3, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
Feb 03, 2026, 10:30 PM UTC
Resolved
Feb 03, 2026, 10:30 PM UTC
Duration
Detected by Pingoru
Feb 03, 2026, 10:30 PM UTC

Update timeline

  1. resolved Feb 03, 2026, 10:30 PM UTC

    Type: Incident Duration: 2 hours and 40 minutes Affected Components: , App, API, Cloud → Feb 3, 22:30:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Feb 3, 23:46:36 GMT+0 - Identified - Performance is degraded across all surfaces for cloud customers. Opal is working on deploying a fix. Feb 4, 00:44:34 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Performance metrics have recovered. Feb 4, 01:10:01 GMT+0 - Resolved - This incident has been resolved. Feb 12, 02:11:44 GMT+0 - Postmortem - Our team has met internally to review the incident on February 3rd 2026, where the Opal cloud platform experienced increased latency and delays in delivering notifications. We've prepared a postmortem for this incident, including a detailed timeline, root cause analysis, and plan for preventing similar issues in the future. You can find the public postmortem for this incident here - [\[LINK\]](https://opal-security.notion.site/EXTERNAL-2026-02-03-Database-Locking-Issues-303b8b94ee958039bd65d28bab0b23e8). We apologize for the disruption this may have caused and appreciate your patience while our team worked to resolve this issue.