Live  /  Semaphore CI  /  Incident

Semaphore CI: Periodic authentication failure with GitHub repositories

Semaphore CI · semaphoreci.comMinor incidentResolved2026-09-03 12:45 UTC
Public — what happened

Summary

Semaphore CI reported a minor issue in which builds working with GitHub repositories intermittently failed to authenticate when running Git commands over HTTPS, beginning on 2026-09-02 at 16:08 UTC. The company said it changed affected builds so they stop quickly instead of hanging while waiting for credentials, and it suggested that users who still see the problem after a rerun configure Git to use HTTP/1.1 before the failing step. Semaphore CI marked the cause as identified but did not describe it, and the incident was listed as resolved on 2026-09-03 at 16:45.

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 37, 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.