Is Semaphore down?

Last checked 7m ago
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 7m ago; the most recent incident resolved 6d 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 8 incidents in the last 90 days (98.73% 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 98.73% uptime · past 90 days
Mon Wed Fri
AprMayJunJul
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 1h 43m
    Started Jul 23, 2026, 12:35 AM UTC · Resolved Jul 23, 2026, 02:18 AM UTC
    Semaphore
    Timeline · 5 updates
    • investigating · Jul 23, 2026, 12:35 AM UTC

      We are currently investigating this issue.

    • investigating · Jul 23, 2026, 01:03 AM UTC

      We are continuing to investigate this issue.

    • identified · Jul 23, 2026, 01:25 AM UTC

      The issue has been identified and a fix is being implemented.

    • monitoring · Jul 23, 2026, 02:00 AM UTC

      A fix has been implemented and we have observed an improvement in job processing. We are continuing to monitor the situation.

    • resolved · Jul 23, 2026, 02:18 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 5h 10m
    Started Jul 21, 2026, 08:36 AM UTC · Resolved Jul 21, 2026, 01:46 PM UTC
    Semaphore
    Timeline · 7 updates
    • investigating · Jul 21, 2026, 08:36 AM UTC

      We are currently investigating this issue.

    • investigating · Jul 21, 2026, 08:49 AM UTC

      As a workaround to get more consistent builds during this time, please try adding the --use-cache flag to your checkout command. Read more about it here: https://docs.semaphore.io/reference/toolbox#cache-full-clone

    • investigating · Jul 21, 2026, 09:06 AM UTC

      Our engineering team is still investigating and working on this issue, but as a current workaround, you can regenerate your GitHub deployment key. You can find the instructions on how to do that here: https://docs.semaphore.io/using-semaphore/connect-github#deploy-key

    • monitoring · Jul 21, 2026, 09:25 AM UTC

      Our team is monitoring the situation. If you are affected, please regenerate your deploy key by following the instructions on this page: https://docs.semaphore.io/using-semaphore/connect-github#deploy-key

    • monitoring · Jul 21, 2026, 10:53 AM UTC

      We are continuing to monitor the situation, and you can follow the current GitHub incident at the following link: https://www.githubstatus.com/incidents/g40zcbvchny4

    • monitoring · Jul 21, 2026, 12:18 PM UTC

      GitHub confirmed that the incident on their end has been resolved, and services should now be returning to normal. We are continuing to monitor the situation. You can review the GitHub update here: https://www.githubstatus.com/incidents/g40zcbvchny4

    • resolved · Jul 21, 2026, 01:46 PM UTC

      GitHub confirmed that the incident on their end has been resolved. You can review the GitHub update here: https://www.githubstatus.com/incidents/g40zcbvchny4

    Latest: GitHub confirmed that the incident on their end has been resolved. You can review the GitHub update here: https://www.githubstatus.com/incidents/g40zcbvchny4

  3. Resolved 2h 53m
    Started Jul 17, 2026, 10:32 AM UTC · Resolved Jul 17, 2026, 01:25 PM UTC
    Semaphore
    Timeline · 3 updates
    • investigating · Jul 17, 2026, 10:32 AM UTC

      We are currently investigating this issue.

    • monitoring · Jul 17, 2026, 10:51 AM UTC

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

    • resolved · Jul 17, 2026, 01:25 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  4. Resolved 44m
    Started Jul 17, 2026, 12:21 AM UTC · Resolved Jul 17, 2026, 01:05 AM UTC
    Semaphore
    Timeline · 3 updates
    • investigating · Jul 17, 2026, 12:21 AM UTC

      We are currently investigating this issue.

    • monitoring · Jul 17, 2026, 12:43 AM UTC

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

    • resolved · Jul 17, 2026, 01:05 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  5. Resolved 24m
    Started Jun 24, 2026, 09:01 PM UTC · Resolved Jun 24, 2026, 09:26 PM UTC
    Semaphore
    Timeline · 4 updates
    • investigating · Jun 24, 2026, 09:01 PM UTC

      We are currently investigating this issue.

    • identified · Jun 24, 2026, 09:07 PM UTC

      The issue has been identified and a fix is being implemented.

    • monitoring · Jun 24, 2026, 09:16 PM UTC

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

    • resolved · Jun 24, 2026, 09:26 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

See the full Semaphore outage history

3 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 · 8 incidents View full outage history →