Upstream Request Timeout: What It Means and How to Fix It on Spotify

"Upstream request timeout" means a proxy server sitting between you and a service waited too long for the backend server behind it and gave up. The text is the default response of the Envoy proxy, which returns it with an HTTP 504 status. On Spotify it usually points to a server-side delay or outage, so the fix is often to wait, then check your connection, clear the cache or reinstall the app.

This guide explains what the error means in plain terms, how to tell whether the problem is on your side or the service's side, and the official Spotify fixes for phones, desktop and the web player. A short section for site owners covers why Envoy returns the message.

What does upstream request timeout mean?

Upstream request timeout means the server that received your request (the proxy or gateway) forwarded it to an "upstream" server, and that upstream server did not answer within the allowed time. In networking, upstream is the server further back in the chain: the one that actually holds your playlists, search results or account data.

The exact wording comes from Envoy, an open-source proxy used by many large web services. When a route's timeout is exceeded, Envoy returns status "504 Gateway Timeout" with the body text "upstream request timeout", as shown in the Envoy Gateway timeout documentation. Envoy's default route timeout is 15 seconds unless the operator changes it.

Two things follow from this:

• The error is generated by the service's infrastructure, not by your device or browser.
• Your connection can still contribute: a very slow or unstable link can stretch a request past the timeout, but most of the time the backend itself is slow, overloaded or down.

"Upstream timeout" without the word "request" refers to the same idea: a server further up the chain did not reply in time.

Why Spotify shows the upstream request timeout error

Spotify shows upstream request timeout when one of its own servers does not respond in time to a request your app or browser made. The most common causes are:

• Spotify-side outage or overload: a backend service is slow or failing, often during big releases or incidents. Many users see the error at the same time.
• Weak or unstable connection: poor Wi-Fi or mobile signal makes requests take longer than the server is willing to wait.
• Network restrictions: firewalls, VPNs, proxies or school and office networks that slow down or interfere with Spotify traffic.
• Stale app data: a corrupted cache or an outdated app version can keep repeating a failing request.

A quick way to tell the difference: if other apps and websites load fine and other people report Spotify problems at the same time, the cause is almost certainly on Spotify's side and waiting is the only fix. If only your device fails, work through the steps below.

How to fix upstream request timeout on Spotify

To fix upstream request timeout on Spotify, rule out an outage first, then check your network, and only then reset the app. Follow these steps in order and test playback after each one:

1. Wait a few minutes and reload. Timeouts caused by a busy backend often clear on their own.
2. Check whether Spotify is down for others through Spotify's official social channels or outage reports.
3. Test other apps and websites. If they fail too, the connection is the problem.
4. Turn Wi-Fi off for 30 seconds and back on, restart your router, or switch between Wi-Fi and mobile data. Spotify's offline troubleshooting page lists these steps.
5. Make sure Offline mode is off: on mobile, tap your profile picture, then Settings and privacy, then Data-saving and offline.
6. Disconnect any VPN or proxy and check that your firewall allows Spotify as an exception.
7. Update the Spotify app from the App Store, Google Play, the Microsoft Store or Spotify's website.
8. Clear the Spotify cache (see the next section).
9. Do a clean reinstall if nothing else works.

If you use Windows and suspect name resolution issues, you can also inspect the cached DNS entries on Windows before flushing them.

How to clear the Spotify cache

Clearing the Spotify cache removes the temporary music and podcast data the app stores for smooth playback, which can fix requests that keep failing. Spotify documents the steps on its storage information page.

On iPhone and Android:

1. Tap your profile picture at the top of the screen.
2. Tap Settings and privacy.
3. Open Data-saving and offline.
4. Under Storage, tap Clear next to Clear cache.

On Windows and Mac:

1. Click your profile picture and select Settings.
2. Scroll down to Storage.
3. Click Clear cache.

Downloads for offline listening are stored separately from the cache. On Android you can also go to Settings > Apps > Spotify > Storage and tap Clear cache there.

How to do a clean reinstall of Spotify

A clean reinstall of Spotify removes the app and its leftover data so a fresh copy starts without corrupted files. Spotify's reinstall guide notes that you have to download music and podcasts again afterwards.

• Android: clear storage and cache under Settings > Apps > Spotify > Storage, uninstall, delete the com.spotify.music folder under Internal Storage > Android > data, restart, then install from Google Play.
• iPhone: clear the cache in the app, delete Spotify under Settings > General > iPhone Storage, turn the phone off for a few minutes, then reinstall from the App Store.
• Mac: quit Spotify, delete com.spotify.client and com.spotify.client.helper in Library > Caches and the Spotify folder in Library > Application Support, restart, then reinstall.
• Windows: uninstall through Settings > Apps, then reinstall from the Microsoft Store or Spotify's website.

Fixing the error in the Spotify web player

In the Spotify web player, upstream request timeout is fixed the same way as in the app, plus a few browser checks. Spotify's web player help recommends:

• Updating your browser to a supported version (recent Chrome, Firefox, Edge, Opera or Safari).
• Opening Spotify in a private or incognito window to rule out extensions and stored site data.
• Checking whether a school, workplace or office network blocks Spotify.
• Switching to the desktop app if the web player still fails.

Browser features such as encrypted DNS can change how your connection resolves servers; see how to turn secure DNS on or off in Chrome, Edge and Firefox if you changed it recently.

Upstream request timeout for site owners and developers

For site owners, upstream request timeout means the Envoy route timeout expired before the backend service sent a complete response. The Envoy route documentation sets the default to 15 seconds, measured from the moment the full downstream request has been received, and a value of 0 disables it.

Raise the timeout only for routes that legitimately run long; otherwise fix the slow backend, since a longer timeout just makes users wait longer for the same failure. The Envoy router filter documentation describes the headers in detail.

FAQ

Related: Spotify not working on Alexa, add local files to Spotify, get your Spotify DNA chart