Expo reported "Partially Degraded Service" on its status page at 2026-11-04 11:15 UTC. Expo reports that GitHub API Requests were partially degraded. Expo resolved the incident. The outage lasted about 6 minutes.

Expo lists these components: GitHub API Requests.

When did the incident start and end?

It started at 2026-11-04 11:15 UTC and ended at 2026-11-04 11:21 UTC. It lasted 6 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. A language model writes the summary from those updates.

ExpoIncident ·

Partially Degraded Service

ResolvedOfficial update

Expo reports that GitHub API Requests were partially degraded. Expo resolved the incident. The outage lasted about 6 minutes.

State

Resolved

Started

Lasted

6 min

Worst impact

Degraded

Timeline

2 updates

11:1511:1611:1811:1911:21

DegradedUpdate postedTimes in UTC

Components degraded

6 min 100%

Updates

Times in UTC

As posted by Expo

Resolved

Components degraded

Affected components

GitHub API Requests

Expo in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

2 h 22 min

This incident

96% 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 22 min

90 days agoToday

Other Expo incidents

All incidents

Expo·Partially Degraded Service

Expo reported partially degraded service for GitHub API Requests. Expo later reported that the incident is resolved. The incident lasted 15 minutes.

Resolved

Expo·Elevated submission error rates

This incident has been resolved.

Resolved

Expo·Elevated iOS submission error rates

This incident has been resolved.

Resolved

Expo·Elevated API server error rates affecting submissions and builds

This incident has been resolved.

Resolved

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

This incident has been resolved.

Resolved

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.live/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.live/feed.xml?providers=expo

Slack

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane