Skip to content

Outage tracker / Apple iCloud

Is Apple iCloud down?

I'm having a problem

Vendor reports no incidentWhat Apple iCloud reports

Apple iCloud reports no incident on its status page.

As of the last successful poll, 2026-10-19 21:24 UTC.

Apple iCloud's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked moments ago

Our checks of Apple iCloud pass from all 10 regions we check.

As of Oct 19, 2026, 9:26 PM UTC, RealUptime's checks of Apple iCloud passed in all 10 regions that returned a reading.

Front-door and live API checks

Email me when Apple iCloud reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Apple iCloud's own statement from its status page, with our regional reading beside it.

our check readinglive · checked Oct 19, 2026, 9:26 PM UTC
US-East372 msChecks passing
US-West583 msChecks passing
Europe336 msChecks passing
Asia-Pacific689 msChecks passing
US-Central858 msChecks passing
Canada1359 msChecks passing
UK418 msChecks passing
Southeast Asia1157 msChecks passing
Australia1174 msChecks passing
South America1052 msChecks passing
their status pagetheir claim, not our reading

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

Apple iCloud response time, by region

US-East
899msp95 · latest
10s5s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 427ms2026-09-21 UTC: p95 384ms2026-09-22 UTC: p95 488ms2026-09-23 UTC: p95 543ms2026-09-24 UTC: p95 501ms2026-09-25 UTC: p95 476ms2026-09-26 UTC: p95 450ms2026-09-27 UTC: p95 394ms2026-09-28 UTC: p95 454ms2026-09-29 UTC: p95 431ms2026-09-30 UTC: p95 6.3s2026-10-01 UTC: p95 7.2s2026-10-02 UTC: p95 383ms2026-10-03 UTC: p95 367ms2026-10-04 UTC: p95 404ms2026-10-05 UTC: p95 394ms2026-10-06 UTC: p95 389ms2026-10-07 UTC: p95 433ms2026-10-08 UTC: p95 431ms2026-10-09 UTC: p95 377ms2026-10-10 UTC: p95 382ms2026-10-11 UTC: p95 388ms2026-10-12 UTC: p95 421ms2026-10-13 UTC: p95 392ms2026-10-14 UTC: p95 406ms2026-10-15 UTC: p95 404ms2026-10-16 UTC: p95 417ms2026-10-17 UTC: p95 533ms2026-10-18 UTC: p95 668ms2026-10-19 UTC: p95 899ms
Sep 20Oct 4Oct 19
US-West
1.2sp95 · 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-09-20 UTC: p95 920ms2026-09-21 UTC: p95 837ms2026-09-22 UTC: p95 872ms2026-09-23 UTC: p95 880ms2026-09-24 UTC: p95 928ms2026-09-25 UTC: p95 933ms2026-09-26 UTC: p95 944ms2026-09-27 UTC: p95 915ms2026-09-28 UTC: p95 899ms2026-09-29 UTC: p95 916ms2026-09-30 UTC: p95 936ms2026-10-01 UTC: p95 927ms2026-10-02 UTC: p95 838ms2026-10-03 UTC: p95 888ms2026-10-04 UTC: p95 920ms2026-10-05 UTC: p95 829ms2026-10-06 UTC: p95 831ms2026-10-07 UTC: p95 903ms2026-10-08 UTC: p95 887ms2026-10-09 UTC: p95 863ms2026-10-10 UTC: p95 850ms2026-10-11 UTC: p95 869ms2026-10-12 UTC: p95 905ms2026-10-13 UTC: p95 836ms2026-10-14 UTC: p95 818ms2026-10-15 UTC: p95 893ms2026-10-16 UTC: p95 857ms2026-10-17 UTC: p95 848ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s
Sep 20Oct 4Oct 19
Europe
581msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 527ms2026-09-21 UTC: p95 524ms2026-09-22 UTC: p95 519ms2026-09-23 UTC: p95 546ms2026-09-24 UTC: p95 546ms2026-09-25 UTC: p95 517ms2026-09-26 UTC: p95 525ms2026-09-27 UTC: p95 561ms2026-09-28 UTC: p95 541ms2026-09-29 UTC: p95 548ms2026-09-30 UTC: p95 526ms2026-10-01 UTC: p95 611ms2026-10-02 UTC: p95 514ms2026-10-03 UTC: p95 546ms2026-10-04 UTC: p95 545ms2026-10-05 UTC: p95 499ms2026-10-06 UTC: p95 508ms2026-10-07 UTC: p95 640ms2026-10-08 UTC: p95 568ms2026-10-09 UTC: p95 482ms2026-10-10 UTC: p95 517ms2026-10-11 UTC: p95 519ms2026-10-12 UTC: p95 526ms2026-10-13 UTC: p95 502ms2026-10-14 UTC: p95 538ms2026-10-15 UTC: p95 570ms2026-10-16 UTC: p95 534ms2026-10-17 UTC: p95 462ms2026-10-18 UTC: p95 523ms2026-10-19 UTC: p95 581ms
Sep 20Oct 4Oct 19
Asia-Pacific
1.1sp95 · 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-09-20 UTC: p95 657ms2026-09-21 UTC: p95 692ms2026-09-22 UTC: p95 777ms2026-09-23 UTC: p95 678ms2026-09-24 UTC: p95 881ms2026-09-25 UTC: p95 844ms2026-09-26 UTC: p95 810ms2026-09-27 UTC: p95 850ms2026-09-28 UTC: p95 829ms2026-09-29 UTC: p95 665ms2026-09-30 UTC: p95 855ms2026-10-01 UTC: p95 727ms2026-10-02 UTC: p95 885ms2026-10-03 UTC: p95 790ms2026-10-04 UTC: p95 730ms2026-10-05 UTC: p95 704ms2026-10-06 UTC: p95 765ms2026-10-07 UTC: p95 680ms2026-10-08 UTC: p95 572ms2026-10-09 UTC: p95 714ms2026-10-10 UTC: p95 614ms2026-10-11 UTC: p95 654ms2026-10-12 UTC: p95 694ms2026-10-13 UTC: p95 635ms2026-10-14 UTC: p95 716ms2026-10-15 UTC: p95 849ms2026-10-16 UTC: p95 764ms2026-10-17 UTC: p95 889ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.1s
Sep 20Oct 4Oct 19
US-Central
1.5sp95 · 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-20 UTC: p95 1.0s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.2s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.0s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 1.1s2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.5s
Sep 20Oct 4Oct 19
Canada
1.3sp95 · 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-09-20 UTC: p95 556ms2026-09-21 UTC: p95 578ms2026-09-22 UTC: p95 882ms2026-09-23 UTC: p95 939ms2026-09-24 UTC: p95 677ms2026-09-25 UTC: p95 826ms2026-09-26 UTC: p95 917ms2026-09-27 UTC: p95 557ms2026-09-28 UTC: p95 918ms2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 882ms2026-10-01 UTC: p95 636ms2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 985ms2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 1.0s2026-10-07 UTC: p95 648ms2026-10-08 UTC: p95 952ms2026-10-09 UTC: p95 590ms2026-10-10 UTC: p95 748ms2026-10-11 UTC: p95 913ms2026-10-12 UTC: p95 994ms2026-10-13 UTC: p95 1.0s2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 1.0s2026-10-16 UTC: p95 674ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.3s
Sep 20Oct 4Oct 19
UK
731msp95 · 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-20 UTC: p95 569ms2026-09-21 UTC: p95 546ms2026-09-22 UTC: p95 583ms2026-09-23 UTC: p95 658ms2026-09-24 UTC: p95 691ms2026-09-25 UTC: p95 798ms2026-09-26 UTC: p95 787ms2026-09-27 UTC: p95 824ms2026-09-28 UTC: p95 666ms2026-09-29 UTC: p95 616ms2026-09-30 UTC: p95 688ms2026-10-01 UTC: p95 711ms2026-10-02 UTC: p95 718ms2026-10-03 UTC: p95 660ms2026-10-04 UTC: p95 657ms2026-10-05 UTC: p95 676ms2026-10-06 UTC: p95 674ms2026-10-07 UTC: p95 680ms2026-10-08 UTC: p95 647ms2026-10-09 UTC: p95 664ms2026-10-10 UTC: p95 798ms2026-10-11 UTC: p95 741ms2026-10-12 UTC: p95 694ms2026-10-13 UTC: p95 684ms2026-10-14 UTC: p95 659ms2026-10-15 UTC: p95 652ms2026-10-16 UTC: p95 682ms2026-10-17 UTC: p95 762ms2026-10-18 UTC: p95 820ms2026-10-19 UTC: p95 731ms
Sep 20Oct 4Oct 19
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-20 UTC: p95 1.0s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 1.4s2026-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.5s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 1.5s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 1.6s2026-10-06 UTC: p95 1.7s2026-10-07 UTC: p95 1.5s2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 958ms2026-10-11 UTC: p95 1.0s2026-10-12 UTC: p95 1.0s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 974ms2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.2s
Sep 20Oct 4Oct 19
Australia
1.9sp95 · 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-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 1.0s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.0s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 1.9s2026-10-19 UTC: p95 1.9s
Sep 20Oct 4Oct 19
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-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.4s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.7s2026-09-26 UTC: p95 1.5s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 1.7s2026-09-30 UTC: p95 1.8s2026-10-01 UTC: p95 1.6s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.3s2026-10-04 UTC: p95 1.7s2026-10-05 UTC: p95 1.2s2026-10-06 UTC: p95 1.7s2026-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 1.9s2026-10-09 UTC: p95 1.6s2026-10-10 UTC: p95 1.7s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.5s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.4s
Sep 20Oct 4Oct 19

Check your own site while you wait on Apple iCloud

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

What we measured, function by function

Apple iCloud 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: 372msstatus code: 421checked: Oct 19, 2026, 9:25 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Apple iCloud normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 583msstatus code: 421checked: Oct 19, 2026, 9:25 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Apple iCloud normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 858msstatus code: 421checked: Oct 19, 2026, 9:24 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Apple iCloud normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 1359msstatus code: 421checked: Oct 19, 2026, 9:23 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Apple iCloud normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1052msstatus code: 421checked: Oct 19, 2026, 9:24 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Apple iCloud 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: 336msstatus code: 421checked: Oct 19, 2026, 9:25 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Apple iCloud normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 418msstatus code: 421checked: Oct 19, 2026, 9:26 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Apple iCloud 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: 689msstatus code: 421checked: Oct 19, 2026, 9:26 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Apple iCloud normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1157msstatus code: 421checked: Oct 19, 2026, 9:23 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Apple iCloud normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 1174msstatus code: 421checked: Oct 19, 2026, 9:26 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Apple iCloud 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 Apple iCloud, 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 Apple iCloud yet, which is not evidence that nothing is wrong.

Recent probe events

No probe events on record yet for Apple iCloud.

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

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

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

Apple iCloud uptime by RealUptime's checksLive, from this page's own readings.
[![Apple iCloud uptime by RealUptime's checks](https://realuptime.io/outages/icloud/badge.svg?days=30)](https://realuptime.io/outages/icloud)
<a href="https://realuptime.io/outages/icloud"><img src="https://realuptime.io/outages/icloud/badge.svg?days=30" alt="Apple iCloud uptime by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

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

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

primaryfunctional: live API
https://setup.icloud.com/setup/ws/1/validate
secondary
https://www.apple.com/support/systemstatus/

What our check can and cannot see

A pass means the service's servers answered our request with the error they give a request that carries no account or valid input. It does not show that sign-in works or that any real request succeeds.

Host checked: setup.icloud.com

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