- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 18of 100
What to do
Check whether your product depends on Flagsmith. 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 0m it lasted.
Anything that failed between 2024-07-04 08:36 UTC and 2024-07-04 08:36 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 1
- resolved
Our Core API was overwhelmed by massive traffic spike, causing the core SQL database to become extremely slow. This led to ECS tasks failing the health checks, prompting the load balancer to start and stop new tasks, which in turn added more load to the already maxed-out database. We tried several approaches to rate limiting the source of the traffic, but eventually had to temporarily stop traffic at the load balancer for 2 minutes in order to stabilise the system. We are working on implementing AWS API Gateway to include rate limiting at the gateway level to avoid these sort of incidents in the future.
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-9505cfc680
Is Flagsmith still down?
No, this incident was resolved 2024-07-04 08:36 UTC. For Flagsmith's live state, see https://down.guide/flagsmith.
How long did it last?
0m, from 2024-07-04 08:36 UTC to 2024-07-04 08:36 UTC, by the times Flagsmith posted.
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.