User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Entertainment
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 34 min ago. Last stored result reached it in 202 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Thu 06 | 0 | 0.0 | 195 ms | 0 |
| Thu 08 | 0 | 0.0 | 278 ms | 0 |
| Thu 10 | 0 | 0.0 | 194 ms | 0 |
| Thu 12 | 0 | 0.0 | 235 ms | 0 |
| Thu 14 | 0 | 0.0 | 201 ms | 0 |
| Thu 16 | 0 | 0.0 | 170 ms | 0 |
| Thu 18 | 0 | 0.0 | 518 ms | 0 |
| Thu 20 | 0 | 0.0 | 206 ms | 0 |
| Thu 22 | 0 | 0.0 | 214 ms | 0 |
| Fri 00 | 0 | 0.0 | 168 ms | 0 |
| Fri 02 | 0 | 0.0 | 198 ms | 0 |
| Fri 05 | 0 | 0.0 | 199 ms | 0 |
| Fri 07 | 0 | 0.0 | 270 ms | 0 |
| Fri 09 | 0 | 0.0 | 357 ms | 0 |
| Fri 10 | 0 | 0.0 | 190 ms | 0 |
| Fri 11 | 0 | 0.0 | 242 ms | 0 |
| Fri 13 | 0 | 0.0 | 194 ms | 0 |
| Fri 15 | 0 | 0.0 | 191 ms | 0 |
| Fri 17 | 0 | 0.0 | 203 ms | 0 |
| Fri 19 | 0 | 0.0 | 200 ms | 0 |
| Fri 21 | 0 | 0.0 | 197 ms | 0 |
| Fri 23 | 0 | 0.0 | 238 ms | 0 |
| Sat 01 | 0 | 0.0 | 214 ms | 0 |
| Sat 03 | 0 | 0.0 | 198 ms | 0 |
| Sat 05 | 0 | 0.0 | 194 ms | 0 |
| Sat 07 | 0 | 0.0 | 204 ms | 0 |
| Sat 09 | 0 | 0.0 | 172 ms | 0 |
| Sat 12 | 0 | 0.0 | 201 ms | 0 |
| Sat 14 | 0 | 0.0 | 165 ms | 0 |
| Sat 16 | 0 | 0.0 | 224 ms | 0 |
| Sat 19 | 0 | 0.0 | 198 ms | 0 |
| Sat 21 | 0 | 0.0 | 211 ms | 0 |
| Sat 23 | 0 | 0.0 | 195 ms | 0 |
| Sun 02 | 0 | 0.0 | 189 ms | 0 |
| Sun 04 | 0 | 0.0 | 161 ms | 0 |
| Sun 07 | 0 | 0.0 | 216 ms | 0 |
| Sun 09 | 0 | 0.0 | 205 ms | 0 |
| Sun 10 | 0 | 0.0 | 178 ms | 0 |
| Sun 12 | 0 | 0.0 | 193 ms | 0 |
| Sun 14 | 0 | 0.0 | 163 ms | 0 |
| Sun 17 | 0 | 0.0 | 208 ms | 0 |
| Sun 18 | 0 | 0.0 | 201 ms | 0 |
| Sun 19 | 0 | 0.0 | 181 ms | 0 |
| Sun 20 | 0 | 0.0 | 214 ms | 0 |
| Sun 21 | 0 | 0.0 | 175 ms | 0 |
| Sun 22 | 0 | 0.0 | 226 ms | 0 |
| Sun 23 | 0 | 0.0 | 215 ms | 0 |
| Mon 01 | 0 | 0.0 | 200 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 11 days of data so far, so the 90-day numbers fill in over time.
No outages on record for stats.fm for Spotify yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when stats.fm for Spotify goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
We track stats.fm for Spotify (stats.fm) as part of the Entertainment group. Your music, your stats, your story. Enter a new dimension of music by getting unique insights into your music taste.
stats.fm for Spotify publishes an official status page at status.stats.fm; when we can read it, its incident level is folded into the status shown here.
Common problems for entertainment services: streams buffering or not starting, playback errors, and app sign-in problems.
Measured uptime from our checks: 100% over 11 days of checks. No public incidents logged since monitoring began 11 days ago.
Response time over the last 24 hours: 196 ms average, 152–226 ms range across 19 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public stats.fm for Spotify incident since monitoring began 11 days ago.
From our own checks: 100% over 11 days of checks.
196 ms on average over the last 24 hours (152–226 ms).
Yes, at https://status.stats.fm.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For entertainment services, watch for streams buffering or not starting, playback errors, and app sign-in problems. If many people report stats.fm for Spotify here at once, the problem is on stats.fm for Spotify's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with stats.fm for Spotify. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.