- Level
- confirmed
- Worst impact
- Partial outage
- Components
- API
- Regions
- us
What to do
Check whether you use Svix API in us. 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 48m it lasted.
Anything that failed between 2023-03-11 20:35 UTC and 2023-03-11 21:23 UTC may need a replay.Subscribe to Svix's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=svix works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Svix 6
- investigating
We are currently investigating this issue.
provider
- investigating
Still investigating.
provider
- investigating
We are still investigating, but we put mitigating changes in place.
provider
- monitoring
The service is back up. We are still monitoring, but everything is operational.
provider
- 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.
provider
- 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/)
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-8ade3d42f8
Is Svix still down?
No, this incident was resolved 2023-03-11 21:23 UTC. For Svix's live state, see https://down.guide/svix.
How long did it last?
48m, from 2023-03-11 20:35 UTC to 2023-03-11 21:23 UTC, by the times Svix posted.
What was affected?
Svix named API in us.
What caused it?
Svix hasn't published a root cause. If it does, it shows here.
Where does this come from?
Svix's official status page, https://status.svix.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.