// troubleshooting guide · upstash

Upstash Redis Slow or Timing Out

Status
Ongoing
platforms:
Fly.io, Vercel, AWS
updated:
November 15, 2026
reports:
5
Method
how we research
Share

RUNBOOK · upstash/high-latency-timeouts5 FIXES

// quick answer

Most slow Upstash calls come from distance (app and database in different regions), REST/HTTP overhead on every call, or a regional incident. Put the database in the same region as your compute, batch commands, and check status.upstash.com.

Most likely fix: Co-locate the database

How to fix it

// try these in order, the most common fix is first

  1. FIX 1Co-locate the database

    1. 01Check the database region in the Console
    2. 02Create a new database in your compute region (Vercel function region, Fly primary region) and migrate
    3. 03For global apps, add read regions close to users (note: writes bill per region)
    Did this fix it?
  2. FIX 2Cut round trips

    1. 01Use redis.pipeline() or auto-pipelining in @upstash/redis
    2. 02Replace many GETs with MGET
    3. 03Use Lua scripts for multi-step logic
    Did this fix it?
  3. FIX 3Measure

    1. 01From the app host run redis-cli --tls -u $REDIS_URL --latency-history
    2. 02Compare against a second database to rule out a bad instance
    Did this fix it?
  4. FIX 4Check for incidents and throttling

    1. 01Open status.upstash.com for your region
    2. 02Look at the Console's throughput chart for hits on the commands/sec cap; move to a larger fixed plan if so
    Did this fix it?
  5. FIX 5Avoid blocking commands

    1. 01Replace KEYS with SCAN
    2. 02Avoid huge HGETALL/SMEMBERS on big keys
    Did this fix it?

Symptoms

Commands that should take a few ms take 100-500ms+, 'could not send HTTP request to instance: connection error: timed out' on Fly.io, rate limiter returns success with reason 'timeout', intermittent 504s.

Why it happens

  • C-01Database region far from the app's region
  • C-02One HTTP round trip per command instead of pipelines
  • C-03Throttling after hitting the commands-per-second limit (10K or 16K/sec)
  • C-04Regional incidents (us-east-1, eu-west-1, Fly iad have had latency incidents)
  • C-05Blocking commands like KEYS on large datasets

// this guide also covers

  • upstash redis slow
  • upstash high latency
  • upstash redis timeout
  • upstash redis timed out fly.io

Still not working?

If Upstash keeps failing, you're not alone. See every Upstash problem users report or the alternatives people switch to.

Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.

Talk to us

Watch Upstash Get an email when its price changes, it has an outage, or we publish a new fix. No spam.

Fixed it? Share this guide

The same problem in other apps

All not loading, error messages & connection guides →

Other Upstash errors

All 11 Upstash errors and fixes →