Is Semaphore Down?

No — Semaphore is up

Reachable from all 8 checked regions

Average response time: 268ms

Last checked 3 hours ago · checks run every 6 hours

Official status page: https://status.semaphore.io

Semaphore uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

414ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 53 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

53-day clean streak

Sep 13 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

fra

206ms

DNS 125ms TCP 2ms TLS 14ms TTFB 192ms

gru

217ms

DNS 18ms TCP 2ms TLS 9ms TTFB 207ms

iad

260ms

DNS 138ms TCP 2ms TLS 11ms TTFB 236ms

jnb

403ms

DNS 194ms TCP 1ms TLS 6ms TTFB 397ms

lax

523ms

DNS 164ms TCP 1ms TLS 8ms TTFB 459ms

lhr

93ms

DNS 32ms TCP 3ms TLS 13ms TTFB 82ms

nrt

260ms

DNS 86ms TCP 1ms TLS 7ms TTFB 254ms

ord

186ms

DNS 126ms TCP 2ms TLS 11ms TTFB 179ms

What Semaphore does

Semaphore is a hosted continuous integration and delivery service that runs builds, tests and deployment pipelines triggered by commits and pull requests. Teams connect it to GitHub or Bitbucket and gate merges on its results. An outage does not take a product down, but it stops the pipeline that ships changes, including the fix for whatever else is broken.

What an outage looks like

Pushes and pull requests do not trigger builds, so pipelines sit idle with no obvious error. Jobs queue and never start, or start and hang without producing logs. Status checks never report back to GitHub or Bitbucket, leaving pull requests blocked on a check that will not arrive. Artifacts and caches fail to upload at the end of otherwise successful jobs.

What to do about it

status.semaphore.io lists Semaphore itself alongside GitHub API Requests, GitHub Packages, GitHub Webhooks and the equivalent Atlassian Bitbucket components, because a missing webhook from your host looks exactly like a Semaphore fault. Check those rows first when builds are simply not triggering. For an urgent release, running the same steps by hand is often faster than waiting, provided the deploy path allows it.

Is it down for everyone, or just you?

If this page says Semaphore is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Semaphore outage FAQ

My builds are not triggering. Is it Semaphore or GitHub?

The status page answers this directly: it tracks GitHub Webhooks, GitHub API Requests and GitHub Packages alongside Semaphore itself, and the Bitbucket equivalents too. A webhook that never leaves GitHub means Semaphore has nothing to react to, and the symptom is identical to a Semaphore outage. Check those rows before opening a support ticket.

Can I deploy while Semaphore is down?

Usually yes, if you can run the pipeline steps by hand and your deploy target does not require a Semaphore-held credential. Reproduce the build and test steps locally first rather than skipping them, because a manual deploy without the usual gates is how one outage turns into a second, self-inflicted incident.

Will queued jobs run after the incident clears?

Typically they do, and pushing more commits during an outage only lengthens that queue. When capacity returns, everything backed up starts at once, which can take a while to clear on a busy repository. If one specific job matters, wait for the backlog rather than re-triggering it and adding another copy of the same work.

A pull request is blocked on a check that never reports. What can I do?

The check is waiting on a status Semaphore cannot deliver. Repository administrators can merge past a required check, but doing so removes the gate the check exists to provide. Prefer waiting unless the change is genuinely urgent, and if you do override, re-run the pipeline afterwards and confirm the result.

Does a Semaphore outage affect code already deployed?

No. Semaphore builds and ships code; it does not serve it. Anything already running in production keeps running, unaffected. The real cost of an outage is that you cannot ship a change, which bites hardest when the change you need to ship is the fix for a separate production problem.

How we measure this

We request Semaphore's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Semaphore publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Semaphore goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required