Opal Security had 22 outages in the last 2 years totaling 3h 59m of downtime — averaging 0.9 incidents per month.
There were 22 Opal Security outages since March 17, 2025 totaling 3h 59m of downtime. Each is summarised below — incident details, duration, and resolution information.
Third party service degradation is impacting Opal's on-prem Slack integration.
This incident has been resolved.
We are currently investigating this incident.
We implemented a fix and are currently monitoring the result.
This incident has been resolved.
Type: Incident Duration: 58 minutes Affected Components: App, API, Slack Integration May 8, 15:11:56 GMT+0 - Investigating - We are currently investigating this incident. May 8, 15:44:01 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. May 8, 16:10:12 GMT+0 - Resolved - This incident has been resolved.
Type: Maintenance Duration: 2 hours and 16 minutes Affected Components: App, API, Slack Integration Apr 8, 02:00:00 GMT+0 - Identified - We will be scheduling a maintenance window for our cloud infrastructure at 7:00 PM PDT this evening to finish resolving the incident from earlier today. During this window, there may be a brief period of downtime (a few minutes) affecting the Web UI, API, and Slack integration. There will be no impact to data integrity, access expirations, or other scheduled tasks. We will update this page when we begin maintenance, and as we make progress on the fix. Apr 8, 02:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 8, 04:16:15 GMT+0 - Completed - Maintenance has completed successfully.
Type: Incident Duration: 6 hours and 4 minutes Affected Components: App, API, , Cloud → Nov 18, 11:47:04 GMT+0 - Identified - The Opal UI is currently unavailable at [app.opal.dev](http://app.opal.dev) due to an outage at our DNS provider, Cloudflare: Nov 18, 14:58:37 GMT+0 - Monitoring - Following Cloudflare's [latest update](https://www.cloudflarestatus.com/incidents/8gmgl950y3h7) indicating their issue may be resolved, we are seeing improved access to the Opal platform. Access to our webapp at [app.opal.dev](http://app.opal.dev) and request submissions via the UI and Slack are functioning more reliably. We will continue to monitor for full service restoration. Thank you for your patience Nov 18, 17:50:58 GMT+0 - Resolved - After monitoring the implemented fix by Cloudflare, we have confirmed this issue has been successfully resolved. Thank you again for your patience as we worked to resolve this issue and we apologize for any inconvenience this issue may have caused.
Type: Incident Duration: 5 hours and 54 minutes Affected Components: App, API Oct 27, 08:00:00 GMT+0 - Investigating - We are currently investigating an incident where access is failing to propagate. Self-hosted customers should avoid upgrading at this time. Thank you for your patience and we apologize for any inconvenience. Oct 27, 11:31:49 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Oct 27, 13:54:16 GMT+0 - Resolved - Access changes are propagating as usual. Any access changes enqueued during the outage will propagate with some delay. We apologize for any disruption and thank you for your patience.
Type: Incident Duration: 49 minutes Oct 20, 08:00:00 GMT+0 - Monitoring - Opal is aware of the ongoing AWS outage. We are monitoring for affects to the main app, which is currently still healthy. Our website is affected and is unavailable at the moment. Oct 20, 08:48:38 GMT+0 - Resolved - is back online!
Type: Incident Duration: 21 hours and 21 minutes Affected Components: App, API, , Cloud → Sep 25, 19:24:00 GMT+0 - Identified - We have identified an issue where access changes made directly in Entra (outside of Opal) to enterprise apps were not syncing as expected. Expirations and propagations within Opal remain unaffected. Sep 26, 16:45:05 GMT+0 - Resolved - This issue has been resolved. Access changes made directly in Entra (outside of Opal) are now syncing as expected. Thank you for your patience as we worked to resolve this issue.
Type: Incident Duration: 10 minutes Affected Components: API Sep 9, 18:00:00 GMT+0 - Resolved - This incident has been resolved. Sep 9, 17:50:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Sep 15, 22:30:17 GMT+0 - Postmortem -
Type: Incident Duration: 49 minutes Affected Components: App, API, , Cloud → Aug 26, 02:25:47 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Aug 26, 02:29:31 GMT+0 - Resolved - This incident has been resolved. Aug 26, 01:40:10 GMT+0 - Investigating - We are currently investigating this incident. Aug 26, 02:01:14 GMT+0 - Identified - We are continuing to work on a fix for this incident. We're scaling up our task workers to accommodate the higher volume of access changes.
Type: Incident Duration: 25 minutes Aug 5, 16:56:51 GMT+0 - Identified - We have identified the root cause of this problem and have initiated a rollback to temporarily resolve the issue. The team is investigating a long-term fix and will implement this before the next release. Thank you for your patience and apologies for any inconvenience Aug 5, 17:22:12 GMT+0 - Resolved - After monitoring the results of the rollback, we have confirmed this issue has been successfully resolved. Thank you again for your patience as we worked to resolve this issue and we apologize for any inconvenience this issue may have caused.
Type: Incident Duration: 2 hours and 35 minutes Jun 17, 18:51:17 GMT+0 - Investigating - We are currently investigating an issue with slack modal where requests are failing sporadically. Thank you for your patience as we investigate this issue. Jun 17, 21:26:31 GMT+0 - Resolved - We have successfully implemented a fix for the elevated Slack request latency issue. After deploying the solution and conducting thorough validation, we can confirm that slack request latency has returned to normal levels and requests from slack are no longer failing sporadically
Type: Incident Duration: 46 minutes Jun 16, 21:15:03 GMT+0 - Investigating - We are currently investigating a potential Okta sync issue where some users are being incorrectly removed from groups. Thank you for your patience as we investigate this issue. Jun 16, 21:38:19 GMT+0 - Monitoring - We believe this issue was isolated to a specific customer's setup but are still performing checks on our end to ensure this issue is not widespread. Jun 16, 22:01:33 GMT+0 - Resolved - After a thorough investigation, our engineering team can confirm that this incident was isolated to a single customer's environment and was due to a change made within their Okta instance. Other environments should be unaffected by this issue. We appreciate your patience while we investigated this issue. If you have any additional questions or concerns, please reach out to our support team.
Type: Incident Duration: 10 minutes Affected Components: App Jun 9, 16:34:00 GMT+0 - Resolved - This incident has been resolved. Jun 9, 16:24:00 GMT+0 - Investigating - Impact includes access grants and revocations. We are currently investigating this incident. Jun 13, 20:02:34 GMT+0 - Postmortem -
Type: Incident Duration: 5 days and 11 hours Affected Components: App Jun 9, 07:37:00 GMT+0 - Investigating - We are currently investigating this incident. Jun 9, 09:48:00 GMT+0 - Resolved - This incident has been resolved. Jun 13, 20:51:30 GMT+0 - Postmortem -
Type: Incident Duration: 1 hour and 31 minutes Affected Components: App May 30, 00:17:12 GMT+0 - Investigating - We are currently investigating this incident. May 30, 00:30:01 GMT+0 - Identified - We are continuing to work on a fix for this incident. May 30, 01:35:10 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. May 30, 01:48:41 GMT+0 - Resolved - This incident has been resolved. Jun 2, 22:36:46 GMT+0 - Postmortem -
Type: Incident Duration: 9 hours and 47 minutes Affected Components: App May 17, 02:00:09 GMT+0 - Resolved - This incident has been resolved. May 16, 23:35:02 GMT+0 - Identified - We are continuing to work on a fix for this incident. May 16, 16:13:08 GMT+0 - Investigating - We are currently investigating this incident. May 17, 01:00:21 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result.
Type: Incident Duration: 6 hours and 15 minutes Affected Components: App Mar 17, 17:32:57 GMT+0 - Identified - We are continuing to work on a fix for this incident. Mar 17, 23:48:18 GMT+0 - Resolved - This incident has been resolved.