- Level
- confirmed
- Worst impact
- Partial outage
- 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 1m it lasted.
Anything that failed between 2023-06-06 16:25 UTC and 2023-06-06 16:25 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 6
- investigating
We are currently investigating this issue.
provider
- investigating
Potential fix is being deployed.
provider
- monitoring
Seems to be resolved. Still monitoring.
provider
- monitoring
EDIT: duplicate of the above.
provider
- resolved
It's confirmed to be working. Sorry about that, a post-mortem is coming.
provider
- postmortem
Postmortem: [https://www.svix.com/blog/outage-us-june-2023/](https://www.svix.com/blog/outage-us-june-2023/)
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-dd4f20f690
Is Svix still down?
No, this incident was resolved 2023-06-06 16:25 UTC. For Svix's live state, see https://down.guide/svix.
How long did it last?
1m, from 2023-06-06 16:25 UTC to 2023-06-06 16:25 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.