- Level
- confirmed
- Worst impact
- Degraded
- 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 2025-01-20 01:52 UTC and 2025-01-19 13:15 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
Sorry also for not updating the status page before, it looked ephemeral when it first surfaced. The issue was one API node that was having networking issues and was failing to connect to the rest of the systems and was timing out while at it. Only requests routed to this API node were affected, so retries would succeed. It's now been 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-7ead079f93
Is Svix still down?
No, this incident was resolved 2025-01-19 13:15 UTC. For Svix's live state, see https://down.guide/svix.
How long did it last?
0m, from 2025-01-20 01:52 UTC to 2025-01-19 13:15 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.