Live status check

Is Apple Services (App Store, Apple Account) down right now?

We check apple.com from one measurement point when you open this page. This shows what we saw, not a worldwide verdict.

A fresh check of apple.com runs in your browser. If no result appears, run the check on the start page.

Our last check

Not checked yet — a fresh check starts when you open this page.

About Apple Services (App Store, Apple Account) problems

Apple Services problems can concern the App Store, Apple Account sign-in, Apple Music or payments. Check Apple's System Status page first, then confirm you are signed in with the right Apple Account and that its payment method is still valid. If the problem affects only one device, signing out of the Apple Account on that device and back in can help.

Official information

Apple Services (App Store, Apple Account) official status page (verified )

Our check and Apple Services (App Store, Apple Account)'s own status page can disagree. We test from one location and read only the homepage response. The provider reports what it knows about its own systems, such as sign-in, apps or single regions. A site can answer our check while one feature is broken, and a regional problem can affect one location but not another.

Apple Services (App Store, Apple Account) help pages

How this check works

  • One measurement location (single-self-hosted-probe), not a worldwide test.
  • We read only the response headers of the HTTPS homepage; page content and features are not tested.
  • We follow at most 5 HTTPS redirects and check every new address again.
  • The whole check stops after 10 seconds.
  • Results are reused for 60 seconds; this page refreshes its saved check at most every 10 minutes.

Full method and limits

Typical Apple Services (App Store, Apple Account) problems

An editorial list of typical problems, not based on live user reports.

General fixes: Cloud and hosting

  1. Read the logs first Cloud dashboards keep logs for each deploy, function or sync. The first error in the log is a good place to start looking for the cause.
  2. Verify the DNS records If a custom domain fails, compare its DNS records with the values the provider shows. DNS changes can take time to reach every network.
  3. Check storage and quotas A full storage plan or a used-up quota stops syncs, uploads and deploys even when the service itself works.
  4. Separate one site from the provider If a single website shows an error page from its hosting or CDN provider, the cause can be that website's own server rather than a problem with the provider for everyone.

Check another website

One measurement point. Results explain what we saw, not a worldwide verdict.