Increased 502 responses to our Core API

What to do

• Check whether you use Flagsmith Admin API, Admin Dashboard. Check your stack

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

• Confirm your retries, queues and scheduled jobs caught up after the 2d 10h it lasted.

  Anything that failed between 2022-06-24 20:26 UTC and 2022-06-27 07:21 UTC may need a replay.

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

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

Updates from Flagsmith 5

1. investigatingJun 24, 2022, 1:54 PM UTC

   Hi, We are experienced slightly elevated 502 errors returning from our Core API. We believe this is due to a recently introduced piece of code that is consuming more memory than it should be and are working on a fix.

   provider

2. monitoringJun 24, 2022, 2:18 PM UTC

   We have deployed a fix and are monitoring our container memory consumption.

   provider

3. investigatingJun 24, 2022, 8:26 PM UTC

   We are still seeing elevated 502 errors and are continuing to investigate. These issues are isolated to our Core API only and seem to be affecting ~0.1% of Core API requests only. Our Edge API continues to be fully operational.

   provider

4. monitoringJun 26, 2022, 5:51 PM UTC

   The errors have been resolved. We are continuing to monitor this.

   provider

5. resolvedJun 27, 2022, 7:21 AM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

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