- Level
- confirmed
- Worst impact
- Degraded
- 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 25m it lasted.
Anything that failed between 2023-12-10 03:20 UTC and 2023-12-10 03:45 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
AWS have not updated their status page, but we are seeing increased errors from internal AWS services in our US region. We are closely monitoring this, but nothing is affected other than the message listing.
provider
- identified
AWS have now updated their status page to indicate that there is indeed an error on their end.
provider
- monitoring
Looks like AWS fixed the issue, we are monitoring.
provider
- resolved
AWS have indeed fixed their issue, and list message is not up to date.
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-849754ee41
Is Svix still down?
No, this incident was resolved 2023-12-10 03:45 UTC. For Svix's live state, see https://down.guide/svix.
How long did it last?
25m, from 2023-12-10 03:20 UTC to 2023-12-10 03:45 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.