Semaphore CI Status

Resolved: This incident has been resolved.

Identified: The issue has been identified and a fix is being implemented.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: The issue has been identified and a fix is being implemented.

Resolved: This incident has been resolved.

Monitoring: GitHub has posted an update indicating recovery of the aforementioned issue. We continue monitoring Semaphore closely as things stabilize.

(GitHub Status: https://www.githubstatus.com/incidents/f314nlctbfs5)

Identified: Webhook delivery delays between GitHub and Semaphore appear to be caused by degraded performance on GitHub’s side. GitHub is currently reporting an active incident that appears related. We are monitoring the situation closely and will provide updates as GitHub resolves the issue.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Monitoring: We’re seeing considerable improvement in internal performance metrics, and we will continue monitoring until conditions fully stabilize.

Investigating: Webhook delivery delays from GitHub led to a backlog of workflows being triggered all at once as delivery resumes. This caused a temporary spike in demand for some Semaphore machines.

We are actively working to reduce the impact and restore normal capacity. We continue monitoring both GitHub’s incident and Semaphore infrastructure closely, and we will provide further updates as conditions stabilize.