- Level
- confirmed
- Worst impact
- Degraded
- Components
- API
- Down Index
- 22of 100
What to do
Check whether you use Svix API. 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 47m it lasted.
Anything that failed between 2023-02-24 21:10 UTC and 2023-02-24 21:57 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 2
- monitoring
We accidentally created multiple incidents for this. Removed the extra ones, here is the original text: We are investigating the root cause, but there was an issue that caused elevated errors (tiny fraction of traffic) for some API endpoints. A fix has been deployed, but we are still monitoring.
provider
- resolved
The issue has been fixed, and we finished monitoring. There was an issue with one of our redis shards acting up due to an issue with the code implementing endpoint rate limiting. We are working on a long term fix.
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-116ee4c8d8
Is Svix still down?
No, this incident was resolved 2023-02-24 21:57 UTC. For Svix's live state, see https://down.guide/svix.
How long did it last?
47m, from 2023-02-24 21:10 UTC to 2023-02-24 21:57 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.