Skip to content

Outage tracker / Spotify

Is Spotify down?

I'm having a problem

Checks passingchecked 1 minute ago

Our checks of Spotify pass from all 10 regions we check.

As of Nov 5, 2026, 3:28 PM UTC, RealUptime's checks of Spotify passed in all 10 regions that returned a reading.

Front-door and live API checks

Our checks of Spotify did not fail from two or more distant regions in the 89 days we have checked it (since Aug 8, 2026). This does not show Spotify works for users.

Email me when our checks of Spotify fail from two or more distant regions

One email when our checks of Spotify fail from two or more distant regions, and one when they pass, after you confirm the address. No account, no card.

This is our own reading from outside. It is not Spotify's official status.

our check readinglive · checked Nov 5, 2026, 3:28 PM UTC
US-East1209 msChecks passing
US-West1738 msChecks passing
Europe635 msChecks passing
Asia-Pacific2198 msChecks passing
US-Central1129 msChecks passing
Canada621 msChecks passing
UK223 msChecks passing
Southeast Asia1479 msChecks passing
Australia1554 msChecks passing
South America2581 msChecks passing
their status pagetheir claim, not our reading

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

from Spotify's own status page, checked Oct 27, 2026, 3:25 AM UTC
Spotify's own status page shows no incident, and our checks of Spotify pass 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
1.6sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 476ms2026-10-08 UTC: p95 435ms2026-10-09 UTC: p95 465ms2026-10-10 UTC: p95 542ms2026-10-11 UTC: p95 500ms2026-10-12 UTC: p95 378ms2026-10-13 UTC: p95 650ms2026-10-14 UTC: p95 541ms2026-10-15 UTC: p95 737ms2026-10-16 UTC: p95 521ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 824ms2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.7s2026-10-27 UTC: p95 1.2s2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 848ms2026-10-30 UTC: p95 931ms2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 1.7s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 1.6s
Oct 7Oct 21Nov 5
US-West
2.0sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 899ms2026-10-08 UTC: p95 676ms2026-10-09 UTC: p95 865ms2026-10-10 UTC: p95 886ms2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 936ms2026-10-13 UTC: p95 830ms2026-10-14 UTC: p95 900ms2026-10-15 UTC: p95 918ms2026-10-16 UTC: p95 734ms2026-10-17 UTC: p95 694ms2026-10-18 UTC: p95 741ms2026-10-19 UTC: p95 983ms2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.6s2026-10-23 UTC: p95 1.7s2026-10-24 UTC: p95 1.6s2026-10-25 UTC: p95 1.6s2026-10-26 UTC: p95 1.9s2026-10-27 UTC: p95 1.9s2026-10-28 UTC: p95 1.7s2026-10-29 UTC: p95 1.9s2026-10-30 UTC: p95 1.7s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 2.8s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5
Europe
1.0sp95 · 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-10-07 UTC: p95 417ms2026-10-08 UTC: p95 359ms2026-10-09 UTC: p95 356ms2026-10-10 UTC: p95 534ms2026-10-11 UTC: p95 481ms2026-10-12 UTC: p95 340ms2026-10-13 UTC: p95 255ms2026-10-14 UTC: p95 276ms2026-10-15 UTC: p95 442ms2026-10-16 UTC: p95 431ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 1.0s2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.4s2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.0s2026-11-05 UTC: p95 1.0s
Oct 7Oct 21Nov 5
Asia-Pacific
3.3sp95 · latest
10s5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 920ms2026-10-13 UTC: p95 1.0s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 2.2s2026-10-18 UTC: p95 2.5s2026-10-19 UTC: p95 2.4s2026-10-20 UTC: p95 2.5s2026-10-21 UTC: p95 2.4s2026-10-22 UTC: p95 2.2s2026-10-23 UTC: p95 2.4s2026-10-24 UTC: p95 2.5s2026-10-25 UTC: p95 2.6s2026-10-26 UTC: p95 3.0s2026-10-27 UTC: p95 5.6s2026-10-28 UTC: p95 2.3s2026-10-29 UTC: p95 2.4s2026-10-30 UTC: p95 2.5s2026-10-31 UTC: p95 2.6s2026-11-01 UTC: p95 2.7s2026-11-02 UTC: p95 3.1s2026-11-03 UTC: p95 2.5s2026-11-04 UTC: p95 3.3s2026-11-05 UTC: p95 3.3s
Oct 7Oct 21Nov 5
US-Central
1.1sp95 · 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-10-07 UTC: p95 516ms2026-10-08 UTC: p95 633ms2026-10-09 UTC: p95 615ms2026-10-10 UTC: p95 590ms2026-10-11 UTC: p95 701ms2026-10-12 UTC: p95 547ms2026-10-13 UTC: p95 555ms2026-10-14 UTC: p95 663ms2026-10-15 UTC: p95 729ms2026-10-16 UTC: p95 590ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 937ms2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 1.0s2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 1.0s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 940ms2026-10-30 UTC: p95 992ms2026-10-31 UTC: p95 886ms2026-11-01 UTC: p95 863ms2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
Canada
1.2sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 610ms2026-10-08 UTC: p95 510ms2026-10-09 UTC: p95 493ms2026-10-10 UTC: p95 461ms2026-10-11 UTC: p95 481ms2026-10-12 UTC: p95 468ms2026-10-13 UTC: p95 551ms2026-10-14 UTC: p95 571ms2026-10-15 UTC: p95 592ms2026-10-16 UTC: p95 546ms2026-10-17 UTC: p95 896ms2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 1.3s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 1.1s2026-10-31 UTC: p95 1.4s2026-11-01 UTC: p95 1.4s2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
UK
950msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 298ms2026-10-08 UTC: p95 392ms2026-10-09 UTC: p95 398ms2026-10-10 UTC: p95 256ms2026-10-11 UTC: p95 164ms2026-10-12 UTC: p95 220ms2026-10-13 UTC: p95 446ms2026-10-14 UTC: p95 295ms2026-10-15 UTC: p95 389ms2026-10-16 UTC: p95 281ms2026-10-17 UTC: p95 773ms2026-10-18 UTC: p95 878ms2026-10-19 UTC: p95 965ms2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 972ms2026-10-24 UTC: p95 1.0s2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 1.3s2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 1.1s2026-10-31 UTC: p95 742ms2026-11-01 UTC: p95 712ms2026-11-02 UTC: p95 967ms2026-11-03 UTC: p95 658ms2026-11-04 UTC: p95 852ms2026-11-05 UTC: p95 950ms
Oct 7Oct 21Nov 5
Southeast Asia
2.5sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 861ms2026-10-08 UTC: p95 944ms2026-10-09 UTC: p95 856ms2026-10-10 UTC: p95 864ms2026-10-11 UTC: p95 818ms2026-10-12 UTC: p95 669ms2026-10-13 UTC: p95 754ms2026-10-14 UTC: p95 908ms2026-10-15 UTC: p95 939ms2026-10-16 UTC: p95 874ms2026-10-17 UTC: p95 2.3s2026-10-18 UTC: p95 2.2s2026-10-19 UTC: p95 2.5s2026-10-20 UTC: p95 2.4s2026-10-21 UTC: p95 1.9s2026-10-22 UTC: p95 2.6s2026-10-23 UTC: p95 2.0s2026-10-24 UTC: p95 2.1s2026-10-25 UTC: p95 1.9s2026-10-26 UTC: p95 2.1s2026-10-27 UTC: p95 2.0s2026-10-28 UTC: p95 1.9s2026-10-29 UTC: p95 2.1s2026-10-30 UTC: p95 2.1s2026-10-31 UTC: p95 2.1s2026-11-01 UTC: p95 2.7s2026-11-02 UTC: p95 2.2s2026-11-03 UTC: p95 2.2s2026-11-04 UTC: p95 2.7s2026-11-05 UTC: p95 2.5s
Oct 7Oct 21Nov 5
Australia
3.2sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 963ms2026-10-08 UTC: p95 968ms2026-10-09 UTC: p95 850ms2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.7s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 2.0s2026-10-15 UTC: p95 1.8s2026-10-16 UTC: p95 1.7s2026-10-17 UTC: p95 2.7s2026-10-18 UTC: p95 3.2s2026-10-19 UTC: p95 3.5s2026-10-20 UTC: p95 3.4s2026-10-21 UTC: p95 3.6s2026-10-22 UTC: p95 3.1s2026-10-23 UTC: p95 3.3s2026-10-24 UTC: p95 3.2s2026-10-25 UTC: p95 3.4s2026-10-26 UTC: p95 3.3s2026-10-27 UTC: p95 3.1s2026-10-28 UTC: p95 3.1s2026-10-29 UTC: p95 3.3s2026-10-30 UTC: p95 3.7s2026-10-31 UTC: p95 3.5s2026-11-01 UTC: p95 3.0s2026-11-02 UTC: p95 2.7s2026-11-03 UTC: p95 2.7s2026-11-04 UTC: p95 3.3s2026-11-05 UTC: p95 3.2s
Oct 7Oct 21Nov 5
South America
2.8sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.7s2026-10-11 UTC: p95 1.9s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.7s2026-10-14 UTC: p95 1.6s2026-10-15 UTC: p95 1.6s2026-10-16 UTC: p95 1.5s2026-10-17 UTC: p95 2.4s2026-10-18 UTC: p95 2.6s2026-10-19 UTC: p95 2.7s2026-10-20 UTC: p95 3.0s2026-10-21 UTC: p95 2.7s2026-10-22 UTC: p95 2.5s2026-10-23 UTC: p95 9.3s2026-10-24 UTC: p95 2.6s2026-10-25 UTC: p95 2.7s2026-10-26 UTC: p95 2.7s2026-10-27 UTC: p95 2.7s2026-10-28 UTC: p95 2.5s2026-10-29 UTC: p95 3.0s2026-10-30 UTC: p95 2.7s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 1.7s2026-11-02 UTC: p95 2.4s2026-11-03 UTC: p95 2.5s2026-11-04 UTC: p95 3.7s2026-11-05 UTC: p95 2.8s
Oct 7Oct 21Nov 5

Check your own site while you wait on Spotify

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • AuthprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Album artUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • App connectionUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Sign-inUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Web playerUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1209msstatus code: 401checked: Nov 5, 2026, 3:28 PM 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
      Checks passinglatency: 1738msstatus code: 401checked: Nov 5, 2026, 3:27 PM 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
      Checks passinglatency: 1129msstatus code: 401checked: Nov 5, 2026, 3:22 PM 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
      Checks passinglatency: 621msstatus code: 401checked: Nov 5, 2026, 3:14 PM 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
    Checks passinglatency: 2581msstatus code: 401checked: Nov 5, 2026, 3:18 PM 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 635msstatus code: 401checked: Nov 5, 2026, 3:20 PM 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
      Checks passinglatency: 223msstatus code: 401checked: Nov 5, 2026, 3:18 PM 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 2198msstatus code: 401checked: Nov 5, 2026, 3:06 PM 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
      Checks passinglatency: 1479msstatus code: 401checked: Nov 5, 2026, 3:23 PM 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
      Checks passinglatency: 1554msstatus code: 401checked: Nov 5, 2026, 3:25 PM 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 probe events

This is an example incident, 10mdeclared on their status page2024-06-01

check 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 check readings and Spotify's own claim at the time, side by side.

Full check history for Spotify: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Put this badge in your README

Spotify uptime by RealUptime's checksLive, from this page's own readings.
[![Spotify uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Spotify down?", https://realuptime.io/outages/spotify. The readings change with every check, so give the date you read them.

How our checks compare with Spotify's stated SLA

At or above your target

Our checks of Spotify failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, 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://open.spotify.com/
secondary
https://accounts.spotify.com/en/login
secondary
https://apresolve.spotify.com/?type=accesspoint
secondary
https://i.scdn.co/image/ab67616d0000b273e8b066f70c206551210d902b

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.spotify.com

RealUptime is not affiliated with Spotify; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.