Vendor Status Watch

← all vendors

Semaphore status history

Current state: operational — “All Systems Operational” per http://status.semaphoreci.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

10incidents, last 30 days
16incidents, last 90 days
45incidents on record
Incidents per week, last 12 weeks:

How long do Semaphore incidents last?

2.4 hmedian incident duration45 measured
7.8 h90th percentile1 in 10 ran longer
102 minmedian, major/critical only11 incidents

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)

StartedIncidentStatusImpactDuration
2026-09-15 14:45 UTCDelays in job processingresolvedminor2 h 01 min
2026-09-02 16:08 UTCPeriodic authentication failure with GitHub repositoriesresolvedminor24 h 32 min
2026-09-02 11:17 UTCPeriodic authentication failure with GitHub repositoriesresolvedminor3 h 59 min
2026-08-31 12:06 UTCDelays in job processingresolvedcritical10 h 04 min
2026-08-28 19:17 UTCDelays in job processingresolvedminor1 h 52 min
2026-08-27 20:09 UTCDelays in Job Processingresolvedmajor52 min
2026-08-27 18:43 UTCPlatform Outageresolvedcritical47 min
2026-08-25 08:35 UTCDegraded performance on r1-standard machinesresolvedminor6 h 11 min
2026-08-21 19:14 UTCIssues with Bitbucket integrationresolvedmajor1 h 33 min
2026-08-18 15:07 UTCDelays in job processing - F1 machinesresolvedminor2 h 40 min
2026-08-04 10:38 UTCBitbucket integration may currently be experiencing issuesresolvedmajor1 h 25 min
2026-07-23 00:35 UTCDelays in job processingresolvedminor1 h 43 min
2026-07-21 08:36 UTCSome jobs may have issues authenticating with GitHubresolvedmajor5 h 10 min
2026-07-17 10:32 UTCSome features may currently be unresponsiveresolvedmajor2 h 53 min
2026-07-17 00:21 UTCDelays in job processingresolvedminor44 min
2026-06-24 21:01 UTCElevated error ratesresolvedminor24 min
2026-06-10 15:12 UTCElevated Error Ratesresolvedminor1 h 09 min
2026-05-20 08:44 UTCDelays when checking out GitHub repos via SSHresolvedminor6 h 47 min
2026-05-19 10:00 UTCDelays when checking out GitHub repos via SSHresolvedminor5 h 42 min
2026-03-12 15:55 UTCDelays in job processingresolvedminor1 h 49 min
2026-03-11 16:28 UTCDelays in job processingresolvedminor1 h 14 min
2026-03-08 15:21 UTCDelays in job processingresolvedminor3 h 30 min
2026-03-03 17:06 UTCDelays in job processingresolvedminor59 min
2026-02-24 08:49 UTCJobs Not Starting and Processing Delaysresolvedmajor1 h 42 min
2026-02-20 15:56 UTCDelays in job processingresolvedminor2 h 46 min
2026-02-18 16:13 UTCDelays in job processingresolvedminor4 h 27 min
2026-02-17 16:32 UTCDelays in job processingresolvedminor1 h 46 min
2026-02-05 16:28 UTCDelays in job processingresolvedminor1 h 00 min
2026-02-04 16:38 UTCDelays in job processingresolvedminor1 h 32 min
2026-02-03 18:06 UTCDelays in Job Processingresolvedminor1 h 17 min
2026-02-03 15:46 UTCDelivering webhooks delays between Github and Semaphoreresolvedminor4 h 03 min
2026-01-27 15:34 UTCDelays in job processing on Semaphoreresolvedminor3 h 36 min
2025-11-12 14:55 UTCNetwork connectivity issues towards us-eastresolvedminor3 h 14 min
2025-11-06 16:51 UTCNetwork congestion on route to AWS ECR us-east regionresolvedminor14 h 24 min
2025-11-04 17:19 UTCNetwork congestion on route to AWS ECR us-east regionresolvedminor6 h 40 min
2025-10-29 11:38 UTCSlow job processingresolvedminor4 h 49 min
2025-10-21 08:58 UTCDelays in job completion on Semaphoreresolvedminor1 h 00 min
2025-10-20 08:44 UTCDocker Hub outage affecting image push/pulls in Semaphoreresolvedmajor16 h 15 min
2025-10-14 19:47 UTCNetwork congestion on route to AWS ECR us-east regionresolvedminor4 h 43 min
2025-10-02 18:48 UTCSlow job processing on e2 machine typesresolvedminor3 h 38 min
2025-09-17 01:02 UTCSlow job processing on C1 machine typesresolvedminor1 h 09 min
2025-09-12 09:41 UTCNew project initialization issuesresolvedmajor2 h 22 min
2025-09-04 17:12 UTCJob processing delays due to connectivity issues with GitHubresolvedmajor1 h 23 min
2025-08-28 17:46 UTCNetwork congestion on route to AWS ECR us-east regionresolvedminor7 h 48 min
2025-08-19 11:01 UTC"Plans & Billing" page unavailableresolvedminor1 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
}