On Tuesday, November 17, Apple's own status pages listed outages (some marked resolved) on tools developers use to publish apps, read sales reports and build software, plus issues on iCloud sign-in. The pages we read state no cause, so the question for a business that ships or sells through Apple is which of your jobs wait on which Apple service. Below: what the pages listed, and three checks.
A status page is a company's own notice board for what is working. Apple keeps two: one for developers (publishing apps, build tools, sales reports) and one for the public (iCloud, the App Store and more).
On November 17 both listed problems, starting at different times, for "All users" or "Some users" in Apple's words.
Think of the developer side as a back office and the public side as the till (our comparison; the split is rough, as the sections below show).
We read three Apple pages at 14:39 PST: the developer status feed (rows stamped "11/17/2026 14:30 PST"), the developer System Status page ("Last updated today, 2:39 PM Pacific Standard Time.") and the public System Status page ("Last updated today, 2:39 PM Pacific Standard Time."). Times in the tables are as Apple's pages printed them. Apple's pages change while an event is open; this page does not update by itself. Current status: developer and public. This page is a dated snapshot, not a status service.
Which parts of your business wait on Apple?
A vendor console is the back office a company gives you for running your work on its platform. For a business that ships through Apple, that means the services where you publish apps, read sales reports, build software and sign people in. In our reading, when a console is listed with an outage, a business does not have to stop as a whole; individual jobs may wait. We sort the services Apple listed by the job a business does with them. The grouping is ours, not Apple's.
- Publishing, reporting and build. At 14:39 PST Apple's developer feed listed outages marked "ongoing" for App Store Connect (where apps are submitted and sales are read, our description), Developer ID Notary Service (Apple's check for Mac software sold outside the store, our description), App Store Connect - Analytics and App Store Connect - Sales and Trends. It listed Xcode Cloud (Apple's service for building and delivering apps, our description) with two resolved rows, an outage and an issue.
- Accounts and sign-in. At 14:39 PST the public page listed "iCloud Account & Sign In" as a "Resolved Issue" from 8:45 AM to 1:15 PM, with "Some users were affected". It printed "Available" for "Apple Account", "iCloud Account & Sign In" and "Sign in with Apple", three separate rows.
- Purchases and other public services. The developer feed listed "App Store - In-App Purchases" as a resolved outage from 02:28 to 03:46 PST. The public page listed App Store and Volume Purchase Program as resolved outages from 8:45 AM to 12:00 PM, and AppleCare on Device from 8:15 AM to 12:39 PM. Apple prints the App Store, App Store - In-App Purchases, App Store - Receipt Verification and Volume Purchase Program as separate rows. In our reading, a row listed for one of them does not tell you what happened to a transaction handled by another.
The split is not clean. Apple printed problems on the selling side as well as the back-office side (our grouping), so a neat divide between back-office rows and purchase rows does not fit what the pages list. "Volume Purchase Program" is a row name on Apple's public page. Apple's support page describes it as credit that organizations in Apple School Manager and Apple Business use to buy apps or books. We did not read a page that says what the row means for any rollout.
Which Apple services had nothing listed against them?
At 14:39 PST the feed listed no event for 42 of its 51 services, and the developer page (14:39 PST) printed "Available" for each of them. It printed "Available" for App Store - In-App Purchases, News Publisher and Xcode Cloud too, although the feed lists resolved rows for each. Among the 42 (our grouping):
- App Store Connect parts: App Store Connect API; App Store Connect - App Upload; App Store Connect - App Processing; App Store Connect - TestFlight.
- Messages and purchases: APNS (the push notification service, our description); App Store - Server APIs; App Store - Server Notifications; App Store - Receipt Verification; Apple Pay Production Instance.
- And: Account; Certificates, Identifiers & Profiles; and 31 more.
A row with no event is all the pages show: they do not state what an empty row means for a live app. The feed listed App Store Connect with "All users are affected" while App Store Connect - App Upload carried no event. In our reading, each row is its own line, and an empty row is not a guarantee: it does not tell you whether a given upload, sign-in, purchase or notification worked in your own app. In our reading, a sensible check is to test the operations your business depends on and to read your own error logs.
What does this look like inside a business?
A job map shows in advance what waits. These rows are invented examples, ours.
| Job (our invented example) | Apple service it may wait on (our mapping) | What to decide or watch before a row reads "ongoing" |
|---|---|---|
| Publishing an app update in the App Store | App Store Connect; App Store Connect - App Upload; App Store Connect - App Processing; Xcode Cloud if you build there | Who may say "wait", and who tells the customer that a date moved |
| Shipping a Mac app outside the store | Developer ID Notary Service | Whether a Mac release can wait, and what the customer is told |
| Month-end sales report | App Store Connect - Sales and Trends; App Store Connect - Analytics | Which Apple reports you have already exported to your own files, and how you would reconcile them (Apple's help page says Sales and Trends and Payments and Financial reports can differ) |
| Staff signing in with an Apple account | Apple Account; iCloud Account & Sign In (separate rows) | Who holds the admin login, and who is told |
| Customers signing in to your app with Sign in with Apple | Sign in with Apple (a separate row) | A second sign-in route that works for the same existing accounts, such as email or another provider |
| Selling items or subscriptions inside an app | App Store - In-App Purchases; App Store; App Store - Receipt Verification | Your own purchase logs and failed-purchase counts for the windows Apple printed, set against a normal day |
| Rolling out apps to staff or school devices | Volume Purchase Program; Apple Business; Apple School Manager | Which devices wait on an app, and who tells staff or students |
The middle column lists services a job may wait on; it does not say any of them was listed with an outage. A different kind of dependency sits in our decode of the Microsoft 365 outage: there, a third-party AI tool read a vendor's mail and calendar service.
Does this matter if your app was built with AI?
No status row or message on the Apple pages we read mentions AI. The link is ours. A team can build an app or a workflow with an AI tool and still publish it through App Store Connect, sign customers in and take payment through Apple. In our reading, an AI tool does not remove those dependencies, so put them on the same job map. For fallbacks around software that depends on other vendors, see why AI agents break in production.
Do this week
In our reading, three steps for an owner or manager who ships or sells through Apple. They are ours, not Apple's.
- Write the job map: every release, report, sign-in and purchase in your business that waits on a vendor console, with the service it may wait on next to each (the table above).
- Decide in advance what you do when a row is listed as an outage: who may say "wait", what the customer sees, what the fallback is, and who is told and through which channel. We do not advise anyone to pause or continue any release.
- If you sell through Apple, compare your own purchase logs for the windows Apple printed with a normal day. The Apple pages we read give no counts of affected users, and Apple's help page says daily Sales and Trends reports are available the following day, so a gap in a report is not, by itself, proof of lost purchases.
What did Apple's developer feed list, row by row?
This is the data behind Apple's developer System Status page; every row carries the stamp "11/17/2026 14:30 PST". Apple's message on the ongoing App Store Connect rows reads "Users are experiencing a problem with this service."
| Service as Apple prints it | Apple's type / status word | Start - end (PST) | Extent, in Apple's words |
|---|---|---|---|
| Developer ID Notary Service | Outage / ongoing | 08:25 - | Some users |
| App Store Connect (start 08:50) | Outage / ongoing | 08:50 - | All users |
| App Store Connect (start 10:57) | Outage / ongoing | 10:57 - | All users |
| App Store Connect - Analytics | Outage / ongoing | 11:09 - | Some users |
| App Store Connect - Sales and Trends | Outage / ongoing | 11:09 - | Some users |
| Apple Music Connect | Outage / ongoing | 11:09 - | Some users |
| Apple Music for Artists | Outage / ongoing | 11:09 - | Some users |
| Xcode Cloud (issue, start 13:00) | Issue / resolved | 13:00 - 14:30 (1 hour 30 minutes, our arithmetic) | Some users |
| Xcode Cloud (outage, start 09:00) | Outage / resolved | 09:00 - 13:00 (4 hours, our arithmetic) | All users |
| News Publisher | Performance / resolved | 08:50 - 13:20 (4 hours 30 minutes, our arithmetic) | Some users |
| App Store - In-App Purchases | Outage / resolved | 02:28 - 03:46 (1 hour 18 minutes, our arithmetic) | Some users |
Notes on the table. A dash after a start time is ours: the feed carries no end time for an ongoing row and the page prints "ongoing". Apple's full words are "Some users are affected" for ongoing rows and "Some users were affected" for resolved ones (likewise "All users"); the last column keeps only "All users" or "Some users". In the feed's data, the four rows with the 11:09 start share one event and list each other as affected services; the page draws them as four rows.
What did Apple's public page list?
This is the page for everyone. It has its own clock, so we do not merge it with the feed. At 14:39 PST it printed "3 outages resolved today" and "7 issues resolved today", and no heading for current issues. All nine services in the table print "Available" in the page's list of available services. The pages we read do not say why; in our reading that list shows the state at the read time.
| Service as Apple prints it | Apple's type / status word | Time printed (page stamp: PST) | Extent, in Apple's words |
|---|---|---|---|
| AppleCare on Device | Outage / Resolved | 8:15 AM - 12:39 PM | All users |
| App Store | Outage / Resolved | 8:45 AM - 12:00 PM | Some users |
| Volume Purchase Program (outage) | Outage / Resolved | 8:45 AM - 12:00 PM | Some users |
| Volume Purchase Program (issue) | Issue / Resolved | 9:11 AM - 1:00 PM | Some users |
| iCloud Account & Sign In | Issue / Resolved | 8:45 AM - 1:15 PM | Some users |
| iCloud Web Apps (iCloud.com) | Performance / Resolved | 8:45 AM - 1:15 PM | Some users |
| iCloud Mail | Performance / Resolved | 8:45 AM - 10:25 AM | Some users |
| Apple Business | Issue / Resolved | 10:40 AM - 2:00 PM | Some users |
| Apple School Manager | Issue / Resolved | 10:40 AM - 2:00 PM | Some users |
| Schoolwork | Issue / Resolved | 10:40 AM - 2:00 PM | Some users |
What do the pages not say?
The tables show what the pages listed at the read. They are not a history of the whole day. The three Apple pages give no estimate of when any ongoing row will end and no number of affected users, only "All users" or "Some users". We did not read Apple's newsroom, any other Apple statement or any press report, so we say nothing about what Apple may have said elsewhere.
We do not know. The Apple pages we read (the developer status feed and the developer and public System Status pages, read November 17, 2026) state no cause and name no other company. We make no claim about a link.
How do we know?
At 14:39 PST on November 17, 2026, we fetched Apple's developer status feed and read the developer and public System Status pages in a browser, then matched every quote word for word against saved copies. We read the Apple help pages cited in Sources for the sentences about reports and volume licences. We did not read Apple's newsroom or any press report. This page analyses three Apple status sources only; it is not a full account of what happened or why.
Read next
Fallbacks for software that depends on other vendors: our production AI guide. The November 17 Signal / Noise digest and the AI Failures hub.
For AI workflows with manual fallbacks and approval steps, see our AI automation page.
Sources
- Apple developer status feed (data behind the developer System Status page), every row stamped 11/17/2026 14:30 PST, read November 17, 2026 at 14:39 PST
- Apple developer System Status page, printed "Last updated today, 2:39 PM Pacific Standard Time.", read November 17, 2026 at 14:39 PST
- Apple public System Status page, printed "Last updated today, 2:39 PM Pacific Standard Time.", read November 17, 2026 at 14:39 PST
- Apple Developer help, Differences in reporting tools (Sales and Trends versus Payments and Financial reports), read November 17, 2026 at about 14:00 PST
- Apple Developer help, Sales and Trends reports availability, read November 17, 2026 at about 14:00 PST
- Apple Support, Where to buy Volume Purchase Program (VPP) Credit for Apple School Manager and Apple Business, read November 17, 2026 at about 14:00 PST
- Apple Developer, Xcode Cloud overview, read November 17, 2026 at about 14:00 PST