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
- Started — 2026-09-02 16:08 UTC
- Resolved — 2026-09-03 16:45 UTC · 24h 37m 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 37, 2026, our weekly internet health report.