Opal Status - Incident history https://status.opal.dev Opal Wed, 18 Mar 2026 21:35:26 +0000 Service Degradation Type: Incident Duration: 5 hours and 36 minutes Affected Components: , App, API, Slack Integration, Cloud → Mar 18, 21:35:26 GMT+0 - Investigating - We are currently investigating this incident. Mar 18, 22:05:01 GMT+0 - Identified - Service degradation to notifications. We have identified the cause and are continuing to work on a fix for this incident. Mar 19, 00:07:27 GMT+0 - Monitoring - We implemented a fix and the queue has returned to a healthy state. We are continuing to monitor the results. Mar 19, 03:11:25 GMT+0 - Resolved - This incident has been resolved. Mar 25, 01:33:25 GMT+0 - Postmortem - 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\]](https://www.notion.so/opal-security/EXTERNAL-2025-03-18-Delays-in-Task-Queue-affecting-Notifications-32db8b94ee95807db04dc753b40a964b?source=copy%5Flink) Type: Incident

Duration: 5 hours and 36 minutes

Affected Components: , , ,

<p><small>Mar <var data-var='date'> 18</var>, <var data-var='time'>21:35:26</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Mar <var data-var='date'> 18</var>, <var data-var='time'>22:05:01</var> GMT+0</small><br><strong>Identified</strong> - Service degradation to notifications. We have identified the cause and are continuing to work on a fix for this incident..</p> <p><small>Mar <var data-var='date'> 19</var>, <var data-var='time'>00:07:27</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and the queue has returned to a healthy state. We are continuing to monitor the results..</p> <p><small>Mar <var data-var='date'> 19</var>, <var data-var='time'>03:11:25</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Mar <var data-var='date'> 25</var>, <var data-var='time'>01:33:25</var> GMT+0</small><br><strong>Postmortem</strong> - 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\]](https://www.notion.so/opal-security/EXTERNAL-2025-03-18-Delays-in-Task-Queue-affecting-Notifications-32db8b94ee95807db04dc753b40a964b?source=copy%5Flink).</p> ]]> Wed, 18 Mar 2026 21:35:26 +0000 https://status.opal.dev/incident/cmmwk8gtj02e6j73cno60u11r https://status.opal.dev/incident/cmmwk8gtj02e6j73cno60u11r Service Degradation Type: Incident Duration: 1 hour and 3 minutes Affected Components: , App, API, Cloud → Feb 18, 02:58:58 GMT+0 - Investigating - We are currently investigating this incident. Feb 18, 03:28:52 GMT+0 - Monitoring - We have mitigated the service degradation and are monitoring. Manually triggered syncs may take longer than usual to complete. Feb 18, 04:02:20 GMT+0 - Resolved - We have identified the root cause and confirmed that our mitigations are working. Manual sync tasks may have been interrupted and will have to be retried. Type: Incident

Duration: 1 hour and 3 minutes

Affected Components: , ,

<p><small>Feb <var data-var='date'> 18</var>, <var data-var='time'>02:58:58</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Feb <var data-var='date'> 18</var>, <var data-var='time'>03:28:52</var> GMT+0</small><br><strong>Monitoring</strong> - We have mitigated the service degradation and are monitoring. Manually triggered syncs may take longer than usual to complete..</p> <p><small>Feb <var data-var='date'> 18</var>, <var data-var='time'>04:02:20</var> GMT+0</small><br><strong>Resolved</strong> - We have identified the root cause and confirmed that our mitigations are working. Manual sync tasks may have been interrupted and will have to be retried. .</p> ]]> Wed, 18 Feb 2026 02:58:58 +0000 https://status.opal.dev/incident/cmlrg0u7103ezeookc6p9z2ss https://status.opal.dev/incident/cmlrg0u7103ezeookc6p9z2ss Service Degradation 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. Type: Incident

Duration: 2 hours and 40 minutes

Affected Components: , ,

<p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>22:30:00</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>23:46:36</var> GMT+0</small><br><strong>Identified</strong> - Performance is degraded across all surfaces for cloud customers. Opal is working on deploying a fix..</p> <p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>00:44:34</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result. Performance metrics have recovered..</p> <p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>01:10:01</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Feb <var data-var='date'> 12</var>, <var data-var='time'>02:11:44</var> GMT+0</small><br><strong>Postmortem</strong> - 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..</p> ]]> Tue, 3 Feb 2026 22:30:00 +0000 https://status.opal.dev/incident/cml77wv9j001klprfomklayie https://status.opal.dev/incident/cml77wv9j001klprfomklayie Opal app down 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: <https://www.cloudflarestatus.com/incidents/8gmgl950y3h7> 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: 6 hours and 4 minutes

Affected Components: , ,

<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>11:47:04</var> GMT+0</small><br><strong>Identified</strong> - The Opal UI is currently unavailable at [app.opal.dev](http://app.opal.dev) due to an outage at our DNS provider, Cloudflare: <https://www.cloudflarestatus.com/incidents/8gmgl950y3h7>.</p> <p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>14:58:37</var> GMT+0</small><br><strong>Monitoring</strong> - 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.</p> <p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>17:50:58</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> ]]> Tue, 18 Nov 2025 11:47:04 +0000 https://status.opal.dev/incident/cmi4idlnq021z4oz55wx4dh10 https://status.opal.dev/incident/cmi4idlnq021z4oz55wx4dh10 Issues with Access Propagation 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: 5 hours and 54 minutes

Affected Components: ,

<p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>11:31:49</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>13:54:16</var> GMT+0</small><br><strong>Resolved</strong> - 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. .</p> ]]> Mon, 27 Oct 2025 08:00:00 +0000 https://status.opal.dev/incident/cmh8zkc5200r0hc2co4lpp21a https://status.opal.dev/incident/cmh8zkc5200r0hc2co4lpp21a Scheduled jobs failing related to AWS outage Type: Incident Duration: 14 hours and 20 minutes Affected Components: App, , API, App, API, Self-Hosted → Oct 20, 19:39:31 GMT+0 - Identified - We are currently investigating an incident where the [LaunchDarkly](https://status.launchdarkly.com/incidents/zxl3q06s2lvq)/[AWS](https://health.aws.amazon.com/health/status?eventID=arn:aws:health:us-east-1::event/MULTIPLE%5FSERVICES/AWS%5FMULTIPLE%5FSERVICES%5FOPERATIONAL%5FISSUE/AWS%5FMULTIPLE%5FSERVICES%5FOPERATIONAL%5FISSUE%5FBA540%5F514A652BE1A) outage is causing scheduled jobs to fail. This may affect delays in sync, access expirations, and event streaming. Self-hosted customers should avoid upgrading at this time. Thank you for your patience and we apologize for any inconvenience. Oct 20, 20:03:54 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Scheduled syncs and access expirations should now be running normally. For self-hosted customers who may be affected, please reach out to our support team for guidance on a workaround to mitigate this issue. Thank you for your patience as we worked to resolve this issue. Oct 20, 20:21:56 GMT+0 - Monitoring - For self-hosted customers, please see [this document](https://www.notion.so/opal-security/EXTERNAL-2025-10-20-Opal-Workaround-for-LaunchDarkly-Incident-292b8b94ee9580cd8babdca08b85b7b6?source=copy%5Flink) for guidance on how to implement a workaround for this issue. If you have any questions or need additional assistance, please reach out to our team. Thank you again for your patience while we worked to resolve this issue. Oct 20, 23:17:35 GMT+0 - Monitoring - Scheduled jobs are running successfully for cloud customers. Self-hosted customers may continue to see errors in launching Opal pods as LaunchDarkly continues to work through [their incident](https://status.launchdarkly.com/incidents/zxl3q06s2lvq). To work around these LaunchDarkly errors, please see [this document](https://www.notion.so/opal-security/EXTERNAL-2025-10-20-Opal-Workaround-for-LaunchDarkly-Incident-292b8b94ee9580cd8babdca08b85b7b6). If you have any questions or need additional assistance, please reach out to our team. Oct 21, 10:00:00 GMT+0 - Resolved - This incident has been resolved. Thank you again for your patience and we apologize for any inconvenience this issue may have caused. Type: Incident

Duration: 14 hours and 20 minutes

Affected Components: , , , ,

<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>19:39:31</var> GMT+0</small><br><strong>Identified</strong> - We are currently investigating an incident where the [LaunchDarkly](https://status.launchdarkly.com/incidents/zxl3q06s2lvq)/[AWS](https://health.aws.amazon.com/health/status?eventID=arn:aws:health:us-east-1::event/MULTIPLE%5FSERVICES/AWS%5FMULTIPLE%5FSERVICES%5FOPERATIONAL%5FISSUE/AWS%5FMULTIPLE%5FSERVICES%5FOPERATIONAL%5FISSUE%5FBA540%5F514A652BE1A) outage is causing scheduled jobs to fail. This may affect delays in sync, access expirations, and event streaming. Self-hosted customers should avoid upgrading at this time. Thank you for your patience and we apologize for any inconvenience..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>20:03:54</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result. Scheduled syncs and access expirations should now be running normally. For self-hosted customers who may be affected, please reach out to our support team for guidance on a workaround to mitigate this issue. Thank you for your patience as we worked to resolve this issue..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>20:21:56</var> GMT+0</small><br><strong>Monitoring</strong> - For self-hosted customers, please see [this document](https://www.notion.so/opal-security/EXTERNAL-2025-10-20-Opal-Workaround-for-LaunchDarkly-Incident-292b8b94ee9580cd8babdca08b85b7b6?source=copy%5Flink) for guidance on how to implement a workaround for this issue. If you have any questions or need additional assistance, please reach out to our team. Thank you again for your patience while we worked to resolve this issue..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>23:17:35</var> GMT+0</small><br><strong>Monitoring</strong> - Scheduled jobs are running successfully for cloud customers. Self-hosted customers may continue to see errors in launching Opal pods as LaunchDarkly continues to work through [their incident](https://status.launchdarkly.com/incidents/zxl3q06s2lvq). To work around these LaunchDarkly errors, please see [this document](https://www.notion.so/opal-security/EXTERNAL-2025-10-20-Opal-Workaround-for-LaunchDarkly-Incident-292b8b94ee9580cd8babdca08b85b7b6). If you have any questions or need additional assistance, please reach out to our team..</p> <p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. Thank you again for your patience and we apologize for any inconvenience this issue may have caused..</p> ]]> Mon, 20 Oct 2025 19:39:31 +0000 https://status.opal.dev/incident/cmgzjhh2n035ebfmyk0shv5ax https://status.opal.dev/incident/cmgzjhh2n035ebfmyk0shv5ax Ongoing AWS Outage 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 <https://www.opal.dev/> is affected and is unavailable at the moment. Oct 20, 08:48:38 GMT+0 - Resolved - <https://www.opal.dev/> is back online! Type: Incident

Duration: 49 minutes

<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br><strong>Monitoring</strong> - Opal is aware of the ongoing AWS outage. We are monitoring for affects to the main app, which is currently still healthy. Our website <https://www.opal.dev/> is affected and is unavailable at the moment..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>08:48:38</var> GMT+0</small><br><strong>Resolved</strong> - <https://www.opal.dev/> is back online!.</p> ]]> Mon, 20 Oct 2025 08:00:00 +0000 https://status.opal.dev/incident/cmgyvqk7603gognpzlusvxnhn https://status.opal.dev/incident/cmgyvqk7603gognpzlusvxnhn Performance issues with visibility limitations Type: Incident Duration: 1 day, 2 hours and 25 minutes Affected Components: App, API, , Cloud → Oct 10, 20:37:54 GMT+0 - Postmortem - Following the recent incident on October 1st, 2025, where some users were experiencing issues due to increased latency, our team has published a report that includes contributing factors, response efforts, and actions being taken to prevent similar issues in the future. We apologize for the disruption this may have caused and appreciate your patience while our team worked to resolve this issue. You can find the full report here: [\[LINK\]](https://opal-security.notion.site/EXTERNAL-2025-10-1-Increased-latency-in-the-authorizer-288b8b94ee9580cdabcff5ceac16a3bc) Oct 1, 18:05:39 GMT+0 - Investigating - We are aware of long load times for some items with visibility restrictions. Some users are seeing timeout errors. Team is currently investigating. Oct 1, 20:05:29 GMT+0 - Monitoring - We rolled back a recent change to mitigate the issue causing long load times and timeout errors for items with visibility restrictions and are monitoring to confirm that the issue has been fully resolved. Thank you for your patience as we worked to resolve this issue! Oct 2, 01:51:44 GMT+0 - Resolved - This incident has been resolved. Oct 2, 15:14:30 GMT+0 - Identified - We are aware of continued performance issues. We are working on identifying and rolling out a fix. Oct 2, 20:31:00 GMT+0 - Resolved - We’ve deployed a fix and are seeing improved latency across the platform. We recognize this issue caused disruption and appreciate your patience while we addressed it. Systems are now stable, and we’ll continue to monitor performance. Type: Incident

Duration: 1 day, 2 hours and 25 minutes

Affected Components: , ,

<p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>20:37:54</var> GMT+0</small><br><strong>Postmortem</strong> - Following the recent incident on October 1st, 2025, where some users were experiencing issues due to increased latency, our team has published a report that includes contributing factors, response efforts, and actions being taken to prevent similar issues in the future. We apologize for the disruption this may have caused and appreciate your patience while our team worked to resolve this issue. You can find the full report here: [\[LINK\]](https://opal-security.notion.site/EXTERNAL-2025-10-1-Increased-latency-in-the-authorizer-288b8b94ee9580cdabcff5ceac16a3bc).</p> <p><small>Oct <var data-var='date'> 1</var>, <var data-var='time'>18:05:39</var> GMT+0</small><br><strong>Investigating</strong> - We are aware of long load times for some items with visibility restrictions. Some users are seeing timeout errors. Team is currently investigating..</p> <p><small>Oct <var data-var='date'> 1</var>, <var data-var='time'>20:05:29</var> GMT+0</small><br><strong>Monitoring</strong> - We rolled back a recent change to mitigate the issue causing long load times and timeout errors for items with visibility restrictions and are monitoring to confirm that the issue has been fully resolved. Thank you for your patience as we worked to resolve this issue!.</p> <p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>01:51:44</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>15:14:30</var> GMT+0</small><br><strong>Identified</strong> - We are aware of continued performance issues. We are working on identifying and rolling out a fix. .</p> <p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>20:31:00</var> GMT+0</small><br><strong>Resolved</strong> - We’ve deployed a fix and are seeing improved latency across the platform. We recognize this issue caused disruption and appreciate your patience while we addressed it. Systems are now stable, and we’ll continue to monitor performance..</p> ]]> Wed, 1 Oct 2025 18:05:39 +0000 https://status.opal.dev/incident/cmg8arkwy0v4ao5fqej6k43ir https://status.opal.dev/incident/cmg8arkwy0v4ao5fqej6k43ir Delays in syncing access changes to Azure Enterprise Apps 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: 21 hours and 21 minutes

Affected Components: , ,

<p><small>Sep <var data-var='date'> 25</var>, <var data-var='time'>19:24:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Sep <var data-var='date'> 26</var>, <var data-var='time'>16:45:05</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> ]]> Thu, 25 Sep 2025 19:24:00 +0000 https://status.opal.dev/incident/cmg14dwxo063zfhewvl4a2r6n https://status.opal.dev/incident/cmg14dwxo063zfhewvl4a2r6n GET /groups/{group_id}/users not returning a full list of users when pagination parameters are not set 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 - <https://opal-security.notion.site/EXTERNAL-2025-09-09-API-Pagination-Breaking-Change-26db8b94ee958128bfc7e5ca143eaecd?pvs=74> Type: Incident

Duration: 10 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>17:50:00</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Sep <var data-var='date'> 15</var>, <var data-var='time'>22:30:17</var> GMT+0</small><br><strong>Postmortem</strong> - <https://opal-security.notion.site/EXTERNAL-2025-09-09-API-Pagination-Breaking-Change-26db8b94ee958128bfc7e5ca143eaecd?pvs=74>.</p> ]]> Tue, 9 Sep 2025 17:50:00 +0000 https://status.opal.dev/incident/cmfcw83nt00pma2ys2pzbyyrb https://status.opal.dev/incident/cmfcw83nt00pma2ys2pzbyyrb Degraded notifications and propagation changes performance 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: 49 minutes

Affected Components: , ,

<p><small>Aug <var data-var='date'> 26</var>, <var data-var='time'>02:25:47</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Aug <var data-var='date'> 26</var>, <var data-var='time'>02:29:31</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Aug <var data-var='date'> 26</var>, <var data-var='time'>01:40:10</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Aug <var data-var='date'> 26</var>, <var data-var='time'>02:01:14</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> ]]> Tue, 26 Aug 2025 01:40:10 +0000 https://status.opal.dev/incident/cmervpkex003wg3572gikepll https://status.opal.dev/incident/cmervpkex003wg3572gikepll Users receiving multiple access expiring notifications 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: 25 minutes

<p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>16:56:51</var> GMT+0</small><br><strong>Identified</strong> - 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.</p> <p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>17:22:12</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> ]]> Tue, 5 Aug 2025 16:56:51 +0000 https://status.opal.dev/incident/cmdys7jms00jrj9abhx829wg6 https://status.opal.dev/incident/cmdys7jms00jrj9abhx829wg6 No Action Required: Brief Maintenance Window Scheduled Type: Maintenance Duration: 2 hours Affected Components: App, API Jul 23, 05:00:00 GMT+0 - Completed - Maintenance has completed successfully Jul 23, 03:00:00 GMT+0 - Identified - **Scheduled Maintenance: Tonight (7/22) at 8pm PST** We will be performing scheduled maintenance on our cloud infrastructure that may result in slightly slower response times for approximately 90 minutes. **What to expect:** \- The web application may load slower than usual. \- All features will remain functional. \- On-premise deployments are NOT affected. \- API requests and integrations (including Slack) will continue to work, though responses may take a bit longer. **What you DON'T need to do:** \- No action required from admins. \- No need to notify your end users. \- No configuration changes needed. **Why we're notifying you:** While we expect minimal impact, we want to keep you informed in case you notice slower load times. This maintenance helps us improve long-term stability and performance. If you experience any significant issues during this window, please contact support immediately. Jul 23, 03:00:01 GMT+0 - Identified - Maintenance is now in progress Type: Maintenance

Duration: 2 hours

Affected Components: ,

<p><small>Jul <var data-var='date'> 23</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Jul <var data-var='date'> 23</var>, <var data-var='time'>03:00:00</var> GMT+0</small><br><strong>Identified</strong> - **Scheduled Maintenance: Tonight (7/22) at 8pm PST** We will be performing scheduled maintenance on our cloud infrastructure that may result in slightly slower response times for approximately 90 minutes. **What to expect:** \- The web application may load slower than usual. \- All features will remain functional. \- On-premise deployments are NOT affected. \- API requests and integrations (including Slack) will continue to work, though responses may take a bit longer. **What you DON'T need to do:** \- No action required from admins. \- No need to notify your end users. \- No configuration changes needed. **Why we're notifying you:** While we expect minimal impact, we want to keep you informed in case you notice slower load times. This maintenance helps us improve long-term stability and performance. If you experience any significant issues during this window, please contact support immediately..</p> <p><small>Jul <var data-var='date'> 23</var>, <var data-var='time'>03:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> ]]> Wed, 23 Jul 2025 03:00:00 +0000 https://status.opal.dev/maintenance/cmdeu2c0t004wuysnh13dteot https://status.opal.dev/maintenance/cmdeu2c0t004wuysnh13dteot Scheduled database maintenance Type: Maintenance Duration: 2 hours Affected Components: App, API Jul 22, 05:00:00 GMT+0 - Completed - Maintenance has completed successfully Jul 22, 03:00:00 GMT+0 - Identified - Service should not be meaningfully impacted. The web app might be marginally slower. Please let us know of any workflows seriously impacted. Jul 22, 03:00:01 GMT+0 - Identified - Maintenance is now in progress Type: Maintenance

Duration: 2 hours

Affected Components: ,

<p><small>Jul <var data-var='date'> 22</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Jul <var data-var='date'> 22</var>, <var data-var='time'>03:00:00</var> GMT+0</small><br><strong>Identified</strong> - Service should not be meaningfully impacted. The web app might be marginally slower. Please let us know of any workflows seriously impacted..</p> <p><small>Jul <var data-var='date'> 22</var>, <var data-var='time'>03:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> ]]> Tue, 22 Jul 2025 03:00:00 +0000 https://status.opal.dev/maintenance/cmddq74pt00825i3mhvey1kob https://status.opal.dev/maintenance/cmddq74pt00825i3mhvey1kob Delays in propagation and notifications. Type: Incident Duration: 1 hour and 32 minutes Affected Components: App Jul 7, 14:31:16 GMT+0 - Investigating - We are currently investigating this incident. Jul 7, 14:45:30 GMT+0 - Identified - We have identified the issue and our team is actively working on a mitigation. Thank you for your patience as we work to resolve this issue. Jul 7, 15:24:42 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. We appreciate your continued patience while we work to resolve this issue. Jul 7, 16:03:02 GMT+0 - Resolved - After monitoring the implemented fix, 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. Jul 8, 20:43:20 GMT+0 - Postmortem - Following the recent incident on 7/7/25, where propagation and notification tasks were delayed, our team has published a report that includes contributing factors, response efforts, and actions being taken to prevent similar issues in the future. We apologize for the disruption this may have caused and appreciate your patience while our team worked to resolve this issue. You can find the full report here: [\[LINK\]](https://www.notion.so/opal-security/EXTERNAL-7-7-2025-Delays-In-Access-Propagation-and-Notifications-229b8b94ee9580d2b960c35d4693e772?source=copy%5Flink) Type: Incident

Duration: 1 hour and 32 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>14:31:16</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>14:45:30</var> GMT+0</small><br><strong>Identified</strong> - We have identified the issue and our team is actively working on a mitigation. Thank you for your patience as we work to resolve this issue..</p> <p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>15:24:42</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result. We appreciate your continued patience while we work to resolve this issue..</p> <p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>16:03:02</var> GMT+0</small><br><strong>Resolved</strong> - After monitoring the implemented fix, 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. .</p> <p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>20:43:20</var> GMT+0</small><br><strong>Postmortem</strong> - Following the recent incident on 7/7/25, where propagation and notification tasks were delayed, our team has published a report that includes contributing factors, response efforts, and actions being taken to prevent similar issues in the future. We apologize for the disruption this may have caused and appreciate your patience while our team worked to resolve this issue. You can find the full report here: [\[LINK\]](https://www.notion.so/opal-security/EXTERNAL-7-7-2025-Delays-In-Access-Propagation-and-Notifications-229b8b94ee9580d2b960c35d4693e772?source=copy%5Flink).</p> ]]> Mon, 7 Jul 2025 14:31:16 +0000 https://status.opal.dev/incident/cmct78m2000oschkvmdf402a6 https://status.opal.dev/incident/cmct78m2000oschkvmdf402a6 Investigating elevated slack request latency 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: 2 hours and 35 minutes

<p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>18:51:17</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating an issue with slack modal where requests are failing sporadically. Thank you for your patience as we investigate this issue..</p> <p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>21:26:31</var> GMT+0</small><br><strong>Resolved</strong> - 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.</p> ]]> Tue, 17 Jun 2025 18:51:17 +0000 https://status.opal.dev/incident/cmc0vpyr20028611kqpvsxkk1 https://status.opal.dev/incident/cmc0vpyr20028611kqpvsxkk1 Users incorrectly removed from groups via Okta sync 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: 46 minutes

<p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>21:15:03</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>21:38:19</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>22:01:33</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> ]]> Mon, 16 Jun 2025 21:15:03 +0000 https://status.opal.dev/incident/cmbzlezmq000tuwkc3ntnai3x https://status.opal.dev/incident/cmbzlezmq000tuwkc3ntnai3x Opal experiencing delays in processing asynchronous workloads 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 - <https://opal-security.notion.site/EXTERNAL-2025-06-09-Delays-in-processing-asynchronous-workloads-211b8b94ee95800ea1ede66fddc8f942> Type: Incident

Duration: 10 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 9</var>, <var data-var='time'>16:34:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jun <var data-var='date'> 9</var>, <var data-var='time'>16:24:00</var> GMT+0</small><br><strong>Investigating</strong> - Impact includes access grants and revocations. We are currently investigating this incident..</p> <p><small>Jun <var data-var='date'> 13</var>, <var data-var='time'>20:02:34</var> GMT+0</small><br><strong>Postmortem</strong> - <https://opal-security.notion.site/EXTERNAL-2025-06-09-Delays-in-processing-asynchronous-workloads-211b8b94ee95800ea1ede66fddc8f942>.</p> ]]> Mon, 9 Jun 2025 16:24:00 +0000 https://status.opal.dev/incident/cmbuymh8y001y8aqhi9ts7qw8 https://status.opal.dev/incident/cmbuymh8y001y8aqhi9ts7qw8 Opal experiencing delays when propagating changes to end systems 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 - <https://opal-security.notion.site/EXTERNAL-2025-06-09-Delays-processing-access-grants-revocations-210b8b94ee9580e5a7bcc51cdf03489c?pvs=74> Type: Incident

Duration: 5 days and 11 hours

Affected Components:

<p><small>Jun <var data-var='date'> 9</var>, <var data-var='time'>07:37:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jun <var data-var='date'> 9</var>, <var data-var='time'>09:48:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jun <var data-var='date'> 13</var>, <var data-var='time'>20:51:30</var> GMT+0</small><br><strong>Postmortem</strong> - <https://opal-security.notion.site/EXTERNAL-2025-06-09-Delays-processing-access-grants-revocations-210b8b94ee9580e5a7bcc51cdf03489c?pvs=74>.</p> ]]> Mon, 9 Jun 2025 07:37:00 +0000 https://status.opal.dev/incident/cmbp60pqj000b10r675tplw9f https://status.opal.dev/incident/cmbp60pqj000b10r675tplw9f Minor Database Maintenance Type: Maintenance Duration: 37 minutes Affected Components: API, App May 31, 00:00:01 GMT+0 - Identified - Maintenance is now in progress May 31, 00:00:00 GMT+0 - Identified - We are planning on rolling out a minor change to our database to improve long-term performance. This will _not_ cause any downtime, but may result in slower response times for a short period as our database updates. May 31, 00:36:55 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 37 minutes

Affected Components: ,

<p><small>May <var data-var='date'> 31</var>, <var data-var='time'>00:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>May <var data-var='date'> 31</var>, <var data-var='time'>00:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning on rolling out a minor change to our database to improve long-term performance. This will _not_ cause any downtime, but may result in slower response times for a short period as our database updates..</p> <p><small>May <var data-var='date'> 31</var>, <var data-var='time'>00:36:55</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Sat, 31 May 2025 00:00:00 +0000 https://status.opal.dev/maintenance/cmbb7omgk001csq1sun5lkrmf https://status.opal.dev/maintenance/cmbb7omgk001csq1sun5lkrmf Access Rules not syncing 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 - <https://opal-security.notion.site/EXTERNAL-2025-05-29-Access-Rules-Failed-To-Sync-206b8b94ee958082839cf529a2922a36?source=copy%5Flink> Type: Incident

Duration: 1 hour and 31 minutes

Affected Components:

<p><small>May <var data-var='date'> 30</var>, <var data-var='time'>00:17:12</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>May <var data-var='date'> 30</var>, <var data-var='time'>00:30:01</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>May <var data-var='date'> 30</var>, <var data-var='time'>01:35:10</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>May <var data-var='date'> 30</var>, <var data-var='time'>01:48:41</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>22:36:46</var> GMT+0</small><br><strong>Postmortem</strong> - <https://opal-security.notion.site/EXTERNAL-2025-05-29-Access-Rules-Failed-To-Sync-206b8b94ee958082839cf529a2922a36?source=copy%5Flink>.</p> ]]> Fri, 30 May 2025 00:17:12 +0000 https://status.opal.dev/incident/cmba1zxwe0003p8cuw3bplubi https://status.opal.dev/incident/cmba1zxwe0003p8cuw3bplubi Some users are unable to log in Type: Incident Duration: 2 hours and 49 minutes Affected Components: App May 27, 13:56:06 GMT+0 - Identified - Some users are unable to log in due to a subprocessor outage. We are continuing to work on a fix for this incident. Thank you for your patience and we apologize for any inconvenience. May 27, 16:34:40 GMT+0 - Monitoring - There was a fix implemented by our subprocessor to resolve the issue and we are currently monitoring the result. Thank you again for your patience and apologize for any inconvenience this may have caused. May 27, 16:45:00 GMT+0 - Resolved - This incident has been resolved. Thank you for your patience and we apologize for any inconvenience this issue may have caused. May 29, 19:31:11 GMT+0 - Postmortem - Following the recent incident on 5/27/25, where Opal’s web platform experienced a partial outage between 6:45am PDT and 9:45am PDT that caused some users to be stuck in an indefinite loading state, our team has published a report that includes contributing factors, response efforts, and actions being taken to prevent similar issues in the future. We apologize for the disruption this may have caused and appreciate your patience while our team worked to resolve this issue. You can find the full report here: [\[LINK\]](https://www.notion.so/opal-security/External-2025-05-27-Some-users-unable-to-login-to-Opal-Web-200b8b94ee95803aa0a6da08879048b6) Type: Incident

Duration: 2 hours and 49 minutes

Affected Components:

<p><small>May <var data-var='date'> 27</var>, <var data-var='time'>13:56:06</var> GMT+0</small><br><strong>Identified</strong> - Some users are unable to log in due to a subprocessor outage. We are continuing to work on a fix for this incident. Thank you for your patience and we apologize for any inconvenience..</p> <p><small>May <var data-var='date'> 27</var>, <var data-var='time'>16:34:40</var> GMT+0</small><br><strong>Monitoring</strong> - There was a fix implemented by our subprocessor to resolve the issue and we are currently monitoring the result. Thank you again for your patience and apologize for any inconvenience this may have caused..</p> <p><small>May <var data-var='date'> 27</var>, <var data-var='time'>16:45:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. Thank you for your patience and we apologize for any inconvenience this issue may have caused..</p> <p><small>May <var data-var='date'> 29</var>, <var data-var='time'>19:31:11</var> GMT+0</small><br><strong>Postmortem</strong> - Following the recent incident on 5/27/25, where Opal’s web platform experienced a partial outage between 6:45am PDT and 9:45am PDT that caused some users to be stuck in an indefinite loading state, our team has published a report that includes contributing factors, response efforts, and actions being taken to prevent similar issues in the future. We apologize for the disruption this may have caused and appreciate your patience while our team worked to resolve this issue. You can find the full report here: [\[LINK\]](https://www.notion.so/opal-security/External-2025-05-27-Some-users-unable-to-login-to-Opal-Web-200b8b94ee95803aa0a6da08879048b6).</p> ]]> Tue, 27 May 2025 13:56:06 +0000 https://status.opal.dev/incident/cmb6kxh5u0007bqqaeseu3x4f https://status.opal.dev/incident/cmb6kxh5u0007bqqaeseu3x4f Degraded performance in group/resource detail pages when viewing users tab 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: 9 hours and 47 minutes

Affected Components:

<p><small>May <var data-var='date'> 17</var>, <var data-var='time'>02:00:09</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>May <var data-var='date'> 16</var>, <var data-var='time'>23:35:02</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>May <var data-var='date'> 16</var>, <var data-var='time'>16:13:08</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>May <var data-var='date'> 17</var>, <var data-var='time'>01:00:21</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> ]]> Fri, 16 May 2025 16:13:08 +0000 https://status.opal.dev/incident/cmaqzzbxg003410983igz6skz https://status.opal.dev/incident/cmaqzzbxg003410983igz6skz Error when loading Opal webapp Type: Incident Duration: 38 minutes Affected Components: App Apr 2, 21:12:21 GMT+0 - Investigating - We are currently investigating an incident where pages are displaying an error: `An error occurred while rendering this page. It's been logged and the team has been alerted. If this is an emergency, please reach out to your Admin or Opal Support.` Thank you for your patience! Apr 2, 21:19:41 GMT+0 - Identified - The team has identified the root cause of the error and are working on a fix. Thank you for your patience while we work to resolve this issue Apr 2, 21:30:37 GMT+0 - Monitoring - A fix has been implemented and we are currently monitoring the result. Thank you for your patience as we worked to resolve this issue. If you are still experiencing errors when accessing Opal, please reach out to support Apr 2, 21:50:26 GMT+0 - Resolved - This incident has been 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. Please reach out to support if you have any questions or concerns. Jun 2, 20:58:30 GMT+0 - Postmortem - Following this incident between 2:06pm PDT and 2:27pm PDT on 4/2/2025, where Opal web pages were displaying an error and lacked styling, our engineering team has published a report detailing the root cause of this issue and our team's response efforts. We apologize for any disruption this may have caused and appreciate your patience while our team worked to resolve this issue. You can find the full report here: [\[LINK\]](https://www.notion.so/opal-security/External-2025-04-02-Opal-Pages-Erroring-out-202b8b94ee958018a8d0c68671410b23?source=copy%5Flink) Type: Incident

Duration: 38 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>21:12:21</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating an incident where pages are displaying an error: `An error occurred while rendering this page. It's been logged and the team has been alerted. If this is an emergency, please reach out to your Admin or Opal Support.` Thank you for your patience!.</p> <p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>21:19:41</var> GMT+0</small><br><strong>Identified</strong> - The team has identified the root cause of the error and are working on a fix. Thank you for your patience while we work to resolve this issue.</p> <p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>21:30:37</var> GMT+0</small><br><strong>Monitoring</strong> - A fix has been implemented and we are currently monitoring the result. Thank you for your patience as we worked to resolve this issue. If you are still experiencing errors when accessing Opal, please reach out to support.</p> <p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>21:50:26</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been 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. Please reach out to support if you have any questions or concerns..</p> <p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>20:58:30</var> GMT+0</small><br><strong>Postmortem</strong> - Following this incident between 2:06pm PDT and 2:27pm PDT on 4/2/2025, where Opal web pages were displaying an error and lacked styling, our engineering team has published a report detailing the root cause of this issue and our team's response efforts. We apologize for any disruption this may have caused and appreciate your patience while our team worked to resolve this issue. You can find the full report here: [\[LINK\]](https://www.notion.so/opal-security/External-2025-04-02-Opal-Pages-Erroring-out-202b8b94ee958018a8d0c68671410b23?source=copy%5Flink).</p> ]]> Wed, 2 Apr 2025 21:12:21 +0000 https://status.opal.dev/incident/cm90famn80002ysewpes4gema https://status.opal.dev/incident/cm90famn80002ysewpes4gema Sporadic issues with viewing access rules 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. Type: Incident

Duration: 6 hours and 15 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 17</var>, <var data-var='time'>17:32:57</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Mar <var data-var='date'> 17</var>, <var data-var='time'>23:48:18</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 17 Mar 2025 17:32:57 +0000 https://status.opal.dev/incident/cm8dceurc004xwlp5cyj0clla https://status.opal.dev/incident/cm8dceurc004xwlp5cyj0clla Partially degraded manual sync Type: Incident Duration: 39 minutes Affected Components: App Mar 10, 13:04:59 GMT+0 - Investigating - We are currently investigating this incident. Mar 10, 13:08:57 GMT+0 - Identified - We are continuing to work on a fix for this incident. Mar 10, 13:39:16 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Mar 10, 13:44:13 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 39 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 10</var>, <var data-var='time'>13:04:59</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Mar <var data-var='date'> 10</var>, <var data-var='time'>13:08:57</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Mar <var data-var='date'> 10</var>, <var data-var='time'>13:39:16</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Mar <var data-var='date'> 10</var>, <var data-var='time'>13:44:13</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 10 Mar 2025 13:04:59 +0000 https://status.opal.dev/incident/cm832ra9n001b135xayco352e https://status.opal.dev/incident/cm832ra9n001b135xayco352e Slack Integration Erroring Type: Incident Duration: 8 hours and 47 minutes Feb 27, 01:01:19 GMT+0 - Resolved - Slack has resolved their incident and operations are back to normal. Feb 26, 16:14:07 GMT+0 - Monitoring - Slack is currently having an outage that is causing users to experience an error: operation\_timeout upon requesting, and other notifications to not be sent. Updates on this incident from Slack can be found at <https://slack-status.com/2025-02/1b757d1d0f444c34>. Type: Incident

Duration: 8 hours and 47 minutes

<p><small>Feb <var data-var='date'> 27</var>, <var data-var='time'>01:01:19</var> GMT+0</small><br><strong>Resolved</strong> - Slack has resolved their incident and operations are back to normal..</p> <p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>16:14:07</var> GMT+0</small><br><strong>Monitoring</strong> - Slack is currently having an outage that is causing users to experience an error: operation\_timeout upon requesting, and other notifications to not be sent. Updates on this incident from Slack can be found at <https://slack-status.com/2025-02/1b757d1d0f444c34>..</p> ]]> Wed, 26 Feb 2025 16:14:07 +0000 https://status.opal.dev/incident/cm7m48ae1000fvl9cmoif13p2 https://status.opal.dev/incident/cm7m48ae1000fvl9cmoif13p2 AWS API operational issue affecting sync and propagation of AWS resources. Type: Incident Affected Components: App Feb 25, 12:15:00 GMT+0 - Resolved - Due to AWS operational issue, sync and propagation errors were observed for AWS resources between 4:13 AM and 4:55 AM. Type: Incident

Affected Components:

<p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>12:15:00</var> GMT+0</small><br><strong>Resolved</strong> - Due to AWS operational issue, sync and propagation errors were observed for AWS resources between 4:13 AM and 4:55 AM..</p> ]]> Tue, 25 Feb 2025 12:15:00 +0000 https://status.opal.dev/incident/cm7ktab9i009q13sb83x31s8a https://status.opal.dev/incident/cm7ktab9i009q13sb83x31s8a Planned Database Maintenance Type: Maintenance Duration: 43 minutes Affected Components: App, API Mar 23, 22:00:01 GMT+0 - Identified - Maintenance has not started yet, but will only consist 2-3m of actual downtime. Mar 23, 22:42:42 GMT+0 - Completed - Maintenance is complete. Mar 23, 22:40:00 GMT+0 - Identified - We will restart our production database in preparation for a database version upgrade - no data will be lost during this time. Opal will be unaccessible until the restart is complete. Mar 23, 22:40:00 GMT+0 - Identified - Maintenance has started. We expect this to be complete in 2-3 minutes. Type: Maintenance

Duration: 43 minutes

Affected Components: ,

<p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>22:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance has not started yet, but will only consist 2-3m of actual downtime..</p> <p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>22:42:42</var> GMT+0</small><br><strong>Completed</strong> - Maintenance is complete..</p> <p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>22:40:00</var> GMT+0</small><br><strong>Identified</strong> - We will restart our production database in preparation for a database version upgrade - no data will be lost during this time. Opal will be unaccessible until the restart is complete..</p> <p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>22:40:00</var> GMT+0</small><br><strong>Identified</strong> - Maintenance has started. We expect this to be complete in 2-3 minutes..</p> ]]> Sat, 23 Mar 2024 22:40:00 +0000 https://status.opal.dev/maintenance/cltxhupkv90067bhobr66qppbs https://status.opal.dev/maintenance/cltxhupkv90067bhobr66qppbs