Live  /  Providers  /  Semaphore CI

Semaphore CI

semaphoreci.comNo open incidents

Independent assessment — SquidGrid is not affiliated with Semaphore CI. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

SaaS & business software · SquidGrid tracks Semaphore CI’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what Semaphore CI is reporting

Current & recent incidents

Resolved

Delays in job processing

Major impact · 2026-09-17 14:47 UTC

Resolved

Intermittent cache connection errors

Minor impact · 2026-09-17 13:56 UTC

Resolved

Delays in job processing

Minor impact · 2026-09-15 16:16 UTC

Resolved

Periodic authentication failure with GitHub repositories

Minor impact · 2026-09-03 12:45 UTC

Resolved

Periodic authentication failure with GitHub repositories

Minor impact · 2026-09-02 14:19 UTC

Resolved

Delays in job processing

Critical impact · 2026-08-31 21:44 UTC

Mirrored from the provider’s own published status. Times in UTC.

Independent path health

A status page tells you what Semaphore CI has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

Semaphore CI runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of Semaphore CI is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with Semaphore CI.