Live / Semaphore CI / Incident
Semaphore CI: Periodic authentication failure with GitHub repositories
Semaphore CI · semaphoreci.comMinor incidentResolved2026-09-02 14:19 UTC
Public — what happened
Summary
Semaphore CI reported a minor incident on 2026-09-02, starting at 11:17 UTC, in which connections to GitHub repositories intermittently failed to authenticate. The company said a broader problem with HTTPS operations was behind it, affecting both Semaphore and its users, and pointed to a GitHub community discussion about it. Semaphore CI said the problem seemed to have eased and that it was still watching the situation, with the incident marked resolved at 15:18.
Timeline
- Started — 2026-09-02 11:17 UTC
- Resolved — 2026-09-02 15:18 UTC · 4h 01m 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.