Skip to content

Outage tracker / Spotify

Is Spotify down?

I'm having a problem

Operationalchecked 1 minute ago

We reached Spotify from all 10 regions we check.

As of Sep 23, 2026, 9:09 AM UTC, Spotify answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

Last outage: 21h 20m on Sep 21, 2026 (web surface, from South America).

our independent probeslive · checked Sep 23, 2026, 9:09 AM UTC
US-East410 msOperational
US-West585 msOperational
Europe161 msOperational
Asia-Pacific509 msOperational
US-Central624 msOperational
Canada412 msOperational
UK338 msOperational
Southeast Asia868 msOperational
Australia423 msOperational
South America1090 msOperational
their status pagetheir claim, not our reading

Spotify reports: All systems operational (“All Systems Operational”)

from Spotify's own status page, checked Sep 23, 2026, 8:47 AM UTC
Our probes and Spotify's own status page agree: both show Spotify as reachable right now.

Spotify's own component breakdown, as they publish it

  • API (example)Operational
  • Management Portal (example)Operational
  • TestOperational

These are Spotify's components, named and scored by Spotify. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Spotify's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Spotify response time, by region

US-East
604msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 716ms2026-08-26 UTC: p95 759ms2026-08-27 UTC: p95 936ms2026-08-28 UTC: p95 772ms2026-08-29 UTC: p95 524ms2026-08-30 UTC: p95 557ms2026-08-31 UTC: p95 451ms2026-09-01 UTC: p95 548ms2026-09-02 UTC: p95 504ms2026-09-03 UTC: p95 558ms2026-09-04 UTC: p95 535ms2026-09-05 UTC: p95 577ms2026-09-06 UTC: p95 505ms2026-09-07 UTC: p95 357ms2026-09-08 UTC: p95 379ms2026-09-09 UTC: p95 381ms2026-09-10 UTC: p95 528ms2026-09-11 UTC: p95 427ms2026-09-12 UTC: p95 342ms2026-09-13 UTC: p95 332ms2026-09-14 UTC: p95 420ms2026-09-15 UTC: p95 400ms2026-09-16 UTC: p95 504ms2026-09-17 UTC: p95 546ms2026-09-18 UTC: p95 500ms2026-09-19 UTC: p95 431ms2026-09-20 UTC: p95 378ms2026-09-21 UTC: p95 421ms2026-09-22 UTC: p95 454ms2026-09-23 UTC: p95 604ms
Aug 25Sep 8Sep 23
US-West
1.0sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 662ms2026-08-26 UTC: p95 657ms2026-08-27 UTC: p95 667ms2026-08-28 UTC: p95 642ms2026-08-29 UTC: p95 543ms2026-08-30 UTC: p95 725ms2026-08-31 UTC: p95 636ms2026-09-01 UTC: p95 452ms2026-09-02 UTC: p95 519ms2026-09-03 UTC: p95 503ms2026-09-04 UTC: p95 454ms2026-09-05 UTC: p95 588ms2026-09-06 UTC: p95 485ms2026-09-07 UTC: p95 358ms2026-09-08 UTC: p95 445ms2026-09-09 UTC: p95 380ms2026-09-10 UTC: p95 345ms2026-09-11 UTC: p95 325ms2026-09-12 UTC: p95 446ms2026-09-13 UTC: p95 304ms2026-09-14 UTC: p95 467ms2026-09-15 UTC: p95 621ms2026-09-16 UTC: p95 748ms2026-09-17 UTC: p95 707ms2026-09-18 UTC: p95 796ms2026-09-19 UTC: p95 793ms2026-09-20 UTC: p95 786ms2026-09-21 UTC: p95 966ms2026-09-22 UTC: p95 939ms2026-09-23 UTC: p95 1.0s
Aug 25Sep 8Sep 23
Europe
928msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 268ms2026-08-26 UTC: p95 271ms2026-08-27 UTC: p95 412ms2026-08-28 UTC: p95 484ms2026-08-29 UTC: p95 361ms2026-08-30 UTC: p95 292ms2026-08-31 UTC: p95 563ms2026-09-01 UTC: p95 294ms2026-09-02 UTC: p95 423ms2026-09-03 UTC: p95 372ms2026-09-04 UTC: p95 378ms2026-09-05 UTC: p95 548ms2026-09-06 UTC: p95 618ms2026-09-07 UTC: p95 666ms2026-09-08 UTC: p95 675ms2026-09-09 UTC: p95 549ms2026-09-10 UTC: p95 222ms2026-09-11 UTC: p95 478ms2026-09-12 UTC: p95 604ms2026-09-13 UTC: p95 576ms2026-09-14 UTC: p95 430ms2026-09-15 UTC: p95 839ms2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 983ms2026-09-19 UTC: p95 895ms2026-09-20 UTC: p95 773ms2026-09-21 UTC: p95 1.0s2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 928ms
Aug 25Sep 8Sep 23
Asia-Pacific
959msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 719ms2026-08-26 UTC: p95 622ms2026-08-27 UTC: p95 737ms2026-08-28 UTC: p95 953ms2026-08-29 UTC: p95 653ms2026-08-30 UTC: p95 638ms2026-08-31 UTC: p95 705ms2026-09-01 UTC: p95 797ms2026-09-02 UTC: p95 1.0s2026-09-03 UTC: p95 1.3s2026-09-04 UTC: p95 1.1s2026-09-05 UTC: p95 1.1s2026-09-06 UTC: p95 1.1s2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 1.2s2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.2s2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 1.0s2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 415ms2026-09-19 UTC: p95 642ms2026-09-20 UTC: p95 665ms2026-09-21 UTC: p95 553ms2026-09-22 UTC: p95 950ms2026-09-23 UTC: p95 959ms
Aug 25Sep 8Sep 23
US-Central
659msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 808ms2026-09-04 UTC: p95 1.1s2026-09-05 UTC: p95 867ms2026-09-06 UTC: p95 633ms2026-09-07 UTC: p95 662ms2026-09-08 UTC: p95 794ms2026-09-09 UTC: p95 718ms2026-09-10 UTC: p95 600ms2026-09-11 UTC: p95 600ms2026-09-12 UTC: p95 446ms2026-09-13 UTC: p95 637ms2026-09-14 UTC: p95 704ms2026-09-15 UTC: p95 623ms2026-09-16 UTC: p95 538ms2026-09-17 UTC: p95 604ms2026-09-18 UTC: p95 626ms2026-09-19 UTC: p95 579ms2026-09-20 UTC: p95 538ms2026-09-21 UTC: p95 512ms2026-09-22 UTC: p95 545ms2026-09-23 UTC: p95 659ms
Aug 25Sep 8Sep 23
Canada
649msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 466ms2026-09-04 UTC: p95 541ms2026-09-05 UTC: p95 682ms2026-09-06 UTC: p95 764ms2026-09-07 UTC: p95 788ms2026-09-08 UTC: p95 756ms2026-09-09 UTC: p95 737ms2026-09-10 UTC: p95 770ms2026-09-11 UTC: p95 691ms2026-09-12 UTC: p95 728ms2026-09-13 UTC: p95 818ms2026-09-14 UTC: p95 740ms2026-09-15 UTC: p95 584ms2026-09-16 UTC: p95 745ms2026-09-17 UTC: p95 598ms2026-09-18 UTC: p95 528ms2026-09-19 UTC: p95 543ms2026-09-20 UTC: p95 536ms2026-09-21 UTC: p95 491ms2026-09-22 UTC: p95 560ms2026-09-23 UTC: p95 649ms
Aug 25Sep 8Sep 23
UK
614msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 320ms2026-09-04 UTC: p95 305ms2026-09-05 UTC: p95 282ms2026-09-06 UTC: p95 307ms2026-09-07 UTC: p95 303ms2026-09-08 UTC: p95 347ms2026-09-09 UTC: p95 416ms2026-09-10 UTC: p95 572ms2026-09-11 UTC: p95 483ms2026-09-12 UTC: p95 212ms2026-09-13 UTC: p95 367ms2026-09-14 UTC: p95 504ms2026-09-15 UTC: p95 528ms2026-09-16 UTC: p95 405ms2026-09-17 UTC: p95 437ms2026-09-18 UTC: p95 418ms2026-09-19 UTC: p95 392ms2026-09-20 UTC: p95 418ms2026-09-21 UTC: p95 505ms2026-09-22 UTC: p95 523ms2026-09-23 UTC: p95 614ms
Aug 25Sep 8Sep 23
Southeast Asia
1.2sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 841ms2026-09-04 UTC: p95 801ms2026-09-05 UTC: p95 812ms2026-09-06 UTC: p95 699ms2026-09-07 UTC: p95 704ms2026-09-08 UTC: p95 690ms2026-09-09 UTC: p95 738ms2026-09-10 UTC: p95 670ms2026-09-11 UTC: p95 736ms2026-09-12 UTC: p95 765ms2026-09-13 UTC: p95 739ms2026-09-14 UTC: p95 724ms2026-09-15 UTC: p95 782ms2026-09-16 UTC: p95 661ms2026-09-17 UTC: p95 750ms2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 723ms2026-09-20 UTC: p95 826ms2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.2s
Aug 25Sep 8Sep 23
Australia
837msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.2s2026-09-04 UTC: p95 1.1s2026-09-05 UTC: p95 1.2s2026-09-06 UTC: p95 1.1s2026-09-07 UTC: p95 1.3s2026-09-08 UTC: p95 1.7s2026-09-09 UTC: p95 1.4s2026-09-10 UTC: p95 799ms2026-09-11 UTC: p95 1.6s2026-09-12 UTC: p95 1.8s2026-09-13 UTC: p95 1.7s2026-09-14 UTC: p95 1.8s2026-09-15 UTC: p95 1.8s2026-09-16 UTC: p95 1.7s2026-09-17 UTC: p95 1.7s2026-09-18 UTC: p95 1.5s2026-09-19 UTC: p95 1.6s2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.0s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 837ms
Aug 25Sep 8Sep 23
South America
1.4sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.4s2026-09-04 UTC: p95 1.1s2026-09-05 UTC: p95 1.3s2026-09-06 UTC: p95 1.3s2026-09-07 UTC: p95 905ms2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.2s2026-09-11 UTC: p95 1.3s2026-09-12 UTC: p95 1.3s2026-09-13 UTC: p95 1.4s2026-09-14 UTC: p95 1.7s2026-09-15 UTC: p95 1.8s2026-09-16 UTC: p95 1.6s2026-09-17 UTC: p95 1.8s2026-09-18 UTC: p95 1.6s2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 1.6s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 1.6s2026-09-23 UTC: p95 1.4s
Aug 25Sep 8Sep 23

Is it Spotify, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Spotify -- it cannot diagnose Spotify's own systems.

What we measured, function by function

Spotify answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the auth row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • AuthprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 410msstatus code: 401checked: Sep 23, 2026, 9:00 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Spotify normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 585msstatus code: 401checked: Sep 23, 2026, 9:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Spotify normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 624msstatus code: 401checked: Sep 23, 2026, 8:50 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Spotify normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 412msstatus code: 401checked: Sep 23, 2026, 9:09 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Spotify normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 1090msstatus code: 401checked: Sep 23, 2026, 9:07 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Spotify normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 161msstatus code: 401checked: Sep 23, 2026, 9:08 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Spotify normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 338msstatus code: 401checked: Sep 23, 2026, 9:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Spotify normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 509msstatus code: 401checked: Sep 23, 2026, 9:07 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Spotify normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 868msstatus code: 401checked: Sep 23, 2026, 9:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Spotify normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 423msstatus code: 401checked: Sep 23, 2026, 8:57 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Spotify normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Spotify, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We started counting reports for Spotify on September 15, 2026.

Recent outages

Partial outage, 21h 20mmeasured by our probes · South America2026-09-21
Outage, 4h 3mmeasured by our probes · South America and Australia2026-09-13
Partial outage, 4hmeasured by our probes · South America2026-09-12
Partial outage, 40mmeasured by our probes · Australia2026-09-10
Partial outage, 40mmeasured by our probes · South America2026-09-10
Outage, 2h 24mmeasured by our probes · South America and Australia2026-09-08
Partial outage, 20mmeasured by our probes · South America2026-09-08
Partial outage, 21mmeasured by our probes · South America2026-09-08

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Spotify since August 8, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Spotify covering any window you pick, with our measurements and Spotify's own claim at the time, side by side.

Full availability history for Spotify: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Spotify, and again when they can reach it again. That is our own measurement from ten regions, not Spotify's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Spotify uptime measured by RealUptimeLive, from this page's own readings.
[![Spotify uptime measured by RealUptime](https://realuptime.io/outages/spotify/badge.svg?days=30)](https://realuptime.io/outages/spotify)
<a href="https://realuptime.io/outages/spotify"><img src="https://realuptime.io/outages/spotify/badge.svg?days=30" alt="Spotify uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Spotify's SLA implies, from our measurement

Below your target

We measured 6h 26m of downtime for Spotify over the last 30 days, which is 99.1059% uptime by our reading. A 99.9% target allows 43 minutes over that period.

That is 5h 43m more than the target allows. The figure above is the pro-rata share of one month's fee for the time we could not reach it. Your contract probably uses a tiered credit schedule instead, and we have not read it, so treat this as one common way to reason about a credit rather than the amount they owe.

Separately, we measured 40h 22m where only one of our regions was affected. It is excluded above because most SLAs would not credit it, and it is the kind of outage a single-vantage monitor never sees at all.

This is computed from our own probe measurements, not from Spotify's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: auth surface
https://api.spotify.com/v1/search
secondary
https://spotify.statuspage.io/
RealUptime is not affiliated with Spotify; the name identifies what we measured, and nothing here speaks for Spotify's own team. We send a single web request to Spotify from 10 regions on our own schedule and time the response. We do not see inside Spotify's systems, do not use an account or real transaction, and are not the same signal Spotify's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Spotify is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.