Live / Semaphore CI / Incident
Semaphore CI: Delays in job processing
Semaphore CI · semaphoreci.comMinor incidentResolved2026-10-14 17:17 UTC
Public — what happened
Summary
Semaphore CI reported a minor incident on October 14, 2026, in which jobs were slow to start, with the problem occurring as they were being set up to run. The company began looking into it at 15:10 UTC and said at 15:55 UTC that it had found the source of the problem, though it did not describe what that was. A fix was in place by 16:19 UTC, and after a period of watching the results, the incident was marked resolved at 17:17.
Affected
Semaphore
Timeline
- Started — 2026-10-14 15:10 UTC
- Investigating — 2026-10-14 15:10 UTC
- Identified — 2026-10-14 15:55 UTC
- Monitoring — 2026-10-14 16:19 UTC
- Resolved — 2026-10-14 17:17 UTC · 2h 08m 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.