Live  /  Semaphore CI  /  Incident

Semaphore CI: Delays in Job Processing

Semaphore CI · semaphoreci.comMinor incidentResolved2026-10-27 02:54 UTC
Public — what happened

Summary

Semaphore CI reported a minor incident involving delays in job processing, which began at 23:40 UTC on 2026-10-26. The company said it identified the issue about half an hour later, and by 01:27 UTC on 2026-10-27 it said processing times had returned to normal. It then said the issue had been identified again at 02:05 UTC and that a fix was being put in place, and at 02:35 UTC it said the fix was in and being monitored. The incident was marked resolved at 02:54 UTC, and Semaphore CI did not describe a cause in its updates.

Affected

Semaphore

As listed on Semaphore CI’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 45, 2026, our weekly internet health report.

The full archive is on the Semaphore CI status & history page.

Related: Semaphore CI status & history. SquidGrid is not affiliated with Semaphore CI.