Skip to main content
Svix

Increased latency and failures for non-create-message endpoints (create message not affected)

Partial outage Lasted 20m · started · Svix's page

Level
confirmed
Worst impact
Partial outage
Components
API
Down Index
30of 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 20m it lasted.

    Anything that failed between 2024-09-30 19:28 UTC and 2024-09-30 19:49 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

  1. investigating

    We are currently investigating this issue.

    provider

  2. investigating

    Message delivery is not affected, but other API calls are seeing increased latency.

    provider

  3. monitoring

    A fix has been deployed, we are monitoring to make sure everything is working as expected.

    provider

  4. resolved

    The issue is confirmed to be fixed.

    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-7cc51dc7a2

Is Svix still down?

No, this incident was resolved 2024-09-30 19:49 UTC. For Svix's live state, see https://down.guide/svix.

How long did it last?

20m, from 2024-09-30 19:28 UTC to 2024-09-30 19:49 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.