On Tuesday, Apple’s App Store Connect was showing performance issues, leaving some developers unable to reliably access the tools they use to manage App Store releases. Apple has acknowledged the incident on its Developer System Status page, but has not explained the cause or given a resolution time, according to 9to5Mac .
The disruption is not being described as a full outage. Apple’s status language says the issue affects “some users” and identifies it only as a “performance” problem, which leaves developers to infer the scope from their own failed sessions and reports from peers.
June 23 outage hits App Store Connect during the developer workday
Developers began flagging access problems publicly on X after Apple’s status page listed the App Store Connect issue. 9to5Mac reported that multiple users on X confirmed the problem, pointing to developer-side access trouble rather than a complete shutdown of Apple’s consumer-facing App Store.
The available source material does not establish an official incident start time, identify a single failing component or provide enough detail to verify specific user quotes. The clearest supported read is narrower: Apple’s own status page showed a performance issue affecting some users, and public developer reports on X backed up that App Store Connect was not working normally for everyone during the June 23 workday.
App Store Connect is the main operating console for App Store developers. Teams use it to manage app records, prepare submissions, update metadata, handle release settings and interact with Apple’s distribution workflow. When access becomes unreliable, the pain is immediate even if the consumer-facing App Store remains online.
Error reports point beyond one isolated account
The public complaints do not prove a universal outage, but they do show the problem is not limited to a single developer’s local setup. The reports cited by 9to5Mac indicate multiple developers were seeing problems with App Store Connect access.
StatusGator also classified Apple Developer App Store Connect as having a minor outage, reporting confirmed issues with App Store Connect while listing other Apple Developer components as operational. Its page showed 240 user-submitted outage reports in the past 24 hours, with top reported issues including Error message, App not loading, Connectivity issue, Sign in problem, Service down, Server not responding and Slow performance.
| Source | Current signal | Scope described |
|---|---|---|
| Apple Developer System Status | Performance issue | Affects “some users” |
| 9to5Mac | Partial unavailability | Multiple X reports from developers |
| StatusGator | Minor outage | App Store Connect affected; other listed components operational |
That distinction matters. A partial outage can be harder for teams to diagnose because one developer may still be able to load a page while another is bounced out, shown an error or blocked from a specific workflow.
MLXIO analysis: Apple’s wording suggests degraded service rather than total downtime. That means the practical impact depends on where a developer is in the release process. A team browsing status pages may lose little time; a team trying to submit a build, adjust release settings or prepare a launch could hit a hard stop.
App submissions and release controls could become the pressure point
The supplied reports do not confirm broad failures across every App Store Connect function. They do, however, confirm access problems and degraded performance affecting at least some developers.
That is enough to create operational risk for affected teams. App Store Connect sits between a developer’s internal release work and Apple’s App Store distribution process, so account instability can delay tasks that require Apple’s portal rather than local tools.
Apple’s own App Store Connect documentation shows how release controls depend on the service. For example, developers can use phased release for app updates, gradually rolling an approved version out over 7 days: 1% on day one, 2% on day two, 5% on day three, 10% on day four, 20% on day five, 50% on day six and 100% on day seven.
If a developer cannot reliably access the portal, the issue is not theoretical. Time-sensitive edits, release pauses, metadata changes or submission checks can become waiting games. The sources do not show that Apple’s app review queues or TestFlight workflows are currently delayed, but those are the kinds of developer operations that depend on stable App Store Connect access.
For readers tracking Apple’s broader software and App Store pressure points, MLXIO has also covered 1,000 Apps an Hour Force Apple's App Store Crackdown and Android Chats Win Big as iOS 27 Fixes RCS Reactions. Those are separate stories, but they underscore why developer-facing Apple systems attract close scrutiny when they wobble.
Apple has not said what broke or when it will be fixed
Apple has not shared additional details beyond the Developer System Status entry cited by 9to5Mac. As of the report, there was no public explanation for the cause, no detailed component breakdown and no firm timeline for full restoration.
That leaves developers with a narrow set of practical steps:
- Monitor: Keep Apple’s Developer System Status page open for a resolution notice or expanded incident details.
- Document: Save screenshots or timestamps of failed submissions, login loops or App Store Connect errors tied to time-sensitive work.
- Retry carefully: Avoid assuming a failed action completed if the session errored or redirected.
- Escalate: If a deadline is involved, affected teams may need to track Apple developer channels or contact support.
The next meaningful update will come from Apple marking the incident resolved or clarifying which App Store Connect functions were affected. Until then, the safest read is limited but consequential: App Store Connect is partially impaired for some developers, and Apple has not yet explained why.
Impact Analysis
- Developers rely on App Store Connect to submit updates and manage releases, so unreliable access can delay app changes.
- Apple has acknowledged the issue but has not provided a cause or resolution timeline.
- The incident appears limited to some developers rather than a full App Store outage.
