The real question is - why isn't this automatically detected and why did it take 8 hours and 17k reports (and numerous bug reports) to detect this outage?

The "system status page is also updated" is a little concerning. Is this manually updated? What's the point of this page if nothing's automated? Why did we "all" have to report the issue? I've left some constructive thoughts for your consideration: https://developer.apple.com/forums/thread/705799#705799021

No one's angry - but we're certainly concerned. Our businesses (and apps) depend upon their servers uptime. This isn't a free service, as Apple has clearly made its case in recent times, we all fund it. What's truly important here is that there needs to be far less time elapsed between the time the server goes down and the time it gets noticed.

Same here. It's never worked for us and we keep seeing a degradation in performance as Core Data returns a fault for all the relationships. Filed: FB11973884

We're seeing this on the latest Version 16.0 (16A242d). Our app uses Swift concurrency + withCheckedContinuation and withCheckedThrowingContinuation and these are crashing on iOS and macOS randomly for random people repeatedly. We've tried just about everything but the crashes "shift" from one part of the app to another. So there's some kind of memory corruption going on.

Unfortunately this is happening to us with all our apps built with Xcode 16's latest version. It's causing random crashes and we're unable to reproduce this ourselves, but seeing an increase in crashes after building and releasing with xcode 16 recently: FB15151141 We had not built or released our app with any of Xcode 16's prior beta versions. This is our first release and there's no stoppage of crash reports coming in. The crashes are happening for macOS 15 and iOS 18 users.