Skip to content

Outage tracker / SoundCloud

Is SoundCloud down?

I'm having a problem

Checks passingchecked 9 minutes ago

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

As of Nov 5, 2026, 2:36 PM UTC, RealUptime's checks of SoundCloud passed in all 10 regions that returned a reading.

Front-door and live API checks

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

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

One email when our checks of SoundCloud 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 SoundCloud's official status.

our check readinglive · checked Nov 5, 2026, 2:36 PM UTC
US-East757 msChecks passing
US-West907 msChecks passing
Europe406 msChecks passing
Asia-Pacific1949 msChecks passing
US-Central790 msChecks passing
Canada1149 msChecks passing
UK96 msChecks passing
Southeast Asia1387 msChecks passing
Australia1065 msChecks passing
South America1022 msChecks passing
their status pagetheir claim, not our reading

SoundCloud publishes no status feed we can read, so the only reading here is our check reading on the left.

SoundCloud response time, by region

US-East
1.6sp95 · latest
2.5s1.3s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 716ms2026-10-08 UTC: p95 653ms2026-10-09 UTC: p95 638ms2026-10-10 UTC: p95 665ms2026-10-11 UTC: p95 639ms2026-10-12 UTC: p95 608ms2026-10-13 UTC: p95 599ms2026-10-14 UTC: p95 686ms2026-10-15 UTC: p95 728ms2026-10-16 UTC: p95 776ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 1.3s2026-10-26 UTC: p95 2.0s2026-10-27 UTC: p95 1.2s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.4s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.6s
Oct 7Oct 21Nov 5
US-West
1.4sp95 · latest
2.5s1.3s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 545ms2026-10-08 UTC: p95 453ms2026-10-09 UTC: p95 553ms2026-10-10 UTC: p95 790ms2026-10-11 UTC: p95 838ms2026-10-12 UTC: p95 692ms2026-10-13 UTC: p95 591ms2026-10-14 UTC: p95 693ms2026-10-15 UTC: p95 824ms2026-10-16 UTC: p95 761ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.6s2026-10-23 UTC: p95 1.6s2026-10-24 UTC: p95 1.6s2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 1.8s2026-10-27 UTC: p95 1.9s2026-10-28 UTC: p95 1.7s2026-10-29 UTC: p95 1.6s2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 1.7s2026-11-01 UTC: p95 1.7s2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 2.0s2026-11-04 UTC: p95 2.1s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
Europe
925msp95 · 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 426ms2026-10-08 UTC: p95 297ms2026-10-09 UTC: p95 277ms2026-10-10 UTC: p95 345ms2026-10-11 UTC: p95 279ms2026-10-12 UTC: p95 315ms2026-10-13 UTC: p95 207ms2026-10-14 UTC: p95 180ms2026-10-15 UTC: p95 204ms2026-10-16 UTC: p95 153ms2026-10-17 UTC: p95 476ms2026-10-18 UTC: p95 579ms2026-10-19 UTC: p95 943ms2026-10-20 UTC: p95 728ms2026-10-21 UTC: p95 686ms2026-10-22 UTC: p95 682ms2026-10-23 UTC: p95 698ms2026-10-24 UTC: p95 571ms2026-10-25 UTC: p95 613ms2026-10-26 UTC: p95 659ms2026-10-27 UTC: p95 748ms2026-10-28 UTC: p95 819ms2026-10-29 UTC: p95 646ms2026-10-30 UTC: p95 642ms2026-10-31 UTC: p95 464ms2026-11-01 UTC: p95 503ms2026-11-02 UTC: p95 1.2s2026-11-03 UTC: p95 794ms2026-11-04 UTC: p95 795ms2026-11-05 UTC: p95 925ms
Oct 7Oct 21Nov 5
Asia-Pacific
2.7sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 790ms2026-10-09 UTC: p95 890ms2026-10-10 UTC: p95 902ms2026-10-11 UTC: p95 975ms2026-10-12 UTC: p95 836ms2026-10-13 UTC: p95 1s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.0s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 2.3s2026-10-18 UTC: p95 2.6s2026-10-19 UTC: p95 2.4s2026-10-20 UTC: p95 2.4s2026-10-21 UTC: p95 2.5s2026-10-22 UTC: p95 2.5s2026-10-23 UTC: p95 2.6s2026-10-24 UTC: p95 2.6s2026-10-25 UTC: p95 2.8s2026-10-26 UTC: p95 2.7s2026-10-27 UTC: p95 3.5s2026-10-28 UTC: p95 2.3s2026-10-29 UTC: p95 2.8s2026-10-30 UTC: p95 2.6s2026-10-31 UTC: p95 2.4s2026-11-01 UTC: p95 2.4s2026-11-02 UTC: p95 2.5s2026-11-03 UTC: p95 2.7s2026-11-04 UTC: p95 2.8s2026-11-05 UTC: p95 2.7s
Oct 7Oct 21Nov 5
US-Central
1.2sp95 · 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 546ms2026-10-08 UTC: p95 643ms2026-10-09 UTC: p95 665ms2026-10-10 UTC: p95 510ms2026-10-11 UTC: p95 566ms2026-10-12 UTC: p95 551ms2026-10-13 UTC: p95 500ms2026-10-14 UTC: p95 575ms2026-10-15 UTC: p95 462ms2026-10-16 UTC: p95 818ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 965ms2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.4s2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 1.3s2026-10-26 UTC: p95 1.7s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.5s2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.4s2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
Canada
1.2sp95 · latest
10s5s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 743ms2026-10-08 UTC: p95 658ms2026-10-09 UTC: p95 525ms2026-10-10 UTC: p95 626ms2026-10-11 UTC: p95 385ms2026-10-12 UTC: p95 788ms2026-10-13 UTC: p95 852ms2026-10-14 UTC: p95 861ms2026-10-15 UTC: p95 821ms2026-10-16 UTC: p95 914ms2026-10-17 UTC: p95 888ms2026-10-18 UTC: p95 900ms2026-10-19 UTC: p95 937ms2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 989ms2026-10-24 UTC: p95 984ms2026-10-25 UTC: p95 6.9s2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 1.8s2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 932ms2026-11-04 UTC: p95 471ms2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
UK
660msp95 · 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 474ms2026-10-08 UTC: p95 299ms2026-10-09 UTC: p95 313ms2026-10-10 UTC: p95 366ms2026-10-11 UTC: p95 342ms2026-10-12 UTC: p95 476ms2026-10-13 UTC: p95 224ms2026-10-14 UTC: p95 185ms2026-10-15 UTC: p95 185ms2026-10-16 UTC: p95 205ms2026-10-17 UTC: p95 235ms2026-10-18 UTC: p95 635ms2026-10-19 UTC: p95 743ms2026-10-20 UTC: p95 230ms2026-10-21 UTC: p95 183ms2026-10-22 UTC: p95 205ms2026-10-23 UTC: p95 309ms2026-10-24 UTC: p95 231ms2026-10-25 UTC: p95 244ms2026-10-26 UTC: p95 191ms2026-10-27 UTC: p95 710ms2026-10-28 UTC: p95 735ms2026-10-29 UTC: p95 562ms2026-10-30 UTC: p95 796ms2026-10-31 UTC: p95 837ms2026-11-01 UTC: p95 587ms2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 706ms2026-11-04 UTC: p95 814ms2026-11-05 UTC: p95 660ms
Oct 7Oct 21Nov 5
Southeast Asia
2.1sp95 · 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 1.1s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 670ms2026-10-19 UTC: p95 677ms2026-10-20 UTC: p95 775ms2026-10-21 UTC: p95 745ms2026-10-22 UTC: p95 734ms2026-10-23 UTC: p95 666ms2026-10-24 UTC: p95 611ms2026-10-25 UTC: p95 758ms2026-10-26 UTC: p95 700ms2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 864ms2026-10-29 UTC: p95 2.5s2026-10-30 UTC: p95 2.7s2026-10-31 UTC: p95 2.9s2026-11-01 UTC: p95 3.0s2026-11-02 UTC: p95 2.7s2026-11-03 UTC: p95 2.3s2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5
Australia
1.8sp95 · 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 776ms2026-10-08 UTC: p95 619ms2026-10-09 UTC: p95 665ms2026-10-10 UTC: p95 770ms2026-10-11 UTC: p95 791ms2026-10-12 UTC: p95 822ms2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 634ms2026-10-15 UTC: p95 935ms2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 2.3s2026-10-18 UTC: p95 2.2s2026-10-19 UTC: p95 2.4s2026-10-20 UTC: p95 2.4s2026-10-21 UTC: p95 2.0s2026-10-22 UTC: p95 1.9s2026-10-23 UTC: p95 2.0s2026-10-24 UTC: p95 2.2s2026-10-25 UTC: p95 1.7s2026-10-26 UTC: p95 1.6s2026-10-27 UTC: p95 1.5s2026-10-28 UTC: p95 2.0s2026-10-29 UTC: p95 2.0s2026-10-30 UTC: p95 2.3s2026-10-31 UTC: p95 1.8s2026-11-01 UTC: p95 2.4s2026-11-02 UTC: p95 2.5s2026-11-03 UTC: p95 3.0s2026-11-04 UTC: p95 2.1s2026-11-05 UTC: p95 1.8s
Oct 7Oct 21Nov 5
South America
2.3sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 976ms2026-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 766ms2026-10-11 UTC: p95 863ms2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 825ms2026-10-14 UTC: p95 771ms2026-10-15 UTC: p95 970ms2026-10-16 UTC: p95 763ms2026-10-17 UTC: p95 893ms2026-10-18 UTC: p95 800ms2026-10-19 UTC: p95 810ms2026-10-20 UTC: p95 829ms2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 616ms2026-10-23 UTC: p95 4.2s2026-10-24 UTC: p95 778ms2026-10-25 UTC: p95 877ms2026-10-26 UTC: p95 1.0s2026-10-27 UTC: p95 1.0s2026-10-28 UTC: p95 1.5s2026-10-29 UTC: p95 976ms2026-10-30 UTC: p95 973ms2026-10-31 UTC: p95 953ms2026-11-01 UTC: p95 2.3s2026-11-02 UTC: p95 2.2s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 814ms2026-11-05 UTC: p95 2.3s
Oct 7Oct 21Nov 5

Check your own site while you wait on SoundCloud

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 SoundCloud. It cannot diagnose SoundCloud's own systems.

What we measured, function by function

SoundCloud 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 api 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
  • APIprimaryUS-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: 757msstatus code: 401checked: Nov 5, 2026, 2:28 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach SoundCloud normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 907msstatus code: 401checked: Nov 5, 2026, 2:26 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach SoundCloud normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 790msstatus code: 401checked: Nov 5, 2026, 2:11 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach SoundCloud normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 1149msstatus code: 401checked: Nov 5, 2026, 2:13 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach SoundCloud normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1022msstatus code: 401checked: Nov 5, 2026, 2:36 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach SoundCloud 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: 406msstatus code: 401checked: Nov 5, 2026, 2:08 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach SoundCloud normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 96msstatus code: 401checked: Nov 5, 2026, 2:36 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach SoundCloud 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: 1949msstatus code: 401checked: Nov 5, 2026, 1:59 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach SoundCloud normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1387msstatus code: 401checked: Nov 5, 2026, 2:02 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach SoundCloud normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 1065msstatus code: 401checked: Nov 5, 2026, 1:53 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach SoundCloud 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 SoundCloud, 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 have not received any reports for SoundCloud yet, which is not evidence that nothing is wrong.

Recent probe events

No probe events on record yet for SoundCloud.

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

We have been measuring SoundCloud since August 20, 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 SoundCloud covering any window you pick, with our check readings and SoundCloud's own claim at the time, side by side.

Full check history for SoundCloud: 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

SoundCloud uptime by RealUptime's checksLive, from this page's own readings.
[![SoundCloud uptime by RealUptime's checks](https://realuptime.io/outages/soundcloud/badge.svg?days=30)](https://realuptime.io/outages/soundcloud)
<a href="https://realuptime.io/outages/soundcloud"><img src="https://realuptime.io/outages/soundcloud/badge.svg?days=30" alt="SoundCloud 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 SoundCloud down?", https://realuptime.io/outages/soundcloud. The readings change with every check, so give the date you read them.

How our checks compare with SoundCloud's stated SLA

At or above your target

Our checks of SoundCloud 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 SoundCloud'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

secondaryfunctional
https://api-v2.soundcloud.com/
secondary
https://soundcloud.com/
primaryfunctional: live API
https://api-v2.soundcloud.com/resolve

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-v2.soundcloud.com

RealUptime is not affiliated with SoundCloud; the name identifies what we checked, and nothing here speaks for SoundCloud's own team. We send a single web request to SoundCloud from 10 regions on our own schedule and time the response. We do not see inside SoundCloud's systems, do not use an account or real transaction, and are not the same signal SoundCloud's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for SoundCloud 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.