Apple's November 17 outage took down App Store Connect. Here is how I would plan my Mac launch around it
By Justinas Rolando, maker of MacPip
On Tuesday, November 17, 2026, Apple said "an internal update caused some outages". iCloud sign-in, the App Store, Apple Music and App Store Connect had problems, and Xcode Cloud was listed too. To keep a Mac app launch safe from the next one: get the build approved days early and release it manually, schedule sale prices ahead in App Store Connect, notarize and staple before launch day, make sure you can build without Xcode Cloud, and check Apple's Developer System Status page first.
On Tuesday, November 17, a lot of Apple went quiet at once. iCloud sign-in, the App Store, Apple Music and, for those of us who ship apps, App Store Connect. If you had a release planned that day, you found out that your plan had a single point of failure, and it wasn't yours.
Nothing I did caused it and nothing I could do fixed it. But with Black Friday next week, it's a good moment to look at which parts of a launch need Apple to be up at the exact hour you need it.
What happened
Here is what's on the record from that day:
- Sign-in and purchases. BleepingComputer put the start of the iCloud Account and Sign In problem at about 11:45 a.m. Eastern, with AppleCare purchases on device failing from about 11:15, and more services added through the afternoon, including iCloud Mail and Apple School Manager.
- App Store Connect. iThinkDifferent reported the App Store Connect outage starting at 8:50 a.m. Pacific. It said App Upload, App Processing, TestFlight, Analytics, Sales and Trends and the App Store Connect API were still listed as available. So the website was down, but most of the pipes behind it weren't.
- Xcode Cloud. Colombia One, reading Apple's developer status page, listed App Store Connect and Xcode Cloud among the affected services.
- Apple's explanation. In a statement to Bloomberg, quoted by Macworld: "Many of our systems are back up and running after an internal update caused some outages this morning." Macworld later added that, according to Apple, all services had been restored.
It wasn't the only wobble this month. On November 12, The Apple Post reported Apple's status page showing degraded performance for App Store Connect and its App Processing for some users.
Two incidents in a week isn't a scandal. Big systems break. It's just something to plan around.
Why it matters if you make a Mac app
Most launch day problems are ones you can fix yourself: a typo, a broken download link, a missing screenshot. An outage is different. You can't fix it, so the only defence is not to need Apple's systems at the moment you're busiest.
And the next two weeks are busy. Black Friday is November 27. If you sell a Mac app, you probably have a sale, a launch or an update you want out before then.
What I would do
1. Get the build approved early, then release it yourself. When you submit a version, App Store Connect lets you choose to release it manually. Once it's approved, its status becomes Pending Developer Release, and you release it when you like. Apple's help page says it can then take up to 24 hours to appear on the App Store, so release the day before, not the hour before. The slow and unpredictable step, review, is then done days ahead.
2. Schedule the sale price, don't click it on the day. Under Pricing and Availability, App Store Connect lets you add a temporary price change with a start and an end date. Set your Black Friday price this week. If the website is down on Friday morning, the change was saved days ago.
3. Use phased release for a big update. Apple's phased release works for macOS too: the update reaches people with automatic updates over 7 days, and you can pause it for up to 30 days in total. If something is wrong, fewer people get it, and you're not racing a dashboard you can't open.
4. Notarize and staple before launch day. If you sell outside the Mac App Store, notarize your app and your DMG when you build them, not on launch morning. A stapled ticket travels with the file, so Gatekeeper can find it even without a network connection. The notarization explainer reads your spctl and stapler output if you're not sure it worked.
5. Don't build your launch on Xcode Cloud alone. It was on the list. If your only way to make a release build is a cloud workflow, make sure you can also archive, sign and upload from your own Mac. Try it once this week, while nothing is on fire.
6. Know where to look. Bookmark Apple's Developer System Status page. It's the first place to check before you spend an hour on an upload that was never going to work.
7. Keep your own channels working. Your website, your mailing list and your direct download don't depend on Apple's servers. If App Store pages are slow on launch day, people can still read about the app and try it.
The MacPip angle
On MacPip, your launch day is the day you pick. That only helps if the download works when people click. So I'd set the date a few days after the build is approved, never the same day.
If you're planning around Black Friday, the launch plan builder turns a date into a dated list of steps, the launch checklist has the signing and notarization steps in order, and you can add your deal to the Black Friday page. Listing your app is free. Listings are scanned automatically when they're submitted, and a blue tick only means MacPip checked the app on a date.
If you just use a Mac
When an app won't download or your Apple Account won't sign in, check Apple's System Status page before you reset anything. On November 17, plenty of people signed out and back in again for nothing.
Sources
- Macworld: iCloud and other services are struggling to stay online today (November 17, 2026)
- BleepingComputer: Apple reports outages affecting iCloud Mail, AppleCare and more (November 17, 2026)
- iThinkDifferent: Apple confirms iCloud sign-in problems and App Store Connect outage (November 17, 2026)
- Colombia One: Apple restores some services after internal update causes widespread outage (November 18, 2026)
- The Apple Post: Apple reports App Store Connect issues affecting developers (November 12, 2026)
- Apple Developer: Select an App Store version release option
- Apple Developer: Schedule price changes for apps
- Apple Developer: Release a version update in phases
- Apple Developer: System Status
Keep reading
- Claude Fable 5.2 and Mythos 5.2: what's new, the benchmarks, and what it means for your MacClaude Fable 5.2 and Mythos 5.2 came out on November 9, 2026. Anthropic's benchmarks as charts, the prices, what changes on a Mac, and four free tools.
- Old Developer ID certificates stop on February 1, 2027. Here is what I would do this weekApple's original Developer ID authority expires on February 1, 2027. Packages signed from it stop installing, and certificates from it stop signing. How to tell if yours is affected, and how to move to G2 before the date.
- Rosetta stops after macOS 27. Here is what I would check in my Mac appApple says macOS 27 is the last release with Rosetta for Intel apps, and macOS 28 keeps it only for some older games. How to find the Intel code hiding in your Mac app, and how people can see which of their apps are affected.
- macOS 27.3 makes Full Disk Access harder to get. Here is what I would change in my Mac appApple said on October 2 that granting Full Disk Access will take very explicit user action, and code in the macOS 27.3 beta stops denied apps from appearing in the list. What changes, who it hits, and what I would change in a Mac app now.
- Apple wrote down how App Review works. Here is what I would change before I submitApple published App Review help articles on review times, the Notes field, Bug Fix Submissions, appeals, screenshots, purpose strings and account deletion. What they say, and what I would change in a Mac app before I submit.
- The Swift Student Challenge takes Mac apps now. Here is what I would buildApple's Swift Student Challenge 2027 opens February 8 to 28 and, for the first time, takes apps for any Apple platform, macOS included. The rules, the dates, and how I would plan a Mac entry.
- macOS 27.2.1 stops curl trusting eMudhra. Here is what I would check in my Mac appmacOS 27.2.1, 26.7.3 and 15.8.3 remove five root certificates from /etc/ssl/cert.pem after the eMudhra key compromise. What changed, who it reaches, and what Mac app makers should test.
- Live Activities are coming to the Mac menu bar. Here is what I would do with my Mac appThe macOS 27.3 beta puts Live Activities in the menu bar of Apple silicon Macs, and Mac apps can start their own. What changed, the limits, and what to try first.
- Memory is making Macs dearer. Here is what I would do with my Mac appApple says memory will keep Macs short and pricier into 2027, and the cheapest Mac has 8 GB. Why that matters for your Mac app, and the checks to run this week.
- Apple now lets you talk to people who cancel. Here is what I would do with my Mac appSince November 4, App Store subscriptions can show a message or offer when someone cancels. The rules, what Apple says it does, and what to check on the Mac.
- Apple is adding two age rating questions. Here is what I would do with my Mac appFrom November 16, App Store Connect asks about shared location and dating features, and every app must answer by January 12, 2027. What changed and what to do.
- Siri AI is open to every developer now. Here is what I would do with my Mac appApple opened Siri AI to all developers in the macOS 27.3 beta. What changed, what you can and cannot ship yet, and a short plan for a small Mac app.
- Touchscreen Macs ship on November 6. Here is what I would check in my Mac appApple's first touch Macs arrive November 6. What changed, what Apple tells developers to do, and a short list of things to test in your own Mac app.
- Introducing MacPipWhat MacPip is, why I built it, how listing and launch day work, what a blue tick really means, and the real numbers from its first days.
- How to launch a Mac app: a checklist that fits on one pageWhat to do before, on and after launch day for a Mac app: signing, your page, directories, Product Hunt, Show HN and what to measure.
- How to write a one-line description that says what your Mac app doesA plain way to write the one line under your Mac app's name: name the job, cut the hype, and test it on someone who has never seen the app.
- Signing and notarization, in plain words, for people making their first Mac appWhat code signing, notarization and stapling each do, in what order, what your users see without them, and how to check your own build.
- What a dofollow link is honestly worth, from a site that offers oneWhat dofollow means, what Google says about links, why a link from a new directory is worth little today, and what to do instead of buying links.
Making apps for iPhone and iPad too? They have their own free home on iPip, MacPip's sister directory.