- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Svix. 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 2022-04-05 18:54 UTC and 2022-04-05 18:39 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 1
- resolved
Due to a race condition in a complex deployment, newly deployed API endpoints were trying to access resources using a stale configuration. Only a few API calls were affected as it only affected a few API endpoints before the deployment completed and updated the configuration for all of them. We have taken precautions for preventing this from ever happening again.
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-ede0d632af
Is Svix still down?
No, this incident was resolved 2022-04-05 18:39 UTC. For Svix's live state, see https://down.guide/svix.
How long did it last?
0m, from 2022-04-05 18:54 UTC to 2022-04-05 18:39 UTC, by the times Svix posted.
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.