Is Semaphore down?

Last checked just now
Current status
Semaphore is up

No incidents right now.

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

Semaphore is operational right now. Last checked just now; the most recent incident resolved 3d 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 3 incidents in the last 90 days (99.52% 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: GitHub Confluence Circle CI OpsGenie JFrog Papertrail Airbrake Splunk OnCall Datadog EU RubyGems View all 6,000+ providers
Semaphore uptime 99.52% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 1h 9m
    Started Jun 10, 2026, 03:12 PM UTC · Resolved Jun 10, 2026, 04:22 PM UTC
    Semaphore
    Timeline · 4 updates
    • identified · Jun 10, 2026, 03:12 PM UTC

      We're experiencing an elevated level of 500's errors and are currently looking into the issue.

    • identified · Jun 10, 2026, 03:20 PM UTC

      The issue has been identified, and our team is implementing a fix.

    • monitoring · Jun 10, 2026, 04:14 PM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · Jun 10, 2026, 04:22 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 6h 47m
    Started May 20, 2026, 08:44 AM UTC · Resolved May 20, 2026, 03:32 PM UTC
    Semaphore
    Timeline · 5 updates
    • identified · May 20, 2026, 08:44 AM UTC

      We identified slow communication between Semaphore jobs and GitHub. We are continuing to work with our upstream provider to resolve this. For impacted jobs, please replace the normal checkout command with the following: retry --times 5 "timeout 40 bash -lc 'source ~/.toolbox/toolbox; checkout'" And afterwards, use cd to change the directory to the cloned repository (replace with your project).

    • monitoring · May 20, 2026, 12:48 PM UTC

      A fix has been implemented and we are monitoring the results.

    • identified · May 20, 2026, 01:59 PM UTC

      We identified slow GitHub operations related to problems with the network, and we deployed a fix to re-route those operations to a healthier server. Some HTTPS operations started to fail because of that. To disable the fix, you should use the command: sudo sed -i 's/^\([0-9].*github\.com\)/#\1/' /etc/hosts And to re-enable, you can use: sudo sed -i 's/^#\([0-9].*github\.com\)/\1/' /etc/hosts

    • monitoring · May 20, 2026, 03:02 PM UTC

      A fix has been implemented, and everything should be back to normal. The previously shared snippets can be removed.

    • resolved · May 20, 2026, 03:32 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 5h 42m
    Started May 19, 2026, 10:00 AM UTC · Resolved May 19, 2026, 03:42 PM UTC
    Semaphore
    Timeline · 5 updates
    • investigating · May 19, 2026, 10:00 AM UTC

      We are currently investigating this issue.

    • investigating · May 19, 2026, 10:38 AM UTC

      We are continuing to investigate this issue.

    • identified · May 19, 2026, 11:18 AM UTC

      We identified that the issue is slow communication between our jobs and GitHub. We are currently working with our upstream provider to to resolve this. For impacted jobs, please replace the normal checkout command with the following: retry --times 5 "timeout 40 bash -lc 'source ~/.toolbox/toolbox; checkout' And afterwards, use cd to change the directory to the cloned repository (replace with your project).

    • monitoring · May 19, 2026, 03:10 PM UTC

      We are not currently seeing timeouts related to slow connections. Our team is continuing to monitor the situation to confirm that service has fully returned to normal.

    • resolved · May 19, 2026, 03:42 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

Outage history

Past 90 days · 3 incidents View full outage history →