https://approjects-vendor-status-watch.static.hf.space/v/launchdarkly.htmlIncidents from LaunchDarkly's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/n8kkgrxbjkdhlaunchdarkly:2026-08-26T12:45:21.432-07:00Wed, 26 Aug 2026 19:45:21 +0000This incident has been resolved. Between 12:00 and 12:12 PM PDT on August 26, server-side SDKs establishing new streaming connections experienced elevated error rates. Existing streaming connections were not affected, and polling requests continued to be served with error rates below 1%. Some requests to the LaunchDarkly web application also experienced elevated errors between approximately 11:29 AM and 12:03 PM PDT. The issue was caused by an internal configuration change, which has been reverted. All systems have recovered and are operating normally. No customer data was lost or compromised.https://stspg.io/cgfs9bf4w12claunchdarkly:2026-08-24T05:20:53.856-07:00Mon, 24 Aug 2026 12:20:53 +0000Email delivery has been restored as of 2:32 PM UTC. Sign-up verification, password reset, teammate invitation, and notification emails are sending normally again. We are re-sending sign-up verification and password reset emails that failed to deliver during the incident window (August 22, 11:48 PM CDT through today). If you attempted to sign up or reset a password during that period and haven't received an email within the next few hours, please retry the action or contact support. We are continuing to monitor email delivery closely and will post a final update once we've confirmed sustained recovery.https://stspg.io/h8byqm8qtb9plaunchdarkly:2026-08-17T03:36:58.299-07:00Mon, 17 Aug 2026 10:36:58 +0000This incident has been resolved.https://stspg.io/xg4w7vvnrk63launchdarkly:2026-08-14T07:47:16.452-07:00Fri, 14 Aug 2026 14:47:16 +0000The issue is being marked as resolved. We're seeing improved latencies and our systems have recovered.https://stspg.io/2f7v4bt6s4k3launchdarkly:2026-08-07T12:29:40.566-07:00Fri, 07 Aug 2026 19:29:40 +0000SDKs restored to operationalhttps://stspg.io/rg10v64yrrnylaunchdarkly:2026-07-31T10:44:16.431-07:00Fri, 31 Jul 2026 17:44:16 +0000The issue with Observability Traces has been resolved. Missing trace data has been recovered.https://stspg.io/4h85388bhst6launchdarkly:2026-07-28T12:24:00.975-07:00Tue, 28 Jul 2026 19:24:00 +0000The issue with session replay and error ingest has been resolved. We've caught up on all backlogged data as of 1:01pm PT.https://stspg.io/sm5vp8lh0nk5launchdarkly:2026-07-26T11:32:00.000-07:00Sun, 26 Jul 2026 18:32:00 +0000Between 11:32 and 11:48 PT, customers experienced increased latency and elevated error rates on API endpoints. Latency and error rates have returned to normal, and the incident has been resolved.https://stspg.io/3zs2g4y0zjhslaunchdarkly:2026-07-10T10:10:40.002-07:00Fri, 10 Jul 2026 17:10:40 +0000All service availability has been fully restored. Customers using server-side SDKs might need to restart their applications to re-enable the SDKs' connection to LaunchDarkly. Customers using the Relay Proxy may also need to restart their Relay Proxy; in this case, the Relay Proxy should be restarted before restarting their applications that connect to it. To determine if an application needs to be restarted, customers can look at their application logs. Affected SDKs will emit (depending on language) logs containing one of "giving up permanently", "Invalid SDK key", "unauthorized", or "not authorized", or "401". Services which emitted logs such as these before 9:13AM PT may be unable to receive flag updates and will be unable to send events to LaunchDarkly until they are restarted.https://stspg.io/5cz51f7pr4jtlaunchdarkly:2026-07-10T09:16:41.335-07:00Fri, 10 Jul 2026 16:16:41 +0000LaunchDarkly UI has recovered. We will continue to monitor Flag Delivery and event ingest here: https://status.launchdarkly.com/incidents/chywwz01ptb0.https://stspg.io/rgzx37hr3zl0launchdarkly:2026-07-10T09:00:08.000-07:00Fri, 10 Jul 2026 16:00:08 +0000This incident has been resolved.https://stspg.io/3xw9y1f2h5qnlaunchdarkly:2026-07-08T11:03:26.146-07:00Wed, 08 Jul 2026 18:03:26 +0000This incident has been resolved.https://stspg.io/nb74mgrw1279launchdarkly:2026-07-07T08:10:53.595-07:00Tue, 07 Jul 2026 15:10:53 +0000Event ingestion is operating normally. Experimentation results, Guarded Rollouts, and in-product data charts were delayed ~5 min between 7:13–7:53 AM PT. No data was lost. We apologize for any inconvenience.https://stspg.io/2w8p702dlbxslaunchdarkly:2026-07-06T13:30:24.000-07:00Mon, 06 Jul 2026 20:30:24 +0000All error rates have normalized.https://stspg.io/68ggsmfb0zjnlaunchdarkly:2026-07-06T07:33:33.315-07:00Mon, 06 Jul 2026 14:33:33 +0000This incident has been resolved.https://stspg.io/9rgffqd467kslaunchdarkly:2026-07-03T07:29:26.981-07:00Fri, 03 Jul 2026 14:29:26 +0000This incident has been resolved.https://stspg.io/vg7t1f736mf2launchdarkly:2026-06-17T12:43:59.686-07:00Wed, 17 Jun 2026 19:43:59 +0000We're now seeing restored access in the affected regions.https://stspg.io/d0gyxn8gm0vclaunchdarkly:2026-06-15T10:02:31.000-07:00Mon, 15 Jun 2026 17:02:31 +0000The issue with Observability data ingest for OpenTelemetry data has been resolved. Impacted services have returned to normal operation.https://stspg.io/wmq9t01dm9q3launchdarkly:2026-06-11T21:23:30.600-07:00Fri, 12 Jun 2026 04:23:30 +0000Monitoring has confirmed no further impact outside of the initially reported 7:30-7:37pm PT timeframehttps://stspg.io/x49f0n3lpj8hlaunchdarkly:2026-06-08T13:46:00.189-07:00Mon, 08 Jun 2026 20:46:00 +0000This incident has been resolved.https://stspg.io/15mgsktmsg0plaunchdarkly:2026-06-03T12:31:35.585-07:00Wed, 03 Jun 2026 19:31:35 +0000The incident has been resolved and the flag dashboard is successfully loading.https://stspg.io/zlc8rc4zk9pslaunchdarkly:2026-05-22T11:40:19.668-07:00Fri, 22 May 2026 18:40:19 +0000We have confirmed Slack notifications are now coming through for segment approvals again.https://stspg.io/bzbs30xtk414launchdarkly:2026-05-19T07:49:33.049-07:00Tue, 19 May 2026 14:49:33 +0000This incident has been resolved. Event ingestion is operating normally and all Experimentation results and Guarded Rollouts are fully restored. No data was lost. We apologize for any inconvenience caused. Results were delayed from 6:58am PDT to 7:52am PDThttps://stspg.io/f2ykhwd908dhlaunchdarkly:2026-05-15T17:03:59.545-07:00Sat, 16 May 2026 00:03:59 +0000All queued events have been processed and data ingestion is operating normally. No data was lost during this incident.https://stspg.io/v1l6f3sk21yclaunchdarkly:2026-05-05T20:58:38.000-07:00Wed, 06 May 2026 03:58:38 +0000We've implemented a fix and have mitigated impact as of 9:25pm PT. Streaming SDKs should be able to connect successfully at this time.https://stspg.io/7qsrvs23ytf5launchdarkly:2026-05-04T12:47:43.131-07:00Mon, 04 May 2026 19:47:43 +0000All experiment and multi-armed bandit result data is caught up. No data was lost.https://stspg.io/hm8181k3hr9blaunchdarkly:2026-05-04T03:14:58.000-07:00Mon, 04 May 2026 10:14:58 +0000This incident has been resolved.https://stspg.io/1dqjflmxfs45launchdarkly:2026-05-02T05:55:19.012-07:00Sat, 02 May 2026 12:55:19 +0000Experimentation results processing and data warehouse export was caught up as of 12:28 pm PT.https://stspg.io/8xxpdt0nt0kblaunchdarkly:2026-04-30T19:52:00.000-07:00Fri, 01 May 2026 02:52:00 +0000We've identified elevated error rates with server-side streaming initialization requests in the APAC region between 19:52 and 19:56 PT. Some customers may have experienced initialization timeouts despite SDK retries.https://stspg.io/xx3vf1rxqht7launchdarkly:2026-04-30T04:14:58.482-07:00Thu, 30 Apr 2026 11:14:58 +0000We've caught up on the streaming data export backlog.