Expo reported "EAS background operations availability issues" on its status page at 2026-09-01 11:45 UTC.

When did the incident start and end?

It started at 2026-09-01 11:45 UTC and ended at 2026-09-01 12:41 UTC. It lasted 56 min.

How do I get alerts for Expo?

Subscribe to the Expo live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Expo. outages.live reads it every few minutes and keeps every update.

ExpoIncident · 2026-09-01 11:45 UTC

EAS background operations availability issues

Q: What is affected?

Expo lists these components: EAS Build, EAS Submit, EAS Update, EAS Insights, EAS Workflows, EAS Hosting, and 6 more.

ResolvedOfficial update

This incident has been resolved.

The latest update from Expo.

State

Resolved

Started

61 d ago

2026-09-01 11:45 UTC

Lasted

56 min

until 2026-09-01 12:41 UTC

Worst impact

Degraded

Timeline

4 updates

11:4511:5912:1312:2712:41

DegradedUpdate postedTimes in UTC

Investigating

19 min 33%

Monitoring

37 min 67%

Updates

Times in UTC

As posted by Expo

Resolved2026-09-01 12:41 UTC

This incident has been resolved.

Monitoring2026-09-01 12:10 UTC

Systems have mostly recovered.

Monitoring2026-09-01 12:04 UTC

A fix has been implemented and we are monitoring the systems as they are recovering.

Investigating2026-09-01 11:45 UTC

We are experiencing availability problems with our background job processing. This affects broad set of operations across EAS. We are investigating the issue and will provide updates as soon as we have more information.

Affected components

EAS BuildEAS SubmitEAS UpdateEAS InsightsEAS WorkflowsEAS HostingExpo Application Services - EAS BuildExpo Application Services - EAS Submit

Expo in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

2 h 34 min

This incident

64% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

18 h

median 2 h 34 min

90 days agoToday

Other Expo incidents

All incidents

Expo·Elevated submission error rates

This incident has been resolved.

Resolvedresolved 15 d ago

Expo·Elevated iOS submission error rates

This incident has been resolved.

Resolvedresolved 16 d ago

Expo·Elevated API server error rates affecting submissions and builds

This incident has been resolved.

Resolvedresolved 18 d ago

Expo·Website and services partially unavailable due to high database load

This incident has been resolved.

Resolvedresolved 26 d ago

Expo·EAS Update cache issue for rollout updates

This incident has been resolved.

Resolvedresolved 38 d ago

Follow Expo

Your coding agent knows when Expo is down, and tells you when a failure is theirs, not yours. You can also get Expo incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "expo" and tell me if Expo has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.cc/feed.xml?providers=expo

Slack

/feed subscribe https://outages.cc/feed.xml?providers=expo

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane