- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
What to do
Check whether you use Svix 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 0m it lasted.
Anything that failed between 2026-07-17 21:00 UTC and 2026-06-22 20:45 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
Svix experienced elevated latency and a small number of errors in the US region between 19:45Z and 20:33Z due to a configuration change that enabled an experimental idempotency flow for an unexpectedly-large number of users. Approximately 12 requests saw 5XX errors during this period, and several thousand requests took longer than expected. This incident has been fully remediated.
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-baa8b0a95c
Is Svix still down?
No, this incident was resolved 2026-06-22 20:45 UTC. For Svix's live state, see https://down.guide/svix.
How long did it last?
0m, from 2026-07-17 21:00 UTC to 2026-06-22 20:45 UTC, by the times Svix posted.
What was affected?
Svix named 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.