Live status & reliability report

Semaphore status, outages & reliability

#9 of 11 code hosting & CI platformsOperational

Semaphore is a hosted CI/CD service, with an open-source community edition, that runs pipelines on Linux, macOS and Docker machines.

Data updated Nov 1, 2026 · score recalculated

Over the last 90 days Semaphore had 98.96% effective uptime across 21 status page incidents (5 partial or major outages), resolving them in 4h 10m on average.

55.7/100Reliability scoreVisit Semaphore ↗

Is Semaphore down right now?

No, Semaphore is up and running.

  • Semaphore's status page reports all systems operational. Checked .
  • All 3 Semaphore pages we check are responding. Checked .

Official Semaphore status page ↗

Uptime (90d)98.96%22h 26m weighted downtime
Incidents (90d)214.3 per 30 days
Major / partial outages5
Avg time to resolve4h 10m
Outages we detected0by our independent probes

90-day uptime

Aug 5, 2026 – Aug 17, 2026: no incidentsAug 18, 2026: 98.32% uptime, 1 incident (Degraded performance)Aug 19, 2026 – Aug 20, 2026: no incidentsAug 21, 2026: 96.75% uptime, 1 incident (Partial outage)Aug 22, 2026 – Aug 24, 2026: no incidentsAug 25, 2026: 96.12% uptime, 1 incident (Degraded performance)Aug 26, 2026: no incidentsAug 27, 2026: 94.88% uptime, 2 incidents (Major outage)Aug 28, 2026: 98.82% uptime, 1 incident (Degraded performance)Aug 29, 2026 – Aug 30, 2026: no incidentsAug 31, 2026: 57.98% uptime, 1 incident (Major outage)Sep 1, 2026: no incidentsSep 2, 2026: 92.59% uptime, 2 incidents (Degraded performance)Sep 3, 2026: 89.57% uptime, 1 incident (Degraded performance)Sep 4, 2026 – Sep 14, 2026: no incidentsSep 15, 2026: 98.73% uptime, 1 incident (Degraded performance)Sep 16, 2026: no incidentsSep 17, 2026: 97.79% uptime, 2 incidents (Partial outage)Sep 18, 2026 – Oct 12, 2026: no incidentsOct 13, 2026: 94.61% uptime, 2 incidents (Degraded performance)Oct 14, 2026: 98.66% uptime, 1 incident (Degraded performance)Oct 15, 2026 – Oct 20, 2026: no incidentsOct 21, 2026: 97.64% uptime, 1 incident (Degraded performance)Oct 22, 2026: 98.59% uptime, 1 incident (Degraded performance)Oct 23, 2026 – Oct 25, 2026: no incidentsOct 26, 2026: 98.11% uptime, 2 incidents (Degraded performance)Oct 27, 2026: 98.18% uptime, 1 incident (Degraded performance)Oct 28, 2026: no incidentsOct 29, 2026: 99.28% uptime, 1 incident (Degraded performance)Oct 30, 2026: 99.82% uptime, 1 incident (Degraded performance)Oct 31, 2026 – Nov 2, 2026: no incidents
90 days ago98.961% average daily uptimeToday
  • No incidents
  • Degraded
  • Partial outage
  • Major outage
  • No data

Key facts about Semaphore's reliability

  • Over the past 12 months, Semaphore published 46 incidents on its status page, 9 of them partial or major outages.
  • Its longest outage on record in that time was “Delays in job processing” on Aug 31, 2026, which lasted 10h 5m.
  • The part of Semaphore most often affected was Semaphore (46 of 46 incidents).
  • Semaphore reported 21 incidents in the last 90 days, up from 9 in the 90 days before.
  • Incidents most often began on a Tuesday (16 of 46, UTC).
  • Semaphore's 90-day uptime of 98.96% is below the average for code hosting & CI platforms (99.29%).
  • It resolves incidents more slowly than the typical code hosting & CI platform: 4h 10m on average, against a median of 2h 21m.

Score breakdown

Uptime · 40% weight
37
98.962% effective uptime
Incident frequency · 20% weight
35
4.25 weighted incidents per 30 days
Time to resolve · 20% weight
71
4h 10m average
Transparency · 20% weight
100
No unreported outages detected

How the score is calculated →

Incidents per month

036912Dec1 degraded performance incident1Jan ’261 partial outage incident7 degraded performance incidents8Feb4 degraded performance incidents4MarApr2 degraded performance incidents2May2 degraded performance incidents2Jun2 partial outage incidents2 degraded performance incidents4Jul2 major outage incidents3 partial outage incidents3 degraded performance incidents8Aug1 partial outage incident4 degraded performance incidents5Sep8 degraded performance incidents1 informational incident9OctNov
  • Major outage
  • Partial outage
  • Degraded
  • Informational

Response time

Daily average response time of Semaphore's public pages, measured by our probes.

0ms270ms539msNov 1, 2026: 490msNov 2, 2026: 469msNov 1, 2026Nov 2, 2026

Score trend

Daily reliability score (rolling 90-day window).

050100Nov 1, 2026: 54.9Nov 2, 2026: 55.7Nov 1, 2026Nov 2, 2026

Semaphore incident history (last 90 days)

Source: Semaphore status page · last checked · Subscribe via RSS

Our independent monitoring

We check these public Semaphore pages every 5 minutes. An outage is recorded after two consecutive failed checks.

PageLast checkUptime (30d)Avg response
HomepageUp 100%691 ms
LoginUp 100%298 ms
DocumentationUp 100%437 ms

How Semaphore compares

Semaphore vs Bitrise

98.96% vs 99.90% uptime

Semaphore vs Depot

98.96% vs 99.89% uptime

Semaphore vs GitLab

98.96% vs 100% uptime

Semaphore vs Bitbucket

98.96% vs 99.74% uptime

Semaphore vs Azure DevOps

98.96% vs 98.64% uptime

Semaphore vs Buildkite

98.96% vs 99.57% uptime

Most reliable Semaphore alternatives →

Semaphore status FAQ

Is Semaphore down right now?

No, Semaphore is up and running. Semaphore's status page currently reports all systems operational, and all 3 of the Semaphore pages we check every five minutes are responding. This page updates automatically when that changes.

How reliable is Semaphore?

Semaphore has a reliability score of 55.7 out of 100, ranking #9 of 11 code hosting & CI platforms. Over the last 90 days it had 98.96% effective uptime.

How often does Semaphore have outages?

Semaphore published 21 incidents on its status page in the last 90 days (5 partial or major outages) and 46 in the past 12 months.

How long do Semaphore outages last?

Semaphore resolves incidents in 4h 10m on average. Its longest outage in the past year lasted 10h 5m, on Aug 31, 2026.

Does Semaphore have a status page?

Yes. Semaphore's official status page is status.semaphore.io. We read it every five minutes and keep its full incident history.