Semaphore Outage History

Semaphore experienced slow communication between jobs and GitHub, causing delays when checking out repositories via SSH. The issue affected Semaphore 2.0 operations for 6.8 hours, with users needing to use a retry command workaround during the incident. The problem was resolved by deploying a network fix to re-route GitHub operations to healthier servers.

Semaphore 2.0 experienced delays when checking out GitHub repositories via SSH due to slow communication between jobs and GitHub. The issue affected users' ability to clone repositories during their CI/CD workflows for 5.8 hours. The problem was resolved after working with the upstream provider, with a temporary workaround provided using retry commands with timeouts during the incident.

Semaphore 2.0 experienced delays in job processing for 2 hours. The issue was identified and a fix was implemented, with monitoring confirming the resolution. The incident has been fully resolved.

Semaphore 2.0 experienced delays in job processing for 1.3 hours. The issue was identified and a fix was implemented, with the service returning to normal operation. The incident was resolved after monitoring confirmed the fix was successful.

Semaphore 2.0 experienced delays in job processing for 3.6 hours. The issue was identified and a fix was implemented, with monitoring confirming the resolution. The incident has been fully resolved.

Semaphore 2.0 experienced delays in job processing for approximately 1 hour. The issue was identified and a fix was implemented, with the service team monitoring the results. The incident was fully resolved after the fix proved effective.

Semaphore 2.0 experienced a major incident where jobs failed to start and processing delays occurred for 1.7 hours. The issue was identified and a fix was implemented, with the service returning to normal operation. The incident was fully resolved after monitoring confirmed the fix was successful.