Opal Security incident

Service Degradation

Minor Resolved View vendor source →

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

Started
Feb 03, 2026, 10:30 PM UTC
Resolved
Feb 04, 2026, 01:10 AM UTC
Duration
2h 40m
Detected by Pingoru
Feb 03, 2026, 10:30 PM UTC

Update timeline

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

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

  2. identified Feb 03, 2026, 11:46 PM UTC

    Performance is degraded across all surfaces for cloud customers. Opal is working on deploying a fix..

  3. monitoring Feb 04, 2026, 12:44 AM UTC

    We implemented a fix and are currently monitoring the result. Performance metrics have recovered..

  4. resolved Feb 04, 2026, 01:10 AM UTC

    This incident has been resolved..

  5. monitoring Feb 12, 2026, 02:11 AM UTC

    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..