Is there an Expo outage?
Expo status: Systems Active
Last checked: 8 minutes ago
Get notified about any outages, downtime or incidents for Expo and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 8 minutes ago
Get notified about any outages, downtime or incidents for Expo and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Expo.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| Classic Update Service (Application Serving API) | Active |
| Dev Tools API | Active |
| Push Notifications Broker | Active |
| Website | Active |
| Expo Application Services | Active |
| EAS Build | Active |
| EAS Insights | Active |
| EAS Submit | Active |
| EAS Update | Active |
| Third-Party Services | Active |
| Apple Developer APIs | Active |
| AWS S3 -- us-west-1 | Active |
| AWS S3 -- us-west-2 | Active |
| AWS sqs-us-east-2 | Active |
| Cloudflare CDN/Cache | Active |
| Cloudflare DNS Root Servers | Active |
| Cloudflare DNS Updates | Active |
| Cloudflare Firewall | Active |
| Cloudflare Logs | Active |
| GitHub | Active |
| GitHub API Requests | Active |
| GitHub Webhooks | Active |
| Google Cloud Platform Cloud Key Management Service | Active |
| Google Cloud Platform Google Cloud Pub/Sub | Active |
| Google Cloud Platform Google Cloud SQL | Active |
| Google Cloud Platform - Google Compute Engine | Active |
| Google Cloud Platform - Google Container Engine | Active |
| SendGrid API | Active |
| SendGrid API v3 | Active |
| Stripe API | Active |
| Twilio SMS | Performance Issues |
View the latest incidents for Expo and check for official updates:
Description: A faulty EAS Build deployment broke the "Configure expo-updates" build phase for most developers. The deployment was reverted, and therefore the issue was fixed. We've waived all failed builds between 15:43 GMT and 17:09 GMT.
Status: Resolved
Impact: Major | Started At: March 6, 2024, 4 p.m.
Description: Expo Go code signing works by using the following mechanism: [https://github.com/expo/code-signing-certificates/pull/1](https://github.com/expo/code-signing-certificates/pull/1) - Expo Go root certificate embedded in the Expo Go application. Valid for 40 years. Private key kept offline. - Expo Go intermediate certificate downloaded by `@expo/cli`. Valid for 2 years. Private key kept on signing server. This is a child certificate of the Expo Go root certificate. - Expo Go development certificate generated and downloaded by `@expo/cli`. When a project is started \(`npx expo start`\) we sign the project manifest to ensure scoped module impersonation isn’t possible within Expo Go \(accessing scoped modules for other projects run in Expo Go\). To do this signing, a private key and certificate signing request is generated. This CSR is sent to the expo signing server, and a development certificate valid for 30 days is returned. This development certificate is a child of the Expo Go intermediate certificate. Then, when Expo Go loads an app, it checks that this certificate chain is valid \(all certificates are valid and lineage is correct\). The incident here was that, while we had planned to refresh the Expo Go intermediate certificate every year to preempt the 2 year validity expiration, it was overlooked. So the Expo Go intermediate certificate expired and therefore the certificate chain was invalid. Note that this only affected projects in local development. The fix was to re-generate a new Expo Go intermediate certificate from our root certificate \([https://github.com/expo/code-signing-certificates/pull/14](https://github.com/expo/code-signing-certificates/pull/14)\) and then update the certificates on the signing server. After the signing server updates were deployed to production, all future requests for a development signing certificate now use the new intermediate certificate. Users still seeing issues should ensure they are not using the `--offline` flag \(at least once\) when running `npx expo start` to get a new development certificate with the updated intermediate certificate.
Status: Postmortem
Impact: Major | Started At: Feb. 29, 2024, 2:52 a.m.
Description: Expo Go code signing works by using the following mechanism: [https://github.com/expo/code-signing-certificates/pull/1](https://github.com/expo/code-signing-certificates/pull/1) - Expo Go root certificate embedded in the Expo Go application. Valid for 40 years. Private key kept offline. - Expo Go intermediate certificate downloaded by `@expo/cli`. Valid for 2 years. Private key kept on signing server. This is a child certificate of the Expo Go root certificate. - Expo Go development certificate generated and downloaded by `@expo/cli`. When a project is started \(`npx expo start`\) we sign the project manifest to ensure scoped module impersonation isn’t possible within Expo Go \(accessing scoped modules for other projects run in Expo Go\). To do this signing, a private key and certificate signing request is generated. This CSR is sent to the expo signing server, and a development certificate valid for 30 days is returned. This development certificate is a child of the Expo Go intermediate certificate. Then, when Expo Go loads an app, it checks that this certificate chain is valid \(all certificates are valid and lineage is correct\). The incident here was that, while we had planned to refresh the Expo Go intermediate certificate every year to preempt the 2 year validity expiration, it was overlooked. So the Expo Go intermediate certificate expired and therefore the certificate chain was invalid. Note that this only affected projects in local development. The fix was to re-generate a new Expo Go intermediate certificate from our root certificate \([https://github.com/expo/code-signing-certificates/pull/14](https://github.com/expo/code-signing-certificates/pull/14)\) and then update the certificates on the signing server. After the signing server updates were deployed to production, all future requests for a development signing certificate now use the new intermediate certificate. Users still seeing issues should ensure they are not using the `--offline` flag \(at least once\) when running `npx expo start` to get a new development certificate with the updated intermediate certificate.
Status: Postmortem
Impact: Major | Started At: Feb. 29, 2024, 2:52 a.m.
Description: The service was back online with security improvements as of 5:11PM PST
Status: Resolved
Impact: Minor | Started At: Jan. 25, 2024, 12:54 a.m.
Description: Snack uses a few services to make it work, and a couple of them became completely unavailable for about half an hour. The cause was that we upgraded our main cluster to use faster servers but some of the services were labeled as being compatible only with the older servers and didn’t have any hardware to run on. In practice, all of our services are compatible with the newer servers and fixing the compatibility labels brought the unavailable services back.
Status: Postmortem
Impact: Minor | Started At: Dec. 14, 2023, 9 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
