Notice history
View current statusMay 2026
Apr 2026
- Postmortem · UTC
Our team has met internally to review the incident on April 7th 2026, where Opal's cloud platform was unavailable. 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].
We apologize for the disruption this may have caused and appreciate your patience while our team worked to resolve this issue.
- Resolved · UTCThis incident has been resolved.
- Monitoring · UTC
We have implemented a fix and are closely monitoring for healthy network traffic.
- Investigating · UTC
We have now identified gateway timeouts affecting app.opal.dev. We are investigating.
- Monitoring · UTC
We have implemented a fix and are monitoring the situation.
- Investigating · UTC
All Opal services are currently degraded. We are actively investigating the issue and appreciate your patience.
Mar 2026
- Postmortem · UTC
Our team has published a report detailing the recent incident, including contributing factors, response efforts, and actions being taken to prevent similar issues in the future.
We understand the disruption this may have caused and appreciate your ongoing support.
You can find the full report here: [LINK] - Resolved · UTCThis incident has been resolved.
- Monitoring · UTC
We implemented a fix and the queue has returned to a healthy state. We are continuing to monitor the results.
- Identified · UTC
Service degradation to notifications. We have identified the cause and are continuing to work on a fix for this incident.
- Investigating · UTCWe are currently investigating this incident.
