Last checked: 9 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: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: July 9, 2024, 3:25 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: July 9, 2024, 3:25 a.m.
Description: The faulty deployment introduced a bug that caused build artifacts to not be uploaded correctly to storage buckets. Developers trying to download the artifacts of affected builds could see an error like "The specified key does not exist. No such object: ..." The issue also affected submissions trying to upload the builds with broken artifacts. The developers who encountered the issue saw an error like "Failed to download the archive file (Response code: 404 Not Found)" The issue was identified by the Expo team and the deployment was reverted at around 10 AM GMT. The charges for all of the broken builds were waived.
Status: Resolved
Impact: Major | Started At: June 26, 2024, 6:30 a.m.
Description: The faulty deployment introduced a bug that caused build artifacts to not be uploaded correctly to storage buckets. Developers trying to download the artifacts of affected builds could see an error like "The specified key does not exist. No such object: ..." The issue also affected submissions trying to upload the builds with broken artifacts. The developers who encountered the issue saw an error like "Failed to download the archive file (Response code: 404 Not Found)" The issue was identified by the Expo team and the deployment was reverted at around 10 AM GMT. The charges for all of the broken builds were waived.
Status: Resolved
Impact: Major | Started At: June 26, 2024, 6:30 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: June 24, 2024, 3:38 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.