Skip to main content
Svix

US region: delay in delivery of some messages + a small amount of API endpoints had higher latency

Degraded Lasted 0m · started · Svix's page

Level
confirmed
Worst impact
Degraded
Regions
us

What to do

  • Check whether you use Svix 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 0m it lasted.

    Anything that failed between 2023-07-20 20:00 UTC and 2023-07-20 20:00 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 1

  1. resolved

    There was delay in sending messages in the US region and higher latency in some API endpoints. As for the latency: around 0.003% of the requests during this period had a "client disconnect" (which means that the client was disconnected before the server responded which usually means a client timeout or a networking issue), and a total of 2 "create message" calls took more than 5 seconds (across all customers, so a very tiny fraction of the requests).

    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-726679cd29

Is Svix still down?

No, this incident was resolved 2023-07-20 20:00 UTC. For Svix's live state, see https://down.guide/svix.

How long did it last?

0m, from 2023-07-20 20:00 UTC to 2023-07-20 20:00 UTC, by the times Svix posted.

What was affected?

Svix named 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.