- Level
- confirmed
- Worst impact
- Degraded
- 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 2h 50m it lasted.
Anything that failed between 2026-09-03 19:41 UTC and 2026-09-03 22:31 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 4
- investigating
Engineers are investigating a small number of errors and timeouts in the US region affecting some message APIs
provider
- investigating
Engineers are continuing to investigate the issue. A vanishingly small number of create-message requests (fewer than 90) are affected. Some customers may see data population delays in the list-message endpoints.
provider
- identified
Engineers have identified the problem and applied a fix; queues are catching up
provider
- resolved
This incident is resolved
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-01e5a32ed4
Is Svix still down?
No, this incident was resolved 2026-09-03 22:31 UTC. For Svix's live state, see https://down.guide/svix.
How long did it last?
2h 50m, from 2026-09-03 19:41 UTC to 2026-09-03 22:31 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.