A desktop setup displays a dark-themed media and device management interface across a monitor, phone, and laptop.
If Spotify won't open, won't play, or stalls in a browser on September 24, 2026, first check whether the fault is on Spotify's end. Spotify's official status page listed all systems operational that day, while user-report trackers picked up complaints in the US. Only after that check does the usual sequence help: restart, check the network, clear the cache, update, fix the browser, and reinstall last. Most generic "7 quick fixes" guides skip the order and the trade-offs. On a Windows PC, the order decides whether you spend two minutes on the problem or wipe your offline downloads for nothing.

Spotify outage reports and an all-clear status page on September 24​

The widely shared troubleshooting guide from WindowsReport said Spotify was having a "huge outage right now." The evidence for that is mixed. When checked on September 24, Spotify's own status page showed "All Systems Operational" and no incidents reported for that day or the previous two weeks. Independent automated monitoring agrees: UptimeRobot says its latest automated check was run September 24, 2026, 08:50 GMT+0 from North America and didn't detect any unusual response times or error codes.

User reports point the other way. According to The Sunday Guardian, users in the US reported problems across the app, audio streaming and the website, including repeated pauses and playlists that wouldn't load. The same report, citing Downdetector data, says 45% of reported problems involve the Spotify app, while 23% concern audio streaming and 18% relate to the website. No other outlet has confirmed a large outage that day, and Spotify has not acknowledged one.

Both can be true. A synthetic check that loads a website from a data center can miss problems with login, playback or particular regions. UptimeRobot notes that an outage doesn't always mean every user is affected; some are regional, some affect only certain features, and some appear as slow loading instead of a full failure. Past outages show how this plays out. During the April 16, 2025 incident, more than 48,000 users had reported issues accessing Spotify by 9:45 a.m. ET, according to Downdetector, and Spotify later confirmed the outage.

For troubleshooting, the order of checks matters more than any single tracker. Spotify's support documentation says to check the @SpotifyStatus account on X and the "Ongoing Issues" board in the Spotify Community before working on your own device. Downdetector spikes and Reddit threads add useful signal, but a handful of user reports doesn't prove a service-wide failure. StatusGator, for example, logs a steady background of complaints: it recorded 6 user-submitted reports of outages in the past 24 hours on a day it rated Spotify operational. If there is a real outage, nothing on your PC will fix it and you'll have to wait. If there isn't, and friends on other networks can stream, the problem is local and the rest of this guide applies.

Force-quit Spotify in Task Manager before you try anything else​

Spotify's own quick-fix list for playback problems, including the "Page not available" and "Something went wrong" errors, starts with three steps: restart the app, update it, reinstall it. Restarting only helps if the app actually closes. On Windows, clicking the X can leave Spotify running in the background, so a true restart means ending any Spotify entries in Task Manager (Ctrl+Shift+Esc) and then launching it again. In the web player, the equivalent is refreshing the tab or closing and reopening the browser.

After relaunching, try a different playlist or track. If only one album fails and everything else plays, the service and your connection are fine. Spotify's support pages note that grayed-out songs can simply be unavailable in your market, and that users travelling abroad may need to change account settings before playback works.

The best way to narrow things down is to try another client, which Spotify's documentation recommends. If the problem doesn't appear on another device or in the web player, the fault is probably specific to the device you started on. Spotify's checklist for that case:

  • The device should be supported and running up-to-date software.
  • The device should have at least 250MB of available memory for playback.
  • On desktop only, a firewall should not be blocking Spotify.
  • Mobile devices should have enough battery charge.
  • On Android only, a faulty SD card can cause problems, and removing it is a valid test.

Spotify's support page also suggests closing other apps you aren't using, which helps on memory-constrained laptops and phones.

Offline Mode, firewalls and office networks can break Spotify on a healthy connection​

A lot of "Spotify isn't working" reports are really Spotify thinking it's offline. Offline Mode is a Spotify setting that limits the app to downloaded content, so anything you haven't downloaded appears grayed out and won't play. Before blaming your router, check that Offline Mode is off:

  1. On Windows desktop, open Spotify, click the three-dot menu at the top, open File, and switch off Offline Mode if it's on.
  2. On Mac, click Spotify in the Apple menu at the top of the screen and switch off Offline Mode.
  3. On a phone or tablet, tap your profile picture, then Settings and privacy, then Data-saving and offline, and switch Offline Mode off.

Offline Mode also affects sign-in. Spotify notes that while the app is in Offline Mode you can't log in with Facebook or Apple, so an email address and password are the fallback.

If Offline Mode is off, check whether other apps and websites load. If they don't, the problem is your connection. Spotify's documented steps are to turn Wi-Fi off, wait 30 seconds and turn it back on, restart your home router, try a different Wi-Fi network or mobile data, and on cellular, confirm you have data allowance left. If Spotify works on another connection, Spotify suggests contacting the provider of the connection that failed.

Sysadmins will recognise the next point. Spotify's documentation says shared or public networks, such as schools and offices, sometimes restrict access to certain services, and it tells users to contact their IT department. If Spotify fails on a corporate network but works on a phone hotspot, the cause is most likely a policy decision, not a Spotify bug. On a personal Windows PC, Spotify also advises checking whether your firewall lists Spotify as an exception.

The WindowsReport guide also suggests turning off any VPN. Spotify's official pages don't list this as a fix, but it's a reasonable isolation test: if Spotify works with the VPN off, the VPN route is involved. That guide also names DNS problems as a cause without giving a procedure. UptimeRobot mentions clearing the DNS cache as one of several general checks, but no Spotify documentation connects DNS to these failures, so changing DNS servers shouldn't be one of your first steps.

Clear the Spotify cache without losing offline downloads​

Cache clearing is where lazy guides go wrong, so it helps to know what the cache is. Spotify's storage documentation describes two separate uses of device storage. The cache holds pieces of music and podcasts so playback doesn't lag. Downloads hold music and podcasts you saved for offline listening. Clearing the cache removes the first and leaves the second alone. Your playlists and Premium subscription are account data, not local files, so they aren't affected.

The current paths, per Spotify:

Windows and other desktop versions​

  1. Click your profile picture at the top and select Settings.
  2. Scroll down to Storage.
  3. Click Clear cache, then restart Spotify.

The same Storage section has a Change location option for moving the cache to another drive. That's useful on a PC whose system SSD is nearly full.

Android and iPhone​

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

Android also has a system-level route through Settings > Apps > Spotify > Storage > Clear Cache, which the WindowsReport guide describes. Spotify's own documentation now points to the in-app path above, which works the same way on both mobile platforms.

Free space matters too. Spotify recommends at least 1GB of free storage for the app, a stricter figure than the 250MB of free memory in its playback checklist. If the drive or phone is nearly full, clearing the cache is a temporary fix. When storage runs short, Spotify's guidance is to remove downloaded tracks by hand. On iPhone, iOS can automatically clear unused stored data to make room for new downloads. The WindowsReport guide calls corrupted cache one of the biggest causes of Spotify failures, but it offers no data to back that up. Clearing the cache is a cheap, low-risk test, not a proven fix.

Spotify web player failures usually come down to the browser, DRM and Windows 10 N editions​

When the desktop app works and the web player doesn't, the browser is the likely cause. Spotify's web player supports current desktop versions of Chrome, Firefox, Edge, Opera and Safari, and its support policy covers browser versions released within the previous 30 months. An older, locked-down browser on a managed machine may simply fall outside that window.

Spotify's first two steps for the web player are to update the browser and try a private or incognito window. A private window loads without your usual cookies and, in most browser configurations, without extensions. If Spotify works there, something in your normal profile is interfering. The WindowsReport guide suggests clearing cookies and cache, temporarily disabling ad blockers, turning off VPN extensions, and trying a different browser such as Edge, Chrome or Firefox. Spotify's web player guide doesn't list those specifically, but they are sensible ways to find which part of the profile is the problem.

The most specific web player failure is the message "Playback of protected content is not enabled" or similar wording. The web player relies on DRM (digital rights management) through the browser's Widevine component, and if the browser blocks protected content, playback won't start. Spotify's documented fixes:

  1. In Chrome, go to chrome://settings/content, open the entry for Spotify's web player, and set Protected content IDs to Allow or Default.
  2. In Firefox, click Enable DRM in the warning bar. If the bar doesn't appear, go to about:preferences#content and turn on Play DRM under DRM content.

Windows has an extra wrinkle. Spotify says N editions of Windows 10, which ship without some built-in media components, need Microsoft's Media Feature Pack installed before the web player will work. The requirement applies to those specific Windows 10 editions, not to Windows PCs generally. If your web player fails on a Windows 10 N machine even with DRM allowed, check that first.

Update Spotify before you reinstall, because reinstalling deletes your downloads​

Old app versions can break after Spotify changes its back end, and Spotify's troubleshooting advice covers both the app and the operating system. The usual routes are the Google Play Store or Apple App Store on mobile. On Windows, the WindowsReport guide says to update through the Microsoft Store or Spotify's own installer, depending on how you installed it. Relaunch afterwards. Neither Spotify nor any report ties a particular app version or Windows build to the problems reported on September 24, so no specific release is known to fix them.

Reinstalling comes last for a reason. Spotify lists it as a quick fix and says it resolves common technical problems and makes sure you have the current version. It also warns that after reinstalling you must re-download any downloaded music and podcasts. If you have a large offline library, or you're about to travel, that's a real cost. Your account and playlists are stored in the cloud and aren't removed, but gigabytes of downloads are.

Following Spotify's guidance and the WindowsReport steps, the sequence is: uninstall Spotify, restart the computer or phone, install the latest version, sign back in, and test playback. If Spotify still fails on one device after a clean reinstall while working everywhere else, Spotify's documentation says the next step is to contact the device manufacturer.

What this means for you​

Start with a status check and a restart, and only reach for cache clearing or reinstalling once the problem is confirmed to be on your device. Readers affected by September 24 reports should compare Spotify's status channels with the tracker spikes before changing anything. Managed-desktop users should talk to IT before assuming Spotify is broken, and anyone with a big offline library should put off reinstalling as long as possible.

  • Check @SpotifyStatus and the Spotify Community "Ongoing Issues" board first, and treat Downdetector or Reddit reports as signals, not confirmation of an outage.
  • On Windows, make a restart count by ending Spotify in Task Manager, then check that Offline Mode is off under File in the three-dot menu.
  • If Spotify fails on an office or school network but works on a hotspot, the network is probably restricting it, and your IT department is the right contact.
  • Clearing the cache under Settings > Storage leaves downloads, playlists and your subscription in place, while reinstalling means re-downloading all offline music and podcasts.
  • For web player DRM errors, allow Protected content IDs in Chrome or turn on Play DRM in Firefox, and install Microsoft's Media Feature Pack on Windows 10 N editions.
  • Keep at least 1GB free for Spotify, and test a different device or the web player to tell a device fault from an account or service problem.

The practical rule is to rule out the cheap explanations before the expensive ones. As of September 24, Spotify had acknowledged nothing, so users hitting problems had no official outage to point to and had to work through the checklist. If Spotify posts an incident on its status page or @SpotifyStatus, the local fixes above won't help until the service is restored. If it doesn't, a Windows user who works through the order above will find the cause without losing an offline library to a reinstall that wasn't needed.