Capgo

Service availability and performance

Jul 22, 2026

1 month ago

Native build runners degraded

Resolved · July 23 at 2:00 PM (UTC) (in 23 hours)

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

Monitoring · July 23 at 10:00 AM (UTC) (4 hours earlier)

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

Identified · July 22 at 6:30 PM (UTC) (16 hours earlier)

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.

Investigating · July 22 at 3:00 PM (UTC) (4 hours earlier)

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.