Crowd sourced reporting of App Store Connect failures?

(always out-of-date) Developer system status is visible here: https://developer.apple.com/system-status/

However this is mostly out of date and seems to be manually updated since hours go by at times and thousands of reports are needed (both via Feedback Reporter or the dev forums) before this page acknowledges an outage of any kind.

Please add a way to contact Apple directly from that page or "ping" whoever's concerned somehow so we can say "Hey guys, it's broken!". If enough people ping, then Apple can take some action. Right now iCloud / App Developer related services are offline multiple times a year and it's very inconvenient as no one even acknowledges till it's widespread everywhere (forums, stackoverflow, twitter etc).

Google Play Store services are super efficient in this regard - they respond to bug reports within a few hours, acknowledge it and are transparent. Their server outages seem to be automatically monitored and controlled so that human-operators can be pinged appropriately.

Every now and then the notarization service goes down and it's a pain because this means we can no longer notarize and push even "direct" macOS apps with critical fixes.

Replies

It's now been several hours (around 4 hours from the time I started counting) and the status page still shows that everything's okay. Yet, everything is NOT okay. We've been unable to process and submit our builds to App Store / Testflight.

Seems like developer status page has now been updated to indicate performance issues with ASC and ASCAPI.

And that's my point. If you click on one of them, they show you that the performance issues began roughly 2 hours ago. That's incorrect - if you scan through the forums, it's been at least 8 hours this way. Why have a status page if it's updated manually, and that too after several hours of reporting and then misreport the incident time?

It's starting to look like this: https://github.blog/2022-03-23-an-update-on-recent-service-disruptions/

Here we go again.