Svix: Most routes 5xx in the US region [resolved]
Affected components: API
Timeline of updates
- investigating
We are currently investigating this issue.
- investigating
Still investigating.
- investigating
We are still investigating, but we put mitigating changes in place.
- monitoring
The service is back up. We are still monitoring, but everything is operational.
- resolved
The issue has been resolved, though we are still trying to locate the root cause. There were no deploys today (Saturday), so it's not due to any change on our end, and the activity doesn't look unusual. For whatever reason our API workers went from ~10% utilization (normal) to 100% in a short span of time. We are investigating with AWS. Update: after investigating with AWS for a few hours, neither they nor us are able to understand the reason for the memory usage jump though their and our metrics don't indicate any change in load, underlying systems, or anything like that. They've indicated that OOM can happen even if there hasn't been any indication to that in the AWS metrics. We are still investigating.
- postmortem
We are still investigating, but here is our more complete update regarding this incident: [https://www.svix.com/blog/we-had-a-partial-outage/](https://www.svix.com/blog/we-had-a-partial-outage/)
Changes Rewindex caught on this incident
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).