---
title: "Native build runners degraded"
description: "Resolved · Jul 22, 2026"
base_url: "https://status.capgo.app"
canonical: "https://status.capgo.app/events/report/2514"
homepage_url: "https://capgo.app"
---

# Native build runners degraded

[Status](/.md) › [Events](/events.md) › Native build runners degraded

Jul 22, 2026 · 1 month ago · 23 hours

## Updates

### + Resolved — Jul 23, 2:00 PM

Incident resolved: native build runners are healthy again.

Follow-ups underway so this class of failure recovers without a human in the loop: automatic detection when runners go offline or wait pressure stays high, automatic re-registration/reconfigure of runners, and guarded auto-capacity when the queue backs up. We are also adding auto-retry for transient CocoaPods CDN/HTTP2 failures.

Status: https://status.capgo.app

### x Monitoring — Jul 23, 10:00 AM

Runner capacity was restored and native builds are succeeding again for affected users. We are monitoring the queue and runner health.

### x Identified — Jul 22, 6:30 PM

Identified instability in our shared macOS native-build runner pool. Runners were dropping offline and recovery still required a manual reconfigure step, so capacity stayed low while many users retried at the same time and wait times grew.

### x Investigating — Jul 22, 3:00 PM

We are investigating reports of long waits for Capgo native builds (iOS/Android). Some jobs remained queued with no available runner, and some iOS builds failed on transient CocoaPods CDN/HTTP2 errors.

---

_Powered by [openstatus.dev](https://openstatus.dev)_