Intermittent slowness in Vector US-EAST-1 region

What to do

• Check whether you use Upstash AWS - US-EAST-1 in us, us-east-1. 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 11h 33m it lasted.

  Anything that failed between 2026-05-29 20:18 UTC and 2026-05-30 07:51 UTC may need a replay.

• Subscribe to Upstash's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=upstash works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Upstash 3

1. investigatingMay 29, 2026, 8:18 PM UTC

   Some Upstash Vector indexes in the US-EAST-1 region may be experiencing intermittent slowness. Initial investigation indicates this may be related to memory pressure on the affected servers. Our team is actively investigating the root cause and working to restore normal performance. We will provide updates as soon as more information is available.

   provider

2. monitoringMay 29, 2026, 11:44 PM UTC

   A fix has been implemented and we are monitoring the results.

   provider

3. resolvedMay 30, 2026, 7:51 AM UTC

   The issue affecting some Upstash Vector indexes in the US-EAST-1 region has been resolved. Our team investigated the incident and identified the conditions that were contributing to elevated memory pressure on the affected servers. We mitigated those conditions by reducing memory utilization on the impacted nodes, rebalancing affected workloads where needed, and increasing available headroom capacity across the region. All affected indexes should now be operating normally, and based on the mitigations applied, we do not expect this issue to recur. We apologize for any inconvenience this may have caused.

   provider

Corrections

None so far.

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