What is Semaphore's uptime?

Over the last 90 days, Semaphore reported 97.30% uptime on its official status page. That figure is calculated from the public incident timeline at http://status.semaphoreci.com — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Semaphore's uptime history rolling forward in real time.

Has Semaphore had outages in 2026?

Yes — Semaphore has had 16 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.

When was the last Semaphore outage?

The most recent Semaphore incident was "Periodic authentication failure with GitHub repositories", which started on September 2, 2026 and was resolved on September 3, 2026. Pingoru captured this directly from http://status.semaphoreci.com. See the full incident card above for affected components and the update timeline.

How often does Semaphore have outages?

Based on the last 90 days, Semaphore averages 5.3 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.

Where is Semaphore's status page?

Semaphore's official status page is http://status.semaphoreci.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.

Is Semaphore down right now?

Semaphore is up. Pingoru checks the official status page every 5 minutes and flips this headline the moment Semaphore reports a change. Current status is based on 7 tracked services.

How does Pingoru know if Semaphore is down?

We read http://status.semaphoreci.com directly, using Semaphore's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.

Where can I get notified when Semaphore has an outage?

Create a free Pingoru account and add Semaphore as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.

Semaphore's status page says the service is up, but I'm having issues — what's wrong?

Three common reasons: • A real Semaphore incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Semaphore issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.

Where does Pingoru get the official Semaphore status?

We use Semaphore's own status page at http://status.semaphoreci.com. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.

All tracked Semaphore components are reporting operational. No incidents are currently affecting service.

Is Semaphore down?

Last checked 9m ago

Current status

Semaphore is up

No incidents right now.

Get alerts when Semaphore breaks → View Semaphore outage history →

Free · no credit card

Official status page: http://status.semaphoreci.com · Polled every 5 minutes · 7 components tracked

Semaphore is operational right now. Last checked 9m ago; the most recent incident resolved 9d ago.

Real-time Semaphore status, recent outages, and incident history — pulled directly from Semaphore's official status page at http://status.semaphoreci.com every 5 minutes. Pingoru tracks 7 Semaphore services and has captured 16 incidents in the last 90 days (97.30% uptime). Get email, Slack, Discord, or webhook alerts the moment Semaphore reports a new incident — free for 5 monitors, no credit card.

Users who monitor Semaphore also follow these DevOps services:

RubyGems View all 6,000+ providers

Semaphore uptime 97.30% uptime · past 90 days

Mon Wed Fri

JunJulAugSep

Less More

Recent outages & incidents

Past 90 days

Periodic authentication failure with GitHub repositories

Resolved 1d

Started Sep 02, 2026, 04:08 PM UTC · Resolved Sep 03, 2026, 04:41 PM UTC

Semaphore
Timeline · 15 updates
- identified · Sep 02, 2026, 04:08 PM UTC
  
  The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 We are continuing to monitor the situation on our end and will share further updates as they become available.
- identified · Sep 02, 2026, 04:35 PM UTC
  
  The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 We are continuing to monitor the situation on our end and will share further updates as they become available.
- identified · Sep 02, 2026, 05:04 PM UTC
  
  The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 We are continuing to monitor the situation on our end and will share further updates as they become available.
- identified · Sep 02, 2026, 05:32 PM UTC
  
  The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 We are continuing to monitor the situation on our end and will share further updates as they become available.
- identified · Sep 02, 2026, 06:02 PM UTC
  
  The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 We are continuing to monitor the situation on our end and will share further updates as they become available.
- identified · Sep 02, 2026, 06:31 PM UTC
  
  The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 We are continuing to monitor the situation on our end and will share further updates as they become available.
- identified · Sep 02, 2026, 07:00 PM UTC
  
  The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 We are continuing to monitor the situation on our end and will share further updates as they become available.
- identified · Sep 02, 2026, 07:32 PM UTC
  
  The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 We are continuing to monitor the situation on our end and will share further updates as they become available.
- identified · Sep 02, 2026, 08:00 PM UTC
  
  The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 We are continuing to monitor the situation on our end and will share further updates as they become available.
- identified · Sep 02, 2026, 08:30 PM UTC
  
  The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 We are continuing to monitor the situation on our end and will share further updates as they become available.
- identified · Sep 02, 2026, 09:00 PM UTC
  
  The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 We are continuing to monitor the situation on our end and will share further updates as they become available.
- identified · Sep 02, 2026, 09:30 PM UTC
  
  The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 We are continuing to monitor the situation on our end and will share further updates as they become available.
- identified · Sep 02, 2026, 10:07 PM UTC
  
  Our engineers are actively monitoring the ongoing situation affecting HTTPS operations: https://github.com/orgs/community/discussions/206581. We’ll share the next update once we have new information from GitHub. As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1
- identified · Sep 03, 2026, 12:45 PM UTC
  
  Our engineers are actively monitoring the intermittent issue affecting Git operations over HTTPS. We will share another update when more information becomes available. To prevent affected builds from stalling while waiting for credentials, our engineering team has implemented fail-fast behavior. Affected builds will now fail promptly, reducing unnecessary runtime. If the issue persists after rerunning the job, add the following command to the job before the affected Git operation to force Git to use HTTP/1.1: git config --global http.version HTTP/1.1
- resolved · Sep 03, 2026, 04:41 PM UTC
  
  Semaphore 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 their end rather than a bug. You can read their latest statement here: https://github.com/orgs/community/discussions/206581#discussioncomment-18269083 For builds affected by this behavior, the previously shared workaround remains available. Configure Git to use HTTP/1.1 before running the affected Git operation: git config --global http.version HTTP/1.1 We will add this instruction and further context to our documentation. Any additional guidance from Semaphore will be shared through in-app notifications. For further assistance, contact our support team at [email protected].
Latest: Semaphore 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 …
Periodic authentication failure with GitHub repositories

Resolved 3h 59m

Started Sep 02, 2026, 11:17 AM UTC · Resolved Sep 02, 2026, 03:16 PM UTC

Semaphore
Timeline · 8 updates
- investigating · Sep 02, 2026, 11:17 AM UTC
  
  We are currently investigating this issue.
- investigating · Sep 02, 2026, 11:44 AM UTC
  
  We are still looking into the cause of this issue, but as a temporary workaround, you can add the following environment variable to your jobs, which will cause them to immediately fail and not hang: GIT_TERMINAL_PROMPT=0 After they fail, you can rerun the pipeline, and only the failed jobs should rerun, allowing you to work through this issue until we have more information to share.
- investigating · Sep 02, 2026, 12:18 PM UTC
  
  We are continuing to investigate this issue.
- identified · Sep 02, 2026, 12:53 PM UTC
  
  We have found that this is currently a wider situation impacting HTTPS operations, which is also affecting Semaphore and our users. You can read more about this in this thread: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 Please also note that we are continuing to monitor and investigate this situation on our end.
- identified · Sep 02, 2026, 01:29 PM UTC
  
  We have found that this is currently a wider situation impacting HTTPS operations, which is also affecting Semaphore and our users. You can read more about this in this thread: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 We are continuing to monitor and investigate this situation on our end.
- identified · Sep 02, 2026, 01:56 PM UTC
  
  We have found that this is currently a wider situation impacting HTTPS operations, which is also affecting Semaphore and our users. You can read more about this in this thread: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 We are continuing to monitor and investigate this situation on our end.
- monitoring · Sep 02, 2026, 02:19 PM UTC
  
  There was a wider situation impacting HTTPS operations, which also affected Semaphore and our users https://github.com/orgs/community/discussions/206581 The issue has since appeared to subside, but we're continuing to monitor the situation on our end.
- resolved · Sep 02, 2026, 03:16 PM UTC
  
  This incident has been resolved.
Latest: This incident has been resolved.
Delays in job processing

Resolved 10h 4m

Started Aug 31, 2026, 12:06 PM UTC · Resolved Aug 31, 2026, 10:11 PM UTC

Semaphore
Timeline · 19 updates
- investigating · Aug 31, 2026, 12:06 PM UTC
  
  We are currently investigating this issue.
- identified · Aug 31, 2026, 12:56 PM UTC
  
  The issue has been identified and a fix is being implemented.
- identified · Aug 31, 2026, 02:10 PM UTC
  
  We are continuing to work on a fix for this issue.
- identified · Aug 31, 2026, 03:32 PM UTC
  
  We’ve identified network connectivity issues between our control plane and build servers. We’re actively working to restore normal service.
- identified · Aug 31, 2026, 04:01 PM UTC
  
  We’re still working to resolve the network connectivity issues between our control plane and build servers. We’ll share another update as soon as we have more information.
- identified · Aug 31, 2026, 04:34 PM UTC
  
  We’re still working to resolve the network connectivity issues between our control plane and build servers. We’ll share another update as soon as we have more information.
- identified · Aug 31, 2026, 05:17 PM UTC
  
  We’re still working to resolve the network connectivity issues between our control plane and build servers. We’ll share another update as soon as we have more information.
- identified · Aug 31, 2026, 05:48 PM UTC
  
  We’re still working to resolve the network connectivity issues between our control plane and build servers. We’ll share another update as soon as we have more information.
- identified · Aug 31, 2026, 05:50 PM UTC
  
  We are continuing to work on a fix for this issue.
- identified · Aug 31, 2026, 05:58 PM UTC
  
  We are continuing to work on a fix for this issue.
- identified · Aug 31, 2026, 06:22 PM UTC
  
  We’re still working to resolve the network connectivity issues between our control plane and build servers. We’ll share another update as soon as we have more information.
- identified · Aug 31, 2026, 06:48 PM UTC
  
  We are continuing to work on a fix for this issue.
- identified · Aug 31, 2026, 07:21 PM UTC
  
  Our team is continuing to work on a fix for this issue.
- identified · Aug 31, 2026, 07:49 PM UTC
  
  We are continuing to work on a fix for this issue.
- identified · Aug 31, 2026, 08:18 PM UTC
  
  Our engineering team is actively working to resolve this issue.
- monitoring · Aug 31, 2026, 08:35 PM UTC
  
  A fix has been implemented and we are monitoring the results.
- monitoring · Aug 31, 2026, 09:09 PM UTC
  
  We are continuing to monitor for any further issues.
- monitoring · Aug 31, 2026, 09:44 PM UTC
  
  Our team is still monitoring the results.
- resolved · Aug 31, 2026, 10:11 PM UTC
  
  This incident has been resolved.
Latest: This incident has been resolved.
Delays in job processing

Resolved 1h 52m

Started Aug 28, 2026, 07:17 PM UTC · Resolved Aug 28, 2026, 09:09 PM UTC

Semaphore
Timeline · 4 updates
- investigating · Aug 28, 2026, 07:17 PM UTC
  
  We are currently investigating this issue.
- identified · Aug 28, 2026, 08:11 PM UTC
  
  The issue has been identified and a fix is being implemented.
- monitoring · Aug 28, 2026, 08:31 PM UTC
  
  A fix has been implemented and we are monitoring the results.
- resolved · Aug 28, 2026, 09:09 PM UTC
  
  This incident has been resolved.
Latest: This incident has been resolved.
Delays in Job Processing

Resolved 52m

Started Aug 27, 2026, 08:09 PM UTC · Resolved Aug 27, 2026, 09:01 PM UTC

Semaphore
Timeline · 5 updates
- investigating · Aug 27, 2026, 08:09 PM UTC
  
  We are currently investigating this issue.
- investigating · Aug 27, 2026, 08:11 PM UTC
  
  We are continuing to investigate this issue.
- identified · Aug 27, 2026, 08:26 PM UTC
  
  The issue has been identified and a fix is being implemented.
- monitoring · Aug 27, 2026, 08:35 PM UTC
  
  A fix has been implemented and we are monitoring the results.
- resolved · Aug 27, 2026, 09:01 PM UTC
  
  This incident has been resolved.
Latest: This incident has been resolved.

See the full Semaphore outage history

10 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Semaphore outage history →

Or sign up free to get alerts when Semaphore breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 15 incidents View full outage history →

Periodic authentication failure with GitHub repositories Resolved

Started Sep 02, 2026, 04:08 PM UTC · Resolved Sep 03, 2026, 04:41 PM UTC · 1d
Periodic authentication failure with GitHub repositories Resolved

Started Sep 02, 2026, 11:17 AM UTC · Resolved Sep 02, 2026, 03:16 PM UTC · 3h 59m
Delays in job processing Resolved

Started Aug 31, 2026, 12:06 PM UTC · Resolved Aug 31, 2026, 10:11 PM UTC · 10h 4m
Delays in job processing Resolved

Started Aug 28, 2026, 07:17 PM UTC · Resolved Aug 28, 2026, 09:09 PM UTC · 1h 52m
Delays in Job Processing Resolved

Started Aug 27, 2026, 08:09 PM UTC · Resolved Aug 27, 2026, 09:01 PM UTC · 52m
Platform Outage Resolved

Started Aug 27, 2026, 06:43 PM UTC · Resolved Aug 27, 2026, 07:30 PM UTC · 47m
Degraded performance on r1-standard machines Resolved

Started Aug 25, 2026, 08:35 AM UTC · Resolved Aug 25, 2026, 02:47 PM UTC · 6h 11m
Issues with Bitbucket integration Resolved

Started Aug 21, 2026, 07:14 PM UTC · Resolved Aug 21, 2026, 08:47 PM UTC · 1h 33m