Semaphore status history
Current state: operational — “All Systems Operational” per http://status.semaphoreci.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Semaphore incidents last?
From 45 incidents with a vendor-posted start and resolve time. Longest on record: Periodic authentication failure with GitHub repositories — 24.5 h (2026-09-02 16:08 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (45)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-15 14:45 UTC | Delays in job processing | resolved | minor | 2 h 01 min |
| 2026-09-02 16:08 UTC | Periodic authentication failure with GitHub repositories | resolved | minor | 24 h 32 min |
| 2026-09-02 11:17 UTC | Periodic authentication failure with GitHub repositories | resolved | minor | 3 h 59 min |
| 2026-08-31 12:06 UTC | Delays in job processing | resolved | critical | 10 h 04 min |
| 2026-08-28 19:17 UTC | Delays in job processing | resolved | minor | 1 h 52 min |
| 2026-08-27 20:09 UTC | Delays in Job Processing | resolved | major | 52 min |
| 2026-08-27 18:43 UTC | Platform Outage | resolved | critical | 47 min |
| 2026-08-25 08:35 UTC | Degraded performance on r1-standard machines | resolved | minor | 6 h 11 min |
| 2026-08-21 19:14 UTC | Issues with Bitbucket integration | resolved | major | 1 h 33 min |
| 2026-08-18 15:07 UTC | Delays in job processing - F1 machines | resolved | minor | 2 h 40 min |
| 2026-08-04 10:38 UTC | Bitbucket integration may currently be experiencing issues | resolved | major | 1 h 25 min |
| 2026-07-23 00:35 UTC | Delays in job processing | resolved | minor | 1 h 43 min |
| 2026-07-21 08:36 UTC | Some jobs may have issues authenticating with GitHub | resolved | major | 5 h 10 min |
| 2026-07-17 10:32 UTC | Some features may currently be unresponsive | resolved | major | 2 h 53 min |
| 2026-07-17 00:21 UTC | Delays in job processing | resolved | minor | 44 min |
| 2026-06-24 21:01 UTC | Elevated error rates | resolved | minor | 24 min |
| 2026-06-10 15:12 UTC | Elevated Error Rates | resolved | minor | 1 h 09 min |
| 2026-05-20 08:44 UTC | Delays when checking out GitHub repos via SSH | resolved | minor | 6 h 47 min |
| 2026-05-19 10:00 UTC | Delays when checking out GitHub repos via SSH | resolved | minor | 5 h 42 min |
| 2026-03-12 15:55 UTC | Delays in job processing | resolved | minor | 1 h 49 min |
| 2026-03-11 16:28 UTC | Delays in job processing | resolved | minor | 1 h 14 min |
| 2026-03-08 15:21 UTC | Delays in job processing | resolved | minor | 3 h 30 min |
| 2026-03-03 17:06 UTC | Delays in job processing | resolved | minor | 59 min |
| 2026-02-24 08:49 UTC | Jobs Not Starting and Processing Delays | resolved | major | 1 h 42 min |
| 2026-02-20 15:56 UTC | Delays in job processing | resolved | minor | 2 h 46 min |
| 2026-02-18 16:13 UTC | Delays in job processing | resolved | minor | 4 h 27 min |
| 2026-02-17 16:32 UTC | Delays in job processing | resolved | minor | 1 h 46 min |
| 2026-02-05 16:28 UTC | Delays in job processing | resolved | minor | 1 h 00 min |
| 2026-02-04 16:38 UTC | Delays in job processing | resolved | minor | 1 h 32 min |
| 2026-02-03 18:06 UTC | Delays in Job Processing | resolved | minor | 1 h 17 min |
| 2026-02-03 15:46 UTC | Delivering webhooks delays between Github and Semaphore | resolved | minor | 4 h 03 min |
| 2026-01-27 15:34 UTC | Delays in job processing on Semaphore | resolved | minor | 3 h 36 min |
| 2025-11-12 14:55 UTC | Network connectivity issues towards us-east | resolved | minor | 3 h 14 min |
| 2025-11-06 16:51 UTC | Network congestion on route to AWS ECR us-east region | resolved | minor | 14 h 24 min |
| 2025-11-04 17:19 UTC | Network congestion on route to AWS ECR us-east region | resolved | minor | 6 h 40 min |
| 2025-10-29 11:38 UTC | Slow job processing | resolved | minor | 4 h 49 min |
| 2025-10-21 08:58 UTC | Delays in job completion on Semaphore | resolved | minor | 1 h 00 min |
| 2025-10-20 08:44 UTC | Docker Hub outage affecting image push/pulls in Semaphore | resolved | major | 16 h 15 min |
| 2025-10-14 19:47 UTC | Network congestion on route to AWS ECR us-east region | resolved | minor | 4 h 43 min |
| 2025-10-02 18:48 UTC | Slow job processing on e2 machine types | resolved | minor | 3 h 38 min |
| 2025-09-17 01:02 UTC | Slow job processing on C1 machine types | resolved | minor | 1 h 09 min |
| 2025-09-12 09:41 UTC | New project initialization issues | resolved | major | 2 h 22 min |
| 2025-09-04 17:12 UTC | Job processing delays due to connectivity issues with GitHub | resolved | major | 1 h 23 min |
| 2025-08-28 17:46 UTC | Network congestion on route to AWS ECR us-east region | resolved | minor | 7 h 48 min |
| 2025-08-19 11:01 UTC | "Plans & Billing" page unavailable | resolved | minor | 1 h 11 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Semaphore with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"semaphore"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}