Opal - Notice history

Experiencing partially degraded performance

Okta Integration - Operational

Notice history

Oct 2025

Scheduled jobs failing related to AWS outage
  • Update
    Update

    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.

    To work around these LaunchDarkly errors, please see this document. If you have any questions or need additional assistance, please reach out to our team.

  • Update
    Update

    For self-hosted customers, please see this document 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.

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

  • Identified
    Identified

    We are currently investigating an incident where the LaunchDarkly/AWS 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.

Ongoing AWS Outage
  • Resolved
    Resolved

    https://www.opal.dev/ is back online!

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

Performance issues with visibility limitations
  • Postmortem
    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]

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

  • Identified
    Identified

    We are aware of continued performance issues. We are working on identifying and rolling out a fix.

  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    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!

  • Investigating
    Investigating
    We are aware of long load times for some items with visibility restrictions. Some users are seeing timeout errors. Team is currently investigating.

Sep 2025

Delays in syncing access changes to Azure Enterprise Apps
  • Resolved
    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.

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

GET /groups/{group_id}/users not returning a full list of users when pagination parameters are not set

Aug 2025

Degraded notifications and propagation changes performance
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Identified
    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.

  • Investigating
    Investigating
    We are currently investigating this incident.
Users receiving multiple access expiring notifications
  • Resolved
    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.

  • Identified
    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 2025 to Oct 2025

Next