Live / Semaphore CI / Incident
Semaphore CI: Delays in jobs scheduling
Semaphore CI · semaphoreci.comResolved2026-10-20 23:59 UTC
Public — what happened
Summary
Semaphore CI said that some jobs were being scheduled late, an issue it reported starting at 21:58 UTC on 2026-10-20. The company said it had already identified the problem at that point and was working on a fix. By 22:44 UTC it reported scheduling times starting to improve, though some delays remained, and by 23:10 UTC it said times were back to normal. Semaphore CI kept monitoring and marked the incident resolved at 23:59 UTC.
Affected
Semaphore
Timeline
- Started — 2026-10-20 21:58 UTC
- Identified — 2026-10-20 21:58 UTC (3 updates)
- Monitoring — 2026-10-20 23:10 UTC (2 updates)
- Resolved — 2026-10-20 23:59 UTC · 2h 01m 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 44, 2026, our weekly internet health report.