- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- eu
What to do
Check whether you use Svix in eu. 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-06-03 00:00 UTC and 2026-06-03 00: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
We experienced an issue where some customer in the EU region experienced elevated response times and error rates. The time frames when this occurred: 23:44 - 23:46, 00:05 - 00:13, 00:38 - 00:48, 03:27 - 03:29, 5:34 - 5:36 UTC. This happened due to a significant spike in traffic (161x traffic the minute before), and the system not scaling fast enough to catch up. This affected customers routed to the same nodes that experienced this load.
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-f9899fc0a0
Is Svix still down?
No, this incident was resolved 2026-06-03 00:00 UTC. For Svix's live state, see https://down.guide/svix.
How long did it last?
0m, from 2026-06-03 00:00 UTC to 2026-06-03 00:00 UTC, by the times Svix posted.
What was affected?
Svix named in eu.
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.