CINXE.COM
Expo Status - Incident History
<?xml version="1.0" encoding="UTF-8"?> <rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"> <channel> <title>Expo Status - Incident History</title> <link>https://status.expo.dev</link> <description>Statuspage</description> <pubDate>Mon, 24 Mar 2025 04:36:12 -0700</pubDate> <item> <title>Errors in EAS Dashboard</title> <description> <p><small>Mar <var data-var='date'>21</var>, <var data-var='time'>09:25</var> PDT</small><br><strong>Resolved</strong> - For around an hour between 8 a.m. PST and 9 a.m. PST some users were not able to access parts of EAS Dashboard. The situation was resolved at 9:07 a. m. PST. We are investigating the root cause.</p> </description> <pubDate>Fri, 21 Mar 2025 09:25:11 -0700</pubDate> <link>https://status.expo.dev/incidents/kgj6fmgkyvb2</link> <guid>https://status.expo.dev/incidents/kgj6fmgkyvb2</guid> </item> <item> <title>Elevated API errors and partially reduced availability</title> <description> <p><small>Mar <var data-var='date'>17</var>, <var data-var='time'>02:00</var> PDT</small><br><strong>Resolved</strong> - We're experienced an elevated level of API errors and partially reduced availability. The issues have been addressed, and everything should be back to the operational state.</p> </description> <pubDate>Mon, 17 Mar 2025 02:00:00 -0700</pubDate> <link>https://status.expo.dev/incidents/7vvtb4y80fjq</link> <guid>https://status.expo.dev/incidents/7vvtb4y80fjq</guid> </item> <item> <title>Classic Updates and older Snacks (SDK 49 and older) will be paused during a short maintenance period</title> <description> <p><small>Mar <var data-var='date'>15</var>, <var data-var='time'>20:11</var> PDT</small><br><strong>Completed</strong> - The scheduled maintenance is done and all affected services have been restored.</p><p><small>Mar <var data-var='date'>15</var>, <var data-var='time'>20:00</var> PDT</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'>11</var>, <var data-var='time'>12:38</var> PDT</small><br><strong>Scheduled</strong> - We will be performing database maintenance during off-peak hours. We expect the maintenance to take 10 to 15 minutes. During this time, old apps that check for classic updates will receive a response saying there is no update and they will launch with the latest update they already have and minimal impact to end users Older Snacks using SDK 49 and older will also be offline. After the maintenance period, all services will be restored to normal.</p> </description> <pubDate>Sat, 15 Mar 2025 20:11:05 -0700</pubDate> <maintenanceEndDate>Sat, 15 Mar 2025 20:15:00 -0700</maintenanceEndDate> <link>https://status.expo.dev/incidents/45xrsxd0qbjr</link> <guid>https://status.expo.dev/incidents/45xrsxd0qbjr</guid> </item> <item> <title>Increased error rates for iOS builds</title> <description> <p><small>Mar <var data-var='date'>10</var>, <var data-var='time'>11:19</var> PDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Mar <var data-var='date'>10</var>, <var data-var='time'>08:54</var> PDT</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Mar <var data-var='date'>10</var>, <var data-var='time'>08:40</var> PDT</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p> </description> <pubDate>Mon, 10 Mar 2025 11:19:28 -0700</pubDate> <link>https://status.expo.dev/incidents/2chsc6zwjlpl</link> <guid>https://status.expo.dev/incidents/2chsc6zwjlpl</guid> </item> <item> <title>Server API Downtime</title> <description> <p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>07:00</var> PST</small><br><strong>Resolved</strong> - At around 7 a.m. PST, our API servers experienced a widespread internal error, causing downtime for many of the services and tools that depend on them (expo.dev website, EAS CLI, etc.).This issue was resolved at 7:11 a.m. PST. We are investigating the root cause.</p> </description> <pubDate>Fri, 07 Mar 2025 07:00:00 -0800</pubDate> <link>https://status.expo.dev/incidents/5jfrycwlfk0h</link> <guid>https://status.expo.dev/incidents/5jfrycwlfk0h</guid> </item> <item> <title>Partial website outage</title> <description> <p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>14:30</var> PST</small><br><strong>Resolved</strong> - Users reported issues loading particular views on the website (expo.dev) due to errors from stale cache items causing requests to non-existent resources. We have addressed the problem, and users should now be able to load the website as expected.</p> </description> <pubDate>Tue, 04 Mar 2025 14:30:00 -0800</pubDate> <link>https://status.expo.dev/incidents/lktdg70lq3w5</link> <guid>https://status.expo.dev/incidents/lktdg70lq3w5</guid> </item> <item> <title>Increased Android queue times and scheduling issues</title> <description> <p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>09:10</var> PST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>08:24</var> PST</small><br><strong>Update</strong> - We are continuing to monitor for any further issues.</p><p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>08:07</var> PST</small><br><strong>Update</strong> - The underlying issue was resolved. We are monitoring queue times.</p><p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>08:03</var> PST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>07:28</var> PST</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>07:23</var> PST</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>07:12</var> PST</small><br><strong>Investigating</strong> - We are currently investigating the issue causing increased queue times for Android builds</p> </description> <pubDate>Tue, 04 Mar 2025 09:10:24 -0800</pubDate> <link>https://status.expo.dev/incidents/sshghxs29n7j</link> <guid>https://status.expo.dev/incidents/sshghxs29n7j</guid> </item> <item> <title>iOS Build Service Maintenance</title> <description> <p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>22:00</var> PST</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>20:00</var> PST</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>09:47</var> PST</small><br><strong>Scheduled</strong> - We will be performing infrastructure maintenance on our iOS build service. During this time, builds may queue for longer than usual.</p> </description> <pubDate>Mon, 03 Mar 2025 22:00:21 -0800</pubDate> <maintenanceEndDate>Mon, 03 Mar 2025 22:00:00 -0800</maintenanceEndDate> <link>https://status.expo.dev/incidents/j6f389ktwqyn</link> <guid>https://status.expo.dev/incidents/j6f389ktwqyn</guid> </item> <item> <title>Temporarily unable to generate new Apple Push Keys</title> <description> <p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>18:02</var> PST</small><br><strong>Resolved</strong> - This incident has been resolved. Please update to the latest EAS CLI version 15.0.12</p><p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>16:56</var> PST</small><br><strong>Identified</strong> - Creating new Apple Push Notification keys is currently failing due to recent changes in Apple鈥檚 API. The root cause has been identified and a fix is in progress. As a workaround, you can generate the push key manually in the Apple Developer portal and upload it to EAS.</p> </description> <pubDate>Fri, 21 Feb 2025 18:02:40 -0800</pubDate> <link>https://status.expo.dev/incidents/h4q6t2q1b5g4</link> <guid>https://status.expo.dev/incidents/h4q6t2q1b5g4</guid> </item> <item> <title>Internal networking issue with EAS Build workers</title> <description> <p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>11:09</var> PST</small><br><strong>Resolved</strong> - This caused many builds to fail during the incident period as a result of failed network requests, such as during Node package installation and CocoaPods installation, or cloning the VM image. All builds that failed between 11:09AM and 12:50PM were waived and will not count against usage.</p> </description> <pubDate>Wed, 05 Feb 2025 11:09:00 -0800</pubDate> <link>https://status.expo.dev/incidents/s92b99qx3rvq</link> <guid>https://status.expo.dev/incidents/s92b99qx3rvq</guid> </item> <item> <title>JitPack service outage impacting Android builds</title> <description> <p><small>Jan <var data-var='date'>24</var>, <var data-var='time'>04:04</var> PST</small><br><strong>Resolved</strong> - The issue was related to the removal of artifacts for the BlurView package from Jetpack (https://github.com/jitpack/jitpack.io/issues/6766#issuecomment-2591888851). The PR with the fix bumping the version of this dependency was already merged (https://github.com/expo/expo/pull/34012).</p><p><small>Jan <var data-var='date'>23</var>, <var data-var='time'>07:56</var> PST</small><br><strong>Monitoring</strong> - We are aware of ongoing issues with JitPack services (https://status.jitpack.io/) that may affect Android builds. These upstream issues could lead to build failures or delays. Our team is monitoring the situation closely and will provide updates as we learn more.</p> </description> <pubDate>Fri, 24 Jan 2025 04:04:19 -0800</pubDate> <link>https://status.expo.dev/incidents/dv7l3k5ynxly</link> <guid>https://status.expo.dev/incidents/dv7l3k5ynxly</guid> </item> <item> <title>Higher Android build failure rate</title> <description> <p><small>Dec <var data-var='date'>19</var>, <var data-var='time'>04:52</var> PST</small><br><strong>Resolved</strong> - We reenabled the Maven cache to overcome the rate-limiting issue and success/error rates for Android builds are back to normal.</p><p><small>Dec <var data-var='date'>19</var>, <var data-var='time'>04:39</var> PST</small><br><strong>Update</strong> - Some Android builds started to fail with the 429 error code during the "Run Gradle" build phase. We are working towards mitigating this issue.</p><p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>15:17</var> PST</small><br><strong>Identified</strong> - Some libraries, like expo-blur and expo-camera, depend on a library that is hosted on JitPack, which is currently experiencing an outage. If you are using one of these libraries in your project, your build may fail on Android.</p> </description> <pubDate>Thu, 19 Dec 2024 04:52:53 -0800</pubDate> <link>https://status.expo.dev/incidents/qgs5zvrvffds</link> <guid>https://status.expo.dev/incidents/qgs5zvrvffds</guid> </item> <item> <title>EAS outage</title> <description> <p><small>Nov <var data-var='date'>25</var>, <var data-var='time'>16:30</var> PST</small><br><strong>Resolved</strong> - We observed a higher than average database load due to a SQL migration that caused other database queries to fail. The issue was identified, a fix was implemented and all services are once again responsive.</p><p><small>Nov <var data-var='date'>25</var>, <var data-var='time'>16:30</var> PST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Nov <var data-var='date'>25</var>, <var data-var='time'>15:46</var> PST</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p> </description> <pubDate>Mon, 25 Nov 2024 16:30:54 -0800</pubDate> <link>https://status.expo.dev/incidents/03g8t6xnl5cc</link> <guid>https://status.expo.dev/incidents/03g8t6xnl5cc</guid> </item> <item> <title>Partial unavailability of expo.dev and EAS Build</title> <description> <p><small>Nov <var data-var='date'>21</var>, <var data-var='time'>02:00</var> PST</small><br><strong>Resolved</strong> - Between 02:00 and 02:21 PST we observed a higher than average database load due to a migration. The issue was identified, a fix was implemented and all services are once again responsive.</p> </description> <pubDate>Thu, 21 Nov 2024 02:00:00 -0800</pubDate> <link>https://status.expo.dev/incidents/5q5fj05p37ry</link> <guid>https://status.expo.dev/incidents/5q5fj05p37ry</guid> </item> <item> <title>Degraded performance due to higher than average database load</title> <description> <p><small>Nov <var data-var='date'>18</var>, <var data-var='time'>15:31</var> PST</small><br><strong>Resolved</strong> - We have implemented a fix for the database, and all services are responsive. We will follow-up with other fixes to maintain the stability.</p><p><small>Nov <var data-var='date'>18</var>, <var data-var='time'>15:23</var> PST</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p><p><small>Nov <var data-var='date'>18</var>, <var data-var='time'>15:11</var> PST</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Nov <var data-var='date'>18</var>, <var data-var='time'>15:10</var> PST</small><br><strong>Update</strong> - We are observing a higher-than-average database load that is causing availability issues for our APIs. Unfortunately, this is causing an extremely high latency, which results in unresponsive services on the website and our CLI tooling. We are investigating the cause and are working on a fix.</p><p><small>Nov <var data-var='date'>18</var>, <var data-var='time'>15:07</var> PST</small><br><strong>Investigating</strong> - We are observing a higher-than-average database load that is causing availability issues for our APIs. This affects using our website, as well as submitting and processing builds and submissions.</p> </description> <pubDate>Mon, 18 Nov 2024 15:31:36 -0800</pubDate> <link>https://status.expo.dev/incidents/qlm7ywdjw8pb</link> <guid>https://status.expo.dev/incidents/qlm7ywdjw8pb</guid> </item> <item> <title>Android Builds erroring due to rate limit hit on a 3rd party repository</title> <description> <p><small>Nov <var data-var='date'> 7</var>, <var data-var='time'>08:37</var> PST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Nov <var data-var='date'> 7</var>, <var data-var='time'>08:26</var> PST</small><br><strong>Monitoring</strong> - We've added failing 3rd party repository to our internal Maven proxy cache. Things should be getting back to normal.</p><p><small>Nov <var data-var='date'> 7</var>, <var data-var='time'>07:42</var> PST</small><br><strong>Identified</strong> - We're working on bringing back Android builds. We'll waive charges for failed Android builds for the period of the outage. Sorry for the inconvenience.</p> </description> <pubDate>Thu, 07 Nov 2024 08:37:07 -0800</pubDate> <link>https://status.expo.dev/incidents/zh7y81f3g9kb</link> <guid>https://status.expo.dev/incidents/zh7y81f3g9kb</guid> </item> <item> <title>Apple Developer authentication services through EAS CLI may be unavailable for some users</title> <description> <p><small>Oct <var data-var='date'>19</var>, <var data-var='time'>11:47</var> PDT</small><br><strong>Resolved</strong> - The Apple authentication fix in the latest eas-cli version (12.5.4) has been confirmed by multiple external people. If you are running into this issue, upgrade your eas-cli version - or open a new issue report on https://github.com/expo/eas-cli/issues.<br /><br />For the latest information see GitHub: https://github.com/expo/eas-cli/issues/2639</p><p><small>Oct <var data-var='date'>19</var>, <var data-var='time'>11:35</var> PDT</small><br><strong>Monitoring</strong> - Upgrade to `eas-cli@12.5.4`, which contains a fix for the Apple authentication issue. We will monitor the rollout until we are confident the issue is resolved.</p><p><small>Oct <var data-var='date'>19</var>, <var data-var='time'>11:04</var> PDT</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p><p><small>Oct <var data-var='date'>18</var>, <var data-var='time'>18:51</var> PDT</small><br><strong>Investigating</strong> - Public Apple Developer authentication API has changed, impacting automation tools like EAS CLI. We are currently investigating the issue. You can work around it by running builds with the `--non-interactive` flag, in order to skip authenticating and re-use existing app signing credentials. Follow along with updates on GitHub: https://github.com/expo/eas-cli/issues/2639</p> </description> <pubDate>Sat, 19 Oct 2024 11:47:19 -0700</pubDate> <link>https://status.expo.dev/incidents/t3cwh0l0x5qd</link> <guid>https://status.expo.dev/incidents/t3cwh0l0x5qd</guid> </item> <item> <title>EAS Build (iOS) cannot install the latest version of Node.js released today</title> <description> <p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>01:02</var> PDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>20:25</var> PDT</small><br><strong>Investigating</strong> - You may get an error message when attempting to install Node 20.15.1 and 22.4.1 like this:<br /><br />Version '20.15.1' not found - try `nvm ls-remote` to browse available versions.<br />Failed to install Node.js v20.15.1<br /><br />We are working on this and as a temporary workaround, please use the prior release of Node: 20.15.0 or 22.4.0.</p> </description> <pubDate>Tue, 09 Jul 2024 01:02:06 -0700</pubDate> <link>https://status.expo.dev/incidents/d7g4msjkbdmr</link> <guid>https://status.expo.dev/incidents/d7g4msjkbdmr</guid> </item> <item> <title>Broken artifacts for EAS builds triggered between ~8:34 AM GMT and ~10 AM GMT</title> <description> <p><small>Jun <var data-var='date'>25</var>, <var data-var='time'>23:30</var> PDT</small><br><strong>Resolved</strong> - The faulty deployment introduced a bug that caused build artifacts to not be uploaded correctly to storage buckets.<br /><br />Developers trying to download the artifacts of affected builds could see an error like "The specified key does not exist. No such object: ..."<br /><br /><br />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)"<br /><br />The issue was identified by the Expo team and the deployment was reverted at around 10 AM GMT. <br /><br />The charges for all of the broken builds were waived.</p> </description> <pubDate>Tue, 25 Jun 2024 23:30:00 -0700</pubDate> <link>https://status.expo.dev/incidents/qkymcrnj81fy</link> <guid>https://status.expo.dev/incidents/qkymcrnj81fy</guid> </item> <item> <title>Elevated builds errors</title> <description> <p><small>Jun <var data-var='date'>24</var>, <var data-var='time'>12:40</var> PDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jun <var data-var='date'>24</var>, <var data-var='time'>08:38</var> PDT</small><br><strong>Identified</strong> - We're experiencing an elevated level of build errors and are currently looking into the issue. It appears to be caused by a partial GCP outage. We're monitoring the issue.</p> </description> <pubDate>Mon, 24 Jun 2024 12:40:50 -0700</pubDate> <link>https://status.expo.dev/incidents/3479qfsqv0kw</link> <guid>https://status.expo.dev/incidents/3479qfsqv0kw</guid> </item> <item> <title>Elevated builds errors</title> <description> <p><small>Jun <var data-var='date'>24</var>, <var data-var='time'>03:16</var> PDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jun <var data-var='date'>23</var>, <var data-var='time'>20:50</var> PDT</small><br><strong>Identified</strong> - We're experiencing an elevated level of builds errors and are currently looking into the issue. It appears to be caused by a partial GCP outage. We're monitoring the issue.</p> </description> <pubDate>Mon, 24 Jun 2024 03:16:47 -0700</pubDate> <link>https://status.expo.dev/incidents/psbfdmkp04d8</link> <guid>https://status.expo.dev/incidents/psbfdmkp04d8</guid> </item> <item> <title>Elevated builds errors</title> <description> <p><small>Jun <var data-var='date'>23</var>, <var data-var='time'>08:45</var> PDT</small><br><strong>Resolved</strong> - Once again this seems to be resolved for good. Third time鈥檚 a charm!</p><p><small>Jun <var data-var='date'>23</var>, <var data-var='time'>07:46</var> PDT</small><br><strong>Identified</strong> - We're yet again experiencing an elevated level of builds errors and are currently looking into the issue. The underlying issue remains to be a partial GCP outage. We're monitoring the issue.</p> </description> <pubDate>Sun, 23 Jun 2024 08:45:23 -0700</pubDate> <link>https://status.expo.dev/incidents/1c00hg3yzck9</link> <guid>https://status.expo.dev/incidents/1c00hg3yzck9</guid> </item> <item> <title>Elevated builds errors</title> <description> <p><small>Jun <var data-var='date'>22</var>, <var data-var='time'>22:30</var> PDT</small><br><strong>Resolved</strong> - The errors are no longer happening. Happy Sunday!</p><p><small>Jun <var data-var='date'>22</var>, <var data-var='time'>21:23</var> PDT</small><br><strong>Identified</strong> - We're experiencing an elevated level of builds errors and are currently looking into the issue. It appears to be caused by a partial GCP outage. We're monitoring the issue.</p> </description> <pubDate>Sat, 22 Jun 2024 22:30:50 -0700</pubDate> <link>https://status.expo.dev/incidents/yztp810ygg22</link> <guid>https://status.expo.dev/incidents/yztp810ygg22</guid> </item> <item> <title>Elevated builds errors</title> <description> <p><small>Jun <var data-var='date'>22</var>, <var data-var='time'>13:58</var> PDT</small><br><strong>Resolved</strong> - All is good. Keep on building!</p><p><small>Jun <var data-var='date'>22</var>, <var data-var='time'>07:58</var> PDT</small><br><strong>Monitoring</strong> - Errors have stopped, we're hopeful for good. We'll keep an eye on it for a bit.</p><p><small>Jun <var data-var='date'>22</var>, <var data-var='time'>07:00</var> PDT</small><br><strong>Identified</strong> - We're experiencing an elevated level of builds errors and are currently looking into the issue. It appears to be caused by a partial GCP outage. We're monitoring the issue.</p> </description> <pubDate>Sat, 22 Jun 2024 13:58:10 -0700</pubDate> <link>https://status.expo.dev/incidents/6ddl92blxp0b</link> <guid>https://status.expo.dev/incidents/6ddl92blxp0b</guid> </item> <item> <title>Elevated Android builds errors</title> <description> <p><small>May <var data-var='date'>16</var>, <var data-var='time'>17:59</var> PDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>May <var data-var='date'>16</var>, <var data-var='time'>16:53</var> PDT</small><br><strong>Monitoring</strong> - The issue seems to be fixed on the GCP side, the error metrics are recovering</p><p><small>May <var data-var='date'>16</var>, <var data-var='time'>16:30</var> PDT</small><br><strong>Identified</strong> - We're experiencing elevated levels of Android builds errors. The issue seems to be caused by an underlying GCP outage: https://status.cloud.google.com.</p> </description> <pubDate>Thu, 16 May 2024 17:59:16 -0700</pubDate> <link>https://status.expo.dev/incidents/y1tg20h95mtq</link> <guid>https://status.expo.dev/incidents/y1tg20h95mtq</guid> </item> </channel> </rss>