Skip to main content
Upstash

Degraded performance on us-east-1 Kafka

Degraded Lasted 3d 17h · started · Upstash's page

Level
confirmed
Worst impact
Degraded
Regions
us, us-east-1
Down Index
31of 100

What to do

  • Check whether you use Upstash 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 3d 17h it lasted.

    Anything that failed between 2024-05-09 14:39 UTC and 2024-05-13 08:30 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. investigating

    We are currently investigating this issue.

    provider

  2. monitoring

    We are working on a fix and monitoring the cluster performance.

    provider

  3. resolved

    This incident has been resolved.

    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-4d8ebda35f

Is Upstash still down?

No, this incident was resolved 2024-05-13 08:30 UTC. For Upstash's live state, see https://down.guide/upstash.

How long did it last?

3d 17h, from 2024-05-09 14:39 UTC to 2024-05-13 08:30 UTC, by the times Upstash posted.

What was affected?

Upstash named in us, us-east-1.

What caused it?

Upstash hasn't published a root cause. If it does, it shows here.

Where does this come from?

Upstash's official status page, https://status.upstash.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.