Resolved incident
Most routes 5xx in the US region [resolved]
Svix · Major · Started
- Duration
- 48m
- Severity
- Major
- Status
- Postmortem
Summary
Major · 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/)
Event timeline
How this incident unfolded, from the official status page.
Investigating
Svix
We are currently investigating this issue.
Investigating
Svix
Still investigating.
Investigating
Svix
We are still investigating, but we put mitigating changes in place.
Monitoring
Svix
The service is back up. We are still monitoring, but everything is operational.
Resolved
Svix
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
Svix
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/)