Incidents | Limrun, Inc.

Android adb tunnels are returning 404

Wed, 05 Aug 2026 17:31:00 -0000

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=" 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

Wed, 05 Aug 2026 16:14:00 -0000

Android Debug Bridge (adb) tunnels started to return 404 or 401 to the clients.

us-east1 degraded

Tue, 16 Jun 2026 01:56:00 -0000

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

Mon, 15 Jun 2026 22:45:00 -0000

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

Thu, 07 May 2026 09:37:00 -0000

us-west1 is temporarily disabled the redirections to us-west2 are working as expected.

us-west1 is disabled

Wed, 06 May 2026 20:00:00 -0000

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

Wed, 25 Feb 2026 21:40:00 -0000

Our provider recovered from the network issue. API is back online.

API is degraded

Wed, 25 Feb 2026 21:11:00 -0000

Our upstream cloud provider is having network issues that are impacting our API.