Live / Semaphore CI / Incident
Semaphore CI: Delays in job processing
Semaphore CI · semaphoreci.comMinor incidentResolved2026-10-13 17:43 UTC
Public — what happened
Summary
Semaphore CI reported a minor incident involving slow job processing, which it began investigating at 15:16 UTC on 2026-10-13. The company did not say which customers were affected or name a cause. By 16:47 UTC it said processing times were getting better, though some slowdowns could continue. At 17:43 UTC Semaphore CI said it had put a fix in place and was watching the results, and the incident had not yet been marked resolved.
Affected
Semaphore
Timeline
- Started — 2026-10-13 15:16 UTC
- Investigating — 2026-10-13 15:16 UTC (2 updates)
- Identified — 2026-10-13 16:47 UTC
- Monitoring — 2026-10-13 17:43 UTC
- Resolved — 2026-10-13 17:43 UTC · 2h 27m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Semaphore CI against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Semaphore CI: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Semaphore CI report →
More from Semaphore CI
Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.