Elevated Streaming Errors in APAC region

What to do

• Check whether you use LaunchDarkly Server-side streaming API in apac. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 28m it lasted.

  Anything that failed between 2026-05-06 03:58 UTC and 2026-05-06 04:26 UTC may need a replay.

• Subscribe to LaunchDarkly's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=launchdarkly works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from LaunchDarkly 3

1. investigatingMay 6, 2026, 3:58 AM UTC

   We are investigating elevated error rates for streaming initialization in the APAC region. Some customers using streaming server-side SDKs may have experienced longer than normal initialization times or timeouts when connecting to LaunchDarkly.

   provider

2. identifiedMay 6, 2026, 4:00 AM UTC

   We're identified an infrastructure issue causing elevated error rates and are working on a fix.

   provider

3. resolvedMay 6, 2026, 4:26 AM UTC

   We've implemented a fix and have mitigated impact as of 9:25pm PT. Streaming SDKs should be able to connect successfully at this time.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.