July 9, 2026
14:10 to 16:05 Pacific
Elevated latency on readiness runs
ResolvedRuns took 40 to 70 seconds instead of the usual 12 to 20 for around two hours, caused by rate limiting at our primary model provider. The fallback chain routed the affected runs to a second model and no run failed. We have raised our committed throughput and added a routing alarm at the 30 second mark.