ChangesFlagsmithCore API is not responding
Flagsmith: Critical incident: Core API is not responding
Summary
Summary pending. The diff below shows exactly what changed.
Incident page: the full timeline of updates
What changed
Struck in red is what Flagsmith removed; blue is what they added. Muted text is unchanged context.
Before: not present
After: Core API is not responding
Before: not present
After: critical
Before: not present
After: resolved
Before: not present
After: 2022-07-10 17:53 UTC
Before: not present
After: 2022-07-10 21:15 UTC
Before: not present
After: Admin API, API - Core API
Before: not present
After: We are investing an outage on our Core API.
Before: not present
After: This looks to be an issue with AWS where our Core API is located. We are investigating.
Before: not present
After: AWS have confirmed an outage in their EU-West-2 data center. We are monitoring and waiting on AWS to provide updates.
Before: not present
After: AWS are restoring services. We hope to have the API back up shortly.
Before: not present
After: The DB has recovered. API latency is high as our ECS cluster scales out.
Before: not present
After: We are still seeing issues with the ECS cluster scaling out correctly, again down to the recent AWS eu-west-2 outage. We are monitoring.
Before: not present
After: This incident has been resolved.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
Sunday, July 10, 2022
1 incident change
- CriticalCritical incident
Core API is not respondingthis change