- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 18of 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 2025-07-18 01:29 UTC and 2025-07-17 23:00 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 the throttling code, some message may have been throttled for a much longer time than they were supposed to. The issue has been fixed and everything should be back in order. No action needed.
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-c51a0a17d3
Is Svix still down?
No, this incident was resolved 2025-07-17 23:00 UTC. For Svix's live state, see https://down.guide/svix.
How long did it last?
0m, from 2025-07-18 01:29 UTC to 2025-07-17 23:00 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.