Is Semaphore down?

Last checked 2m ago
Current status
Semaphore is up

No incidents right now.

Semaphore is operational right now. Last checked 2m ago; the most recent incident resolved 6h ago.

Real-time Semaphore status, recent outages, and incident history: pulled directly from Semaphore's official status page at status.semaphoreci.com every 5 minutes. Pingoru tracks 7 Semaphore services and has captured 22 incidents in the last 90 days (96.74% uptime). Get email, Slack, Discord, or webhook alerts the moment Semaphore reports a new incident, free for 3 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 8,000+ providers
Semaphore uptime 96.74% uptime · past 90 days
Mon Wed Fri
JulAugSepOct
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 3h 14m
    Started Oct 26, 2026, 11:40 PM UTC · Resolved Oct 27, 2026, 02:54 AM UTC
    Semaphore
    Timeline · 9 updates
    • investigating · Oct 26, 2026, 11:40 PM UTC

      We are currently investigating this issue.

    • identified · Oct 27, 2026, 12:10 AM UTC

      The issue has been identified, and we are continuing to monitor the situation.

    • monitoring · Oct 27, 2026, 12:36 AM UTC

      We're continuing to monitor the situation closely and will provide further updates.

    • monitoring · Oct 27, 2026, 01:01 AM UTC

      We are starting to see improvements in job processing times, and jobs should be returning to normal.

    • monitoring · Oct 27, 2026, 01:27 AM UTC

      Job processing times have returned to normal. We're continuing to monitor the situation closely to ensure service continues running as expected.

    • monitoring · Oct 27, 2026, 01:39 AM UTC

      We are continuing to monitoring the situation.

    • identified · Oct 27, 2026, 02:05 AM UTC

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

    • monitoring · Oct 27, 2026, 02:35 AM UTC

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

    • resolved · Oct 27, 2026, 02:54 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 2h 41m
    Started Oct 26, 2026, 03:02 PM UTC · Resolved Oct 26, 2026, 05:43 PM UTC
    Semaphore
    Timeline · 4 updates
    • investigating · Oct 26, 2026, 03:02 PM UTC

      We are currently investigating this issue.

    • identified · Oct 26, 2026, 04:03 PM UTC

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

    • monitoring · Oct 26, 2026, 05:02 PM UTC

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

    • resolved · Oct 26, 2026, 05:43 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 2h 15m
    Started Oct 22, 2026, 03:08 PM UTC · Resolved Oct 22, 2026, 05:23 PM UTC
    Semaphore
    Timeline · 5 updates
    • investigating · Oct 22, 2026, 03:08 PM UTC

      We are currently investigating this issue.

    • investigating · Oct 22, 2026, 04:03 PM UTC

      We are continuing to investigate this issue.

    • identified · Oct 22, 2026, 05:01 PM UTC

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

    • monitoring · Oct 22, 2026, 05:12 PM UTC

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

    • resolved · Oct 22, 2026, 05:23 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  4. Resolved 3h 46m
    Started Oct 21, 2026, 02:14 PM UTC · Resolved Oct 21, 2026, 06:01 PM UTC
    Semaphore
    Timeline · 9 updates
    • investigating · Oct 21, 2026, 02:14 PM UTC

      We are currently investigating this issue.

    • identified · Oct 21, 2026, 02:23 PM UTC

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

    • monitoring · Oct 21, 2026, 02:41 PM UTC

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

    • monitoring · Oct 21, 2026, 03:38 PM UTC

      We are continuing to monitor for any further issues.

    • monitoring · Oct 21, 2026, 04:33 PM UTC

      We are continuing to monitor for any further issues.

    • investigating · Oct 21, 2026, 05:02 PM UTC

      We are currently investigating this issue.

    • identified · Oct 21, 2026, 05:18 PM UTC

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

    • monitoring · Oct 21, 2026, 05:40 PM UTC

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

    • resolved · Oct 21, 2026, 06:01 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  5. Resolved 2h 1m
    Started Oct 20, 2026, 09:58 PM UTC · Resolved Oct 20, 2026, 11:59 PM UTC
    Semaphore
    Timeline · 6 updates
    • identified · Oct 20, 2026, 09:58 PM UTC

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

    • identified · Oct 20, 2026, 10:27 PM UTC

      We are continuing to work on a fix for this issue.

    • identified · Oct 20, 2026, 10:44 PM UTC

      We're starting to see improvements in job scheduling times, although some delays may still occur. We're continuing to monitor the situation closely and will provide further updates as we make progress.

    • monitoring · Oct 20, 2026, 11:10 PM UTC

      Job scheduling times have returned to normal. We're continuing to monitor the situation closely to ensure service continues running as expected.

    • monitoring · Oct 20, 2026, 11:30 PM UTC

      We are continuing to monitor the situation.

    • resolved · Oct 20, 2026, 11:59 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

See the full Semaphore outage history

16 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

Incident record

Since April 2026 · Statuspage by Atlassian · 7 components checked every 5 minutes
58incidents recorded
46last 12 months
21last 90 days
4 hourstypical duration, 12 months

The longest incident in the last year, Periodic authentication failure with GitHub repositories on September 2, 2026, ran for 25 hours. 4 maintenance windows announced in the same period.

Most affected components, last 12 months

  • Semaphore46

Latest incidents

Outage history

Past 90 days · 21 incidents View full outage history →