Semaphore CI Outage History

49 incidents recorded over the last 365 days, 45 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Semaphore CI status100.00% uptime history

Every Recorded Semaphore CI Incident

Semaphore CI incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 29, 2026Delays in Job ProcessingThis incident has been resolved.1h 25mResolved
Oct 26, 2026Delays in Job ProcessingThis incident has been resolved.3h 14mResolved
Oct 26, 2026Delays in Job ProcessingThis incident has been resolved.2h 41mResolved
Oct 22, 2026Delays in Job ProcessingThis incident has been resolved.2h 15mResolved
Oct 21, 2026Delays in Job ProcessingThis incident has been resolved.3h 46mResolved
Oct 20, 2026Delays in jobs schedulingThis incident has been resolved.2h 1mResolved
Oct 14, 2026Delays in job processingThis incident has been resolved.2h 7mResolved
Oct 13, 2026Delays in job processingThis incident has been resolved.2h 56mResolved
Oct 13, 2026Intermittent network connectivity issuesThis incident has been resolved.8h 36mResolved
Sep 17, 2026Delays in job processingThis incident has been resolved.51 minResolved
Sep 17, 2026Intermittent cache connection errorsThis incident has been resolved.38 minResolved
Sep 15, 2026Delays in job processingThis incident has been resolved.2h 1mResolved
Sep 2, 2026Periodic authentication failure with GitHub repositoriesSemaphore is currently operating normally, which is why we’re marking this incident as resolved. GitHub confirmed that the behavior affecting unauthenticated Git operations is the result of an intentional change on…24h 32mResolved
Sep 2, 2026Periodic authentication failure with GitHub repositoriesThis incident has been resolved.3h 59mResolved
Aug 31, 2026Delays in job processingThis incident has been resolved.10h 4mResolved
Aug 28, 2026Delays in job processingThis incident has been resolved.1h 52mResolved
Aug 27, 2026Delays in Job ProcessingThis incident has been resolved.52 minResolved
Aug 27, 2026Platform OutageThis incident has been resolved.47 minResolved
Aug 25, 2026Degraded performance on r1-standard machinesThis incident has been resolved.6h 11mResolved
Aug 21, 2026Issues with Bitbucket integrationThis incident has been resolved.1h 33mResolved
Aug 18, 2026Delays in job processing - F1 machinesThis incident has been resolved.2h 40mResolved
Aug 15, 2026Scheduled Semaphore MaintenanceThe scheduled maintenance has been completed.170h 0mScheduled
Aug 4, 2026Bitbucket integration may currently be experiencing issuesThis incident has been resolved.1h 25mResolved
Jul 23, 2026Delays in job processingThis incident has been resolved.1h 43mResolved
Jul 21, 2026Some jobs may have issues authenticating with GitHubGitHub confirmed that the incident on their end has been resolved. You can review the GitHub update here: https://www.githubstatus.com/incidents/g40zcbvchny45h 10mResolved
Jul 17, 2026Some features may currently be unresponsiveThis incident has been resolved.2h 53mResolved
Jul 17, 2026Delays in job processingThis incident has been resolved.44 minResolved
Jun 24, 2026Elevated error ratesThis incident has been resolved.24 minResolved
Jun 10, 2026Elevated Error RatesThis incident has been resolved.1h 9mResolved
May 20, 2026Delays when checking out GitHub repos via SSHThis incident has been resolved.6h 47mResolved
May 19, 2026Delays when checking out GitHub repos via SSHThis incident has been resolved.5h 42mResolved
Mar 12, 2026Delays in job processingThis incident has been resolved.1h 49mResolved
Mar 11, 2026Delays in job processingThis incident has been resolved.1h 14mResolved
Mar 8, 2026Delays in job processingThis incident has been resolved.3h 30mResolved
Mar 3, 2026Delays in job processingThis incident has been resolved.59 minResolved
Feb 24, 2026Jobs Not Starting and Processing DelaysThis incident has been resolved.1h 42mResolved
Feb 20, 2026Delays in job processingThis incident has been resolved.2h 46mResolved
Feb 18, 2026Delays in job processingThis incident has been resolved.4h 27mResolved
Feb 17, 2026Delays in job processingThis incident has been resolved.1h 46mResolved
Feb 7, 2026Infrastructure maintenanceThe scheduled maintenance has been completed.2h 0mScheduled
Feb 5, 2026Delays in job processingThis incident has been resolved.1h 0mResolved
Feb 4, 2026Delays in job processingThis incident has been resolved.1h 32mResolved
Feb 3, 2026Delays in Job ProcessingThis incident has been resolved.1h 17mResolved
Feb 3, 2026Delivering webhooks delays between Github and SemaphoreThis incident has been resolved.4h 3mResolved
Feb 1, 2026Scheduled database maintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Jan 27, 2026Delays in job processing on SemaphoreThis incident has been resolved.3h 36mResolved
Jan 18, 2026Scheduled database server maintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Nov 12, 2025Network connectivity issues towards us-eastThis incident has been resolved.3h 14mResolved
Nov 6, 2025Network congestion on route to AWS ECR us-east regionWe have observed connection times recover and stay healthy for the affected regions.14h 24mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Semaphore CI incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Semaphore CI Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Semaphore CI acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Semaphore CI outage in this window ran 7d 2h, against a mean recovery of 6h 47m. If you depend on Semaphore CI in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.