- Level
- confirmed
- Worst impact
- Operational
- Regions
- us
What to do
Check whether you use Svix in us. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide 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 2022-08-10 00:09 UTC and 2022-08-09 23:30 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 an internal AWS issue the idempotency mechanism was failing for some of the requests with an idempotency key set (only US region affected).
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-0a02ac3d78
Is Svix still down?
No, this incident was resolved 2022-08-09 23:30 UTC. For Svix's live state, see https://down.guide/providers/svix.
How long did it last?
0m, from 2022-08-10 00:09 UTC to 2022-08-09 23:30 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.