- Level
- confirmed
- Worst impact
- Degraded
- Components
- API
What to do
Check whether you use Svix API. 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 1h 31m it lasted.
Anything that failed between 2022-11-03 19:10 UTC and 2022-11-03 20:41 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
- identified
One customer who was using the new application metadata feature my experience elevated errors, we have a fix which is being deployed as we speak. Affected people: only people using the new application metadata, only when used with application create when passing the get_if_exists flag, and only for people who have called it within this period.
provider
- monitoring
A fix has been implemented, and we are monitoring to make sure it's all fixed.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- resolved
This incident has 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-335acc20b0
Is Svix still down?
No, this incident was resolved 2022-11-03 20:41 UTC. For Svix's live state, see https://down.guide/providers/svix.
How long did it last?
1h 31m, from 2022-11-03 19:10 UTC to 2022-11-03 20:41 UTC, by the times Svix posted.
What was affected?
Svix named API.
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.