Is LaunchDarkly Down Right Now? Discover if there is an ongoing service outage.

Users of CUPED-adjusted iterations in experimentation may be missing data from June 11th 4:30AM PST to June 13th 10AM PST. There is no underlying data loss and our engineers are working to backfill this data as quickly as possible. We will provide another update once the missing data has been fully restored.

LaunchDarkly customers leveraging the Cloudflare Edge SDK may experience intermittent delays in processing flag changes. This is due to broad platform wide outages at Cloudflare. We're continuing to investigate the status with this partner. All other edge SDK's should be functioning normally. We'll post an update when available from Cloudflare.

We are currently experiencing elevated error rates for users making scheduled changes to flags. Our team is currently investigating and will update when more information is available.

The scheduled maintenance has been completed.

During the month of May 2025, the following SDK versions will reach their end of life in accordance with LaunchDarkly's End of Life policy (https://launchdarkly.com/policies/end-of-life-policy).- .NET Client SDK 5.1.x- .NET Server SDK 8.4.x- Android SDK 5.2.x- C++ Client SDK 3.4.x- C++ Client SDK 3.5.x- C++ Server SDK 3.3.x- C++ Server SDK 3.4.x- Erlang Server SDK 3.2.x- Flutter Client SDK 4.5.x- iOS SDK 9.6.x- iOS SDK 9.7.x- Java Server SDK 7.4.x- JavaScript Client SDK 3.2.x- Node.js Client SDK 3.1.x- React Web SDK 3.1.x- React Web SDK 3.2.x- Vue SDK 2.1.xCustomers using these or older SDK versions should update to supported SDK versions. For more information, read about our supported SDK versions (https://docs.launchdarkly.com/sdk/concepts/versioning#supported-versions).

The issue with intermittent issues with accessing flags has been resolved. Impacted services have returned to normal operation.

The issue with intermittent issues with accessing flags has been identified and a fix has been implemented. We are continuing to monitor the performance of impacted services. We will continue to update this page until it is resolved.

We are investigating reports of intermittent issues with accessing flags. Please continue to monitor this page for updates. We’re working to determine customer impact.

The issue with stale warehouse data export data has been resolved. Impacted services have returned to normal operation.

The data backfill has completed. We will monitor to ensure warehouse data export data is fresh.

The data backfill is still ongoing and on-track for completion in 1.5 hours.

The data backfill is progressing. We are still on track for completion in 3.5 hours.

We have started backfilling the data. We anticipate this to complete in 4.5 hours.

We have identified stale warehouse data export data, starting 6pm UTC yesterday May 28th. This affects downstream services, Snowflake Native Experimentation and Product Analytics. We expect to be able to backfill the data resulting in no data loss.

We are investigating reports of intermittent issues with accessing flags. Please continue to monitor this page for updates. We’re working to determine customer impact.

The data backfill is still ongoing and on-track for completion in 1.5 hours.

The data backfill is progressing. We are still on track for completion in 3.5 hours.

We have started backfilling the data. We anticipate this to complete in 4.5 hours.

We have identified stale warehouse data export data, starting 6pm UTC yesterday May 28th. This affects downstream services, Snowflake Native Experimentation and Product Analytics. We expect to be able to backfill the data resulting in no data loss.

We have identified stale warehouse data export data, starting 6pm UTC yesterday May 28th. This affects downstream services, Snowflake Native Experimentation and Product Analytics. We expect to be able to backfill the data resulting in no data loss.

Between 1:08 PM UTC (6:08 AM PT) and 4:25 PM UTC (9:25 AM PT) on Tuesday, May 27, 2025, customers may have experienced issues with their browser SDKs connecting to the Flag Delivery Network's polling services. This time window represents the outer bounds of potential impact; each customer's actual impact may vary depending on the cache expiry of their environment data. Customers who have implemented their own caching mechanisms outside of LaunchDarkly's SDKs may have had additional recovery time. We resolved the issue and impacted services have returned to normal operation.

Polling connections are continuing to fully recover for impacted browser SDKs.

A fix has been implemented and Browser SDK connections continue to recover while we clear cached errors from the polling service.

Only browser SDKs are affected by this incident. The team has determined that non-browser SDKs (e.g. mobile and desktop SDKs) are unaffected. SDK connections are starting to come back online and recover.

Client-side and mobile SDKs are unable to connect to the Flag Delivery Network’s polling capability. Impacted SDKs will continue to serve last known-good flag values. Server-side SDK connectivity is unaffected, as is client-side and mobile streaming connectivity. The ability to manage flags is also unaffected.

We are continuing to investigate this issue.

Client SDK users are experiencing CORS errors

Between 1:08 PM UTC (6:08 AM PT) and 4:25 PM UTC (9:25 AM PT) on Tuesday, May 27, 2025, customers may have experienced issues with their browser SDKs connecting to the Flag Delivery Network's polling services. This time window represents the outer bounds of potential impact; each customer's actual impact may vary depending on the cache expiry of their environment data.Customers who have implemented their own caching mechanisms outside of LaunchDarkly's SDKs may have had additional recovery time.We resolved the issue and impacted services have returned to normal operation.

Polling connections are continuing to fully recover for impacted browser SDKs.

A fix has been implemented and Browser SDK connections continue to recover while we clear cached errors from the polling service.

Only browser SDKs are affected by this incident. The team has determined that non-browser SDKs (e.g. mobile and desktop SDKs) are unaffected.SDK connections are starting to come back online and recover.

Client-side and mobile SDKs are unable to connect to the Flag Delivery Network’s polling capability. Impacted SDKs will continue to serve last known-good flag values.Server-side SDK connectivity is unaffected, as is client-side and mobile streaming connectivity. The ability to manage flags is also unaffected.

We are continuing to investigate this issue.

Client SDK users are experiencing CORS errors

Client-side and mobile SDKs are unable to connect to the Flag Delivery Network’s polling capability. Impacted SDKs will continue to serve last known-good flag values.Server-side SDK connectivity is unaffected, as is client-side and mobile streaming connectivity. The ability to manage flags is also unaffected.

We are continuing to investigate this issue.

Client SDK users are experiencing CORS errors

We are continuing to investigate this issue.

Client SDK users are experiencing CORS errors

Backfill for Snowflake data export has been completed. All data should now be available.

We have identified partial missing data from our data export to Snowflake warehouses, starting 8pm UTC yesterday May 19th. We expect to be able to backfill the data resulting in no data loss.

We have identified partial missing data from our data export to Snowflake warehouses, starting 8pm UTC yesterday May 19th. We expect to be able to backfill the data resulting in no data loss.

Between 12:15am UTC and 9:25am UTC on May 20, users with custom roles that restricted "ViewEnvironmentSdkKey" access were unable to view restricted environments in the web application. Other roles were not impacted. As of 9:25am UTC this incident was resolved and all permissions are working as expected.

Between 12:15am UTC and 9:25am UTC on May 20, users with custom roles that restricted "ViewEnvironmentSdkKey" access were unable to view restricted environments in the web application. Other roles were not impacted. As of 9:25am UTC this incident was resolved and all permissions are working as expected.

The issue with Data Export transfers has been resolved. All data transfer is up to date and the service has returned to normal operation.

Customers are experiencing delays with Data Export transfers. No data has been lost. We have identified the issue and are deploying a fix now.

Customers are experiencing delays with Data Export transfers. We are investigating and will provide updates as they become available.

Customers are experiencing delays with Data Export transfers. We are investigating and will provide updates as they become available.

The issue with loading flags in the LaunchDarkly UI has been resolved. Impacted services have returned to normal operation.

Some customers are unable to load the flags list in the LaunchDarkly UI. We are investigating and will provide updates as they become available.

Some customers are unable to load the flags list in the LaunchDarkly UI. We are investigating and will provide updates as they become available.

The issue with with the docs site has been resolved. Impacted services have returned to normal operation.

Some users are unable to load our docs site, https://launchdarkly.com/docs/home. We are investigating and will provide updates as they become available.

Some users are unable to load our docs site, https://launchdarkly.com/docs/home. We are investigating and will provide updates as they become available.

The issue with editing experiments has been resolved.

Experimentation customers are currently unable to edit experiments. Running experiments are otherwise unaffected, and customers are still able to create new experiments.

Experimentation customers are currently unable to edit experiments. Running experiments are otherwise unaffected, and customers are still able to create new experiments.

Errors due to rate limiting have been resolved, and backfilling of data to customers' warehouses has been completed. Snowflake Data Export is fully operational again.

We are now seeing customers receive data through data export. However, errors due to rate limiting have not been fully resolved; instead, they are happening less frequently. We will continue to tune the parameters around max concurrent transfers, and we will continue to monitor as we work on an eventual fix for data export

Customers using Snowflake Data Export may have received partial or no data since April 30. We are continuing to work with our export orchestration provider to resolve this issue. Once this issue is resolved, we will start work to backfill data, since we are still receiving data; only the ability to export said data is affected by this incident.

Customers using Data Export may have received partial or no data since April 30. We are now tuning the number of max concurrent transfers to see if this will mitigate or resolve errors for data transfer, and we will continue to monitor this incident until resolution.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently seeing elevated errors when creating guarded and progressive rollouts. Ongoing rollouts are not impacted.

We are currently seeing elevated errors when creating guarded and progressive rollouts. Ongoing rollouts are not impacted.

Customers using Data Export may have received partial or no data since April 30. We are now tuning the number of max concurrent transfers to see if this will mitigate or resolve errors for data transfer, and we will continue to monitor this incident until resolution.

The scheduled maintenance has been completed.

During the month of April 2025, the following SDK versions will reach their end of life in accordance with LaunchDarkly's End of Life policy (https://launchdarkly.com/policies/end-of-life-policy).- .NET Server SDK 8.2.x- .NET Server SDK 8.3.x- Android SDK 5.1.x- Cloudflare SDK 2.4.x- Flutter Client SDK 4.4.x- Go Server SDK 7.2.x- Go Server SDK 7.3.x- Java Server SDK 7.3.x- Node.js Server SDK 9.2.x- Node.js Server SDK 9.3.x- Python Server SDK 9.3.x- React Native SDK 10.0.x- Ruby Server SDK 8.3.xCustomers using these or older SDK versions should update to supported SDK versions. For more information, read about our supported SDK versions (https://docs.launchdarkly.com/sdk/concepts/versioning#supported-versions).

The issue with delayed flag insights charts has been resolved. Impacted services have returned to normal operation

The issue with delayed flag insights charts has been identified and a fix has been implemented, AI config usage charts are no longer delayed. We are continuing to monitor the performance of impacted services. We will continue to update this page until it is resolved.

Some customers are experiencing delayed flag insights and AI config usage charts. We are investigating and will provide updates as they become available.

Some customers are experiencing delayed flag insights and AI config usage charts. We are investigating and will provide updates as they become available.

The scheduled maintenance has been completed.

Older API versions will be deprecated on April 30, 2025. Upgrade to API 20240415 for faster performance and new features.Please note that SDKs are not impacted by these changes.Learn More – REST API migration guide: https://docs.launchdarkly.com/home/guides/api/api-migration-guide/Questions? Email support@launchdarkly.com

Some customers experienced elevated error rates establishing new connections to LaunchDarkly streaming service from server side SDKs in streaming mode between 15:25 and 15:40 PT. The server side polling and client side SDKs were not impacted. The issue is resolved and service has returned to normal operation.

The issue with server-side SDKs has been resolved. Impacted services have returned to normal operation.

All delayed flag evaluation data has been caught up and fully processed.

We have resolved the underlying issue and are now processing the backlog of flag evaluation data. We expect to fully catch up to real-time processing within the next 60 minutes.

We have identified an issue causing delayed flag evaluation data in the web app. Our engineers are currently working on the fix and we'll provide another update shortly.

We have resolved the underlying issue and are now processing the backlog of flag evaluation data. We expect to fully catch up to real-time processing within the next 60 minutes.

We have identified an issue causing delayed flag evaluation data in the web app. Our engineers are currently working on the fix and we'll provide another update shortly.

Our vendor has pushed an update to resolve the intermittent errors on the Docs site. No further issues have been observed.

We are continuing to monitor traffic on the docs site and have scheduled time with our vendor tomorrow afternoon PT to further troubleshoot.

We are continuing to investigate the issue with our vendor. Our monitoring shows a very small portion of visitors to the docs site experienced these errors from approximately 1:10PM - 2:07PM PT.

The documentation site is experiencing intermittently long page load times. Some customers may experience HTTP 504 errors when viewing pages on the docs site. We're investigating this issue in collaboration with our vendor.

No further issues have been observed or reported related to the incident.

A fix has been implemented to address the errors when creating a new AI configuration. We will continue to monitor for the next several minutes to ensure full feature restoration.

The issue has been identified and we are working on remediation. We will send an update shortly to confirm the issue with AI Configs has been resolved.

Early access customers using the AI Configs feature are experiencing elevated errors beginning at 12:18UTC. Customers may receive an error when attempting to create a new AI configuration. We are continuing to investigate the root cause of these errors and will provide an update when available.

Early access customers using the AI Configs feature are experiencing elevated errors beginning at 12:18UTC. Customers may receive an error when attempting to create a new AI configuration. We are continuing to investigate the root cause of these errors and will provide an update when available.

We are continuing to monitor traffic on the docs site and have scheduled time with our vendor tomorrow afternoon PT to further troubleshoot.

We are continuing to investigate the issue with our vendor. Our monitoring shows a very small portion of visitors to the docs site experienced these errors from approximately 1:10PM - 2:07PM PT.

The documentation site is experiencing intermittently long page load times. Some customers may experience HTTP 504 errors when viewing pages on the docs site. We're investigating this issue in collaboration with our vendor.

The documentation site is experiencing intermittently long page load times. Some customers may experience HTTP 504 errors when viewing pages on the docs site. We're investigating this issue in collaboration with our vendor.

The scheduled maintenance has been completed.

During the month of March 2025, the following SDK versions will reach their end of life in accordance with LaunchDarkly's End of Life policy (https://launchdarkly.com/policies/end-of-life-policy).- .NET Client SDK 5.0.x- .NET Server SDK 8.0.x- .NET Server SDK 8.1.x- Android SDK 5.0.x- Erlang Server SDK 3.1.x- Flutter Client SDK 4.1.x- Flutter Client SDK 4.2.x- Flutter Client SDK 4.3.x- Go Server SDK 7.0.x- Go Server SDK 7.1.x- Haskell Server SDK 4.0.x- iOS SDK 9.4.x- iOS SDK 9.5.x- Java Server SDK 7.2.x- JavaScript Client SDK 3.1.x- Lua Server SDK 2.0.x- Node.js Client SDK 3.0.x- PHP SDK 6.0.x- Python Server SDK 9.2.x- React Web SDK 3.0.x- Roku SDK 2.0.x- Ruby Server SDK 8.2.x- Rust Server SDK 2.0.x- Vue SDK 2.0.xCustomers using these or older SDK versions should update to supported SDK versions. For more information, read about our supported SDK versions (https://docs.launchdarkly.com/sdk/concepts/versioning#supported-versions).

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented, and we are monitoring the results. Error rates have now returned to baseline.

We are currently investigating an increase in errors received by clients of the Streamer SDK in APSE1. Other regions are not impacted.

This incident has been resolved.

A fix has been implemented, and we are monitoring the results. Error rates have now returned to baseline.

We are currently investigating an increase in errors received by clients of the Streamer SDK in APSE1. Other regions are not impacted.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating malformed links on our docs site.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating malformed links on our docs site.

This incident has been resolved.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

Some customers are experiencing issues creating Guarded Rollouts. Existing Guarded Rollouts are not impacted. We are investigating and will provide updates as they become available.

The issue with Guarded Rollouts has been resolved. Impacted services have returned to normal operation

The issue with Guarded Rollouts has been identified and a fix has been implemented. We are continuing to monitor the performance of impacted services. We will continue to update this page until it is resolved.

The issue with Guarded Rollouts has been identified and a fix is being implemented. We are continuing to monitor the performance of impacted services. We will continue to update this page until it is resolved.

Some customers are experiencing issues with Guarded Rollouts running too quickly. We are investigating and will provide updates as they become available.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We have identified the cause of the problem and are working to implement a solution.

We are currently investigating an issue with displaying context info and autocomplete on flag/segment configuration. We'll update as we have more information.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We have determined that occurs in accounts that have flag key conventions defined for the project.

We are investigating the issue.

The issue with Email notifcations has been resolved. Impacted services have returned to normal operation

A fix has been implemented and we are monitoring the results.

Customers are experiencing delays with email notifications. We are actively working to resolve this issue while we investigate other potential impacts.

This incident has been resolved.

The cause has been identified and data is flowing again. We are working on clearing the backlog.

Data in our Flag Insights feature is partially delayed beginning at around 1 PM Pacific Time. We are investigating the issue.

Between 8:29am - 8:41am PT, our docs pages were slow or unresponsive, due to an outage with an 3rd party. They have resolved the issue and our docs are available now.

The issue with customers using polling SDKs in the EU instance experiencing flag update delays up to 90 minutes has been resolved. Impacted services have returned to normal operation.

A fix has been implemented and we are monitoring the results.

Customers using polling SDKs in the EU instance may be experiencing flag update delays up to 90 minutes. We are investigating and will provide updates as they become available.

The issue with increased latency and error rates across APIs has been resolved. Impacted services have returned to normal operation.

We have scaled up and there is now no customer impact. We are continuing to monitor the performance of impacted services. We will continue to update this page until it is resolved.

We believe customer impact is mitigated due to scaling up. We are still investigating root cause.

We are continuing to investigate this issue.

We scaled up infrastructure to mitigate increased latency and error rate. We are continuing to investigate and will provide updates as they become available.

Customers are experiencing increased latency and error rate across all APIs. The team is investigating and we will provide more updates when available.

Some customers may be experiencing polling SDKs intermittently failing to get updates. In most cases we expect these to be succeeding upon retry. We are investigating and will provide updates as they become available.

The issue with delayed historic results for recently started CUPED experiments has been resolved. All data has been backfilled.

We have identified and mitigated an issue that resulted in delayed historic results for recently started CUPED experiments. With the underlying cause addressed, current CUPED results now show correct data. Additionally, we're backfilling historic result data and will post another update once this backfill is complete.

The issue with delayed flag updates for small number of customers has been resolved. Impacted services have returned to normal operation. The impact was limited to less than 1% of customers.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

We have identified the issue with a small number of customers experiencing delayed flag updates in the US region, starting at 9:04AM PST. We are working on a fix to this.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We suspect this is related to the incident in one of the downstream providers: https://health.aws.amazon.com/health/status - And we are currently monitoring that incident right now.

We are currently investigating the issue. Reloading the page could make it work.

This incident has been resolved.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

We are investigating a bug on Flag Targeting page, if there is an experiment running on the flag's default rule, the default rule is not showing up. The actual audience allocation and data are not affected.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently investigating an issue where all customers are unable to create or modify Vercel integrations. Existing Vercel integrations remain functional and are not affected by this issue.

This incident has been resolved.

The initial fix resolved all teams issues for this incident. Permissions were not affected. There was no data loss and flag delivery was not impacted.

We have resolved the issue where some teams were not showing in the UI. Teams without members were not showing in the teams UI, all teams are displaying now. There is a related issue where teams with permissions of "No Access" are being overly restricted. We're confirming that the fix identified resolves this issue as well.

The issue has been identified and a fix is being implemented.

We are currently investigating an incident where some teams are missing from the UI. Data loss is not expected. Flag Delivery is not impacted.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating an issue serving relay proxy automatic configuration.

The issue with missing some aggregate usage data in the account dashboards has been resolved. The backfill of missing data has completed and the impacted services have returned to normal operation. There was no data loss experienced.

The backfill of missing account usage charts data is still in progress. We have backfilled most data, but small portion still remains. We expect the process to complete within the next day. We will post another update and resolve this incident once the backfill is fully completed.

The issue with missing some aggregate usage data in the account dashboards has been identified and a fix has been implemented. We are in the process of backfilling the missing data. We will post another update and resolve this incident once the backfill process is completed.

We have identified the issue with customer account dashboards missing some usage aggregate data since Dec 20. There is no data loss. We are working on the fix and will post an update once issue is resolved. Service operation is not impacted, the issue is limited to account usage charts.

The server-side SDK initialization issue has been successfully resolved.

We are continuing to monitor for any further issues.

Between 16:35 and 16:42 server-side SDKs experienced an elevated error rate during initialization. The affected SDKs automatically retried initialization. The problem has been addressed and we are monitoring the issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

All customers are experiencing the missing percentage rollout option from the Serve dropdown in the feature flag rule edit page. Feature flags that are not using percentage rollout or already have the percentage rollout can still be created or edited. Percentage rollout in a rule can still be created via API. We have identified the issue and are working on a fix. We will provide updates as they become available.

The issue with delayed experimentation results processing has been resolved. Impacted services have returned to normal operation.

The issue with delayed experimentation results processing has been identified and a fix has been implemented. We are continuing to monitor the performance of impacted services. We will continue to update this page until it is resolved. Customers may begin seeing recovery of affected services at this time.

All customers are experiencing delays with experimentation results processing. We have identified the issue and are continuing our work to resolve it.

All customers are experiencing delays with experimentation results processing. We are investigating and will provide updates as they become available. Data loss is not expected.

The issue with segments and segment approvals has been resolved. Impacted services have returned to normal operation

The issue related to segments and approvals has been identified. We are continuing our work to resolve it.

Some customers may be experiencing impacts with segments when segment approvals are applied. We are investigating and will provide updates as they become available.

The issue with delayed events has been resolved. It has been determined that this incident has no customer impact.

We are investigating a potential service interruption with our internal data warehouse that may impact some customers. A very small number of records are delayed in processing before being available for reporting within the system. Please continue to monitor this page for updates.

We have fixed the issue with the "login in with Google" button.

We have fixed the issue with the "login in with Google" button and are monitoring the results.

We have identified the issue with the "login in with Google" button and are continuing our work to resolve it.

We're investigating an issue affecting signing in to app.launchdarkly.com with Google. This issue does not affect other sign in methods or active sessions. As a temporary workaround, users can log in through Google using the pop-up on the right-hand side of the screen.

The issue with emails being marked as spam has been resolved. Impacted services have returned to normal operation

The issue with transactional emails being identified as spam has been identified and a fix is in progress. We are continuing to monitor the performance of this issue, as email may continue to be identified as spam for a short time. We will continue to update this page until it is resolved.

Some customers are experiencing LaunchDarkly-sourced emails being marked as spam. We have identified the issue and are working to resolve it.

The issue with the edge integration has been resolved. Impacted services have returned to normal operation

Some customers who use the edge integration are experiencing delayed flag updates. We are investigating and will provide updates as they become available.

This incident has been resolved.

We have identified the issue. This is only impacting customers with older SDKs that do not support holdouts. We are working on a fix.

We are investigating reports that the view for managing experimentation holdouts is blank for some customers. All other views are unaffected.

The issue with the Microsoft Teams integration has been resolved. Impacted services have returned to normal operation

The Microsoft Teams integration issue is now understood, and a fix is in the process of being implemented.

All customers are experiencing a failure of the Microsoft Teams integration. We are investigating and will provide updates as they become available.

For about a 15 minute span we noticed an increased rate of new SDK connections were failing. This likely affected some customers, but not all. The issue has been resolved. Impacted services have returned to normal operation, and we are continuing to monitor the situation. Flag Delivery was not impacted and there was no data loss experienced.

This incident has been resolved.

The issue with "off" variation configuration has been identified and a fix is being implemented. We are continuing to monitor the performance of impacted services. We will continue to update this page until it is fully resolved.

Self-service customers are experiencing an inability to change the flag configuration that the "off" variation severs via the product interface. We are investigating and will provide updates as they become available.

The issue with the Jira integration errors has been resolved with the LaunchDarkly for Jira version 1.0.18-AC from Atlassian Marketplace. Affected customers who have not yet received the update from Atlassian may manually update the integration from Jira administration.

We have published the fix for Jira integration. The fix is expected to automatically roll out to affected customers' Jira instances within the next several hours. As a workaround to waiting, customers may manually update the integration from their Jira administration.

We have identified the issue with errors when using our Jira integration. We are continuing our work to resolve it.

We are investigating reports with customers experiencing errors when using Jira integration. We are investigating and will provide updates as they become available.

We identified the root cause and restored service for the affected customers. 4 customers were affected.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.