Elevated response times in the US region for a small percentage of the requests

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-08-24 16:00 UTC and 2023-08-24 16: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. resolvedAug 24, 2023, 4:00 PM UTC

   There were elevated response times in the US region for a small percentage of the requests. The issue was due to a memory leak in a new third party library we integrated with, which caused some nodes to operate with constrained resources (heavy CPU/MEM usage). This fixed itself automatically by killing the affected nodes (each one as it exhausted its resources over the span of a few minutes) and starting new ones instead. The team has also deployed a fix to revert the inclusion of the new library pending further investigation on why this was happening, and why it wasn't detected in the staging environment.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.