Skip to main content
Flagsmith

Slow response times for Edge API requests

Degraded Lasted 29m · started · Flagsmith's page

Level
confirmed
Worst impact
Degraded
Components
Edge API
Down Index
30of 100

What to do

  • Check whether you use Flagsmith Edge API. 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 29m it lasted.

    Anything that failed between 2023-07-10 12:29 UTC and 2023-07-10 12:58 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. investigating

    We are currently investigating this issue.

    provider

  2. identified

    We have identified an issue caused by a downstream service which is causing a knock on effect to our performance. We are currently deploying a change to remove the downstream service.

    provider

  3. monitoring

    The downstream service has been successfully removed. Response times have returned to normal. We are continuing to monitor the situation.

    provider

  4. resolved

    This incident has been resolved.

    provider

  5. postmortem

    ## Timeline At 12:15pm UTC, we were notified of increased response times on a number of our Edge API endpoints. Investigation showed nothing immediately obvious but we suspected that it could be caused by Sentry, our APM tool. We set about removing the Sentry initialisation from our code and deployed it as soon as we could. At 12:48pm UTC, this change was deployed and we observed the response times decrease immediately. At 12:52pm UTC our monitoring confirmed that the average response time had returned to normal. ## Next Steps * Look into improvements to reduce / remove the impact of Sentry issues on our Edge API. * Decrease the shutdown timeout of the Sentry SDK. * Look at using [Sentry relay](https://docs.sentry.io/product/relay) to remove the impact on core Edge API services. ‌ * Add integration tests to simulate performance degradation / outages from all downstream services.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-70f4cbebdc

Is Flagsmith still down?

No, this incident was resolved 2023-07-10 12:58 UTC. For Flagsmith's live state, see https://down.guide/flagsmith.

How long did it last?

29m, from 2023-07-10 12:29 UTC to 2023-07-10 12:58 UTC, by the times Flagsmith posted.

What was affected?

Flagsmith named Edge API.

What caused it?

Flagsmith hasn't published a root cause. If it does, it shows here.

Where does this come from?

Flagsmith's official status page, https://status.flagsmith.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.