Status updates | Limrun, Inc. Incidents and maintenance reported on status page for Limrun, Inc. https://status.limrun.com/ en Xcode 27 RC builds are failing https://status.limrun.com/incident/1063146 Sat, 12 Sep 2026 10:05:00 -0000 https://status.limrun.com/incident/1063146#bd2f7d2556c49c4b917bd84891c69fc16a4347a7c1ef898f665cdd987696e114 Incident After a rollout in production, we've seen increased rate of failures in builds done with Xcode 27 RC1. We reverted the release and degradation is resolved. The root cause seems to be that there is a behavioral change in the new Xcode 27 version and our integration tests were using a different beta version, which passed all the tests. Since then, the behavior change is accommodated and rolled out without any issues. Xcode 27 RC builds are failing https://status.limrun.com/incident/1063146 Sat, 12 Sep 2026 09:01:00 -0000 https://status.limrun.com/incident/1063146#709e645c6111feb1639f8cb123afed6acc29500632ff7f4d82e8ab09dc24d9ce Incident After a rollout in production, we've seen increased rate of failures in builds done with Xcode 27 RC1. We reverted the release and degradation is resolved. The root cause seems to be that there is a behavioral change in the new Xcode 27 version and our integration tests were using a different beta version, which passed all the tests. Since then, the behavior change is accommodated and rolled out without any issues. Android adb tunnels are returning 404 https://status.limrun.com/incident/997197 Wed, 05 Aug 2026 17:31:00 -0000 https://status.limrun.com/incident/997197#898b03dbfc73efd07d82675e3ad12043f915091f05c0436980112bfd485736ef Incident We had rolled out a change for internal authentication of our services when they reach out to the customer workloads during assignment. As part of that rollout, the router which forwards all incoming requests to the customer workloads, including adb traffic, stopped stripping the. "?token=<instance token>" query parameter from the requests as part of cleanup. However, the HTTP library used to front that request started to fail to pair the requests with the correct path as it was not configured to do so, e.g. it was expecting exact match. Because this was a staged rollout involving multiple components to make sure we enable the auth once all pieces are in place, it did not surface itself in staging where all components were already deployed which contained the fix for this issue. So, it was effectively failure of our rollout ordering that made us blind to the problem in staging and it made it to the production. We've reverted all changes during the incident but it took more than we expected to untangle all the pieces. Once rollback is completed, all regions started to recover as the old versions of Android were deployed. We then applied the same rollout plan with fallbacks. The rollout was successful and it didn't need to fall back, later on we cleared those fallbacks and concluded the incident. Android adb tunnels are returning 404 https://status.limrun.com/incident/997197 Wed, 05 Aug 2026 16:14:00 -0000 https://status.limrun.com/incident/997197#b3e27f61ef8957d5ccf9e2331d9e0f0e012624c826a218e970de5ce8d7d43260 Incident Android Debug Bridge (adb) tunnels started to return 404 or 401 to the clients. us-east1 degraded https://status.limrun.com/incident/925147 Tue, 16 Jun 2026 01:56:00 -0000 https://status.limrun.com/incident/925147#282a2a0056aa79d826929d3883eed44300d36ef729daedf4c868dbfe57bc8499 Incident A subset of Android instances in us-east1 had an issue where the connections couldn't be established due to DNS of the underlying hosts flapping to internal IPs. The incident took place for 3 hours, starting at June 15, 2026 3:45PM PST and fixed at 6:50PM PST. us-east1 degraded https://status.limrun.com/incident/925147 Mon, 15 Jun 2026 22:45:00 -0000 https://status.limrun.com/incident/925147#424e4897e78b91c67eb46ee2388b4daf92a09a163680fb497e0a18a950ff8eb1 Incident A subset of Android instances in us-east1 had an issue where the connections couldn't be established due to DNS of the underlying hosts flapping to internal IPs. us-west1 is disabled https://status.limrun.com/incident/890052 Thu, 07 May 2026 09:37:00 -0000 https://status.limrun.com/incident/890052#108e2f14f82091e5beb33535241cf1468ed2bc9547a7a8c85966ec346064b60c Incident us-west1 is temporarily disabled the redirections to us-west2 are working as expected. us-west1 is disabled https://status.limrun.com/incident/890052 Wed, 06 May 2026 20:00:00 -0000 https://status.limrun.com/incident/890052#f6fe8d5f6ed8b2d9b8c5687072759c4e1843b40085d1262ee329dc5d1a12a6eb Incident No instances will be created on us-west1 at this time. All pinned and non-pinned requests are redirected to us-west2. API is degraded https://status.limrun.com/incident/846996 Wed, 25 Feb 2026 21:40:00 -0000 https://status.limrun.com/incident/846996#3a86a95d52b553128a602e3ff0f5613647a30d8d78d79d158107ed1cd0acbf47 Incident Our provider recovered from the network issue. API is back online. API is degraded https://status.limrun.com/incident/846996 Wed, 25 Feb 2026 21:11:00 -0000 https://status.limrun.com/incident/846996#8ec0ed6436eb65c4e98460b7e29d3ee6eca1aab7eb986238475f4cde55c84d5d Incident Our upstream cloud provider is having network issues that are impacting our API.