Live / Incidents / Semaphore CI
Semaphore CI: Periodic authentication failure with GitHub repositories
Semaphore CI · semaphoreci.comImpact: minorResolved2026-09-03 12:45 UTC
Public — what happened
Summary
Our engineers are actively monitoring the intermittent issue affecting Git operations over HTTPS. We will share another update when more information becomes available.
To prevent affected builds from stalling while waiting for credentials, our engineering team has implemented fail-fast behavior. Affected builds will now fail promptly, reducing unnecessary runtime.
If the issue persists after rerunning the job, add the following command to the job before the affected Git operation to force Git to use HTTP/1.1:
git config --global http.version HTTP/1.1
Timeline
- Started — 2026-09-02 16:08 UTC
- Last update — 2026-09-03 12:45 UTC
- Resolved — 2026-09-03 16:45 UTC
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 →