Live / Semaphore CI / Incident
Semaphore CI: Intermittent network connectivity issues
Semaphore CI · semaphoreci.comMinor incidentResolved2026-10-13 22:30 UTC
Public — what happened
Summary
Semaphore CI reported intermittent network connectivity problems starting at 13:53 UTC on October 13, 2026, which it rated as minor, including dropped connections and sluggish network speeds. The company said the trouble was probably tied to recent maintenance by its infrastructure provider, and later pinpointed unreliable connections between that provider's network and some Google services, which could disrupt artifact uploads and downloads and jobs relying on Google-hosted resources. Semaphore CI said it passed diagnostic details to the provider, reported at 21:45 UTC that connectivity was recovering, and marked the incident resolved at 22:30.
Affected
Semaphore
Timeline
- Started — 2026-10-13 13:53 UTC
- Investigating — 2026-10-13 13:53 UTC (2 updates)
- Identified — 2026-10-13 14:40 UTC (2 updates)
- Investigating — 2026-10-13 16:34 UTC (2 updates)
- Identified — 2026-10-13 18:31 UTC
- Monitoring — 2026-10-13 21:45 UTC
- Resolved — 2026-10-13 22:30 UTC · 8h 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 43, 2026, our weekly internet health report.