Opal - Notice history

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.

We have implemented a fix and are closely monitoring for healthy network traffic.

We have now identified gateway timeouts affecting app.opal.dev. We are investigating.

We have implemented a fix and are monitoring the situation.

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]

We implemented a fix and the queue has returned to a healthy state. We are continuing to monitor the results.

Service degradation to notifications. We have identified the cause and are continuing to work on a fix for this incident.

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

We apologize for the disruption this may have caused and appreciate your patience while our team worked to resolve this issue.

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

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