Semaphore CI logo

Is Semaphore CI Down?

OtherLive status, outages, and incident history

No. Semaphore CI is up right now.

Every monitored Semaphore CI system is operational as of November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · every 60s

Know the moment Semaphore CI breaks

Semaphore CI is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Semaphore CI status page
How we know: the official Semaphore CI status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Semaphore CI Status Summary

As of 18:54 UTC on 9 November 2026, Semaphore CI is operational. PulsAPI checked Semaphore CI's official status page and found 7 of 7 components operational, with no active incidents. Over the last 30 days PulsAPI measured 99.95% uptime for Semaphore CI, counting degraded performance as up. The latest incident, "Delays in Job Processing", was on Oct 29, 2026 and lasted 1h 25m.

Cite as: PulsAPI, “Semaphore CI status”, checked 9 November 2026, 18:54 UTC. https://www.pulsapi.com/services/semaphore-ci

Semaphore CI Component Status

The main Semaphore CI systems on this page. All 7 are operational right now.

7operational
Semaphore
Operational
Upstream Services » Atlassian Bitbucket API
Operational
Upstream Services » Atlassian Bitbucket Source downloads
Operational

4 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Upstream Services » Atlassian Bitbucket Webhooks, Upstream Services » GitHub API Requests, Upstream Services » GitHub Packages, Upstream Services » GitHub Webhooks.

See all of them free

Component statuses may change independently during partial outages.

Recent Semaphore CI Outages & Incidents

Incident history from the official Semaphore CI status page, including resolution updates.

Delays in Job ProcessingResolved Oct 29, 2026 · 1h 25mResolved

This incident has been resolved. --- [2026-10-30T00:03:02.820Z] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-10-29T23:49:19.173Z] (identified) The issue has been identified and a fix is being implemented. --- [2026-10-29T23:18:35.895Z] (investigating) We are continuing to investigate this issue. --- [2026-10-29T22:51:35.678Z] (investigating) We are currently investigating this issue.

Delays in Job ProcessingResolved Oct 26, 2026 · 3h 14mResolved

This incident has been resolved. --- [2026-10-27T02:35:08.456Z] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-10-27T02:05:05.945Z] (identified) The issue has been identified and a fix is being implemented. --- [2026-10-27T01:39:54.673Z] (monitoring) We are continuing to monitoring the situation. --- [2026-10-27T01:27:59.465Z] (monitoring) Job processing times have returned to normal. We're continuing to monitor the situation closely to ensure service continues running as expected. --- [2026-10-27T01:01:59.584Z] (monitoring) We are starting to see improvements in job processing times, and jobs should be returning to normal. --- [2026-10-27T00:36:34.041Z] (monitoring) We're continuing to monitor the situation closely and will provide further updates. --- [2026-10-27T00:10:02.153Z] (identified) The issue has been identified, and we are continuing to monitor the situation. --- [2026-10-26T23:40:01.917Z] (investigating) We are currently investigating this issue.

Delays in Job ProcessingResolved Oct 26, 2026 · 2h 41mResolved

This incident has been resolved. --- [2026-10-26T17:02:32.392Z] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-10-26T16:03:50.189Z] (identified) The issue has been identified and a fix is being implemented. --- [2026-10-26T15:02:04.753Z] (investigating) We are currently investigating this issue.

Semaphore CI Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Semaphore CI incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 11100.00% average · 29 days with incidentsNov 9

Going further back: Semaphore CI uptime by month and every recorded Semaphore CI outage.

Live Semaphore CI Outage Reports

Problems reported by engineers using Semaphore CI. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Semaphore CI problems reported yet.

Something wrong with Semaphore CI on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Semaphore CI

Is Semaphore CI down? Semaphore CI reports live availability for 8 components at status.semaphore.io, among them Semaphore, GitHub API Requests and GitHub Packages. Track Semaphore CI outages, degradations and past incidents here, with uptime history and alerts across your CI/CD stack.

Over the past 30 days, PulsAPI has measured Semaphore CI uptime at 99.95%. Response times, incident history, and SLA tracking for Semaphore CI are available on the PulsAPI dashboard.

Semaphore CI Status FAQ

Is Semaphore CI down right now?

The verdict at the top of this page comes from the latest poll of the official Semaphore CI status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Semaphore CI is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Semaphore CI recovers.

How do I check Semaphore CI uptime history?

PulsAPI tracks Semaphore CI uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.95%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Semaphore CI changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Semaphore CI outages?

PulsAPI reads the official Semaphore CI status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Semaphore CI components?

Yes. PulsAPI monitors 7 individual Semaphore CI components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Semaphore CI goes down?

Yes. Create a free account and subscribe to Semaphore CI: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Semaphore CI to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Semaphore CI problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Semaphore CI?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Semaphore CI plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Semaphore CI with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services