Is Semaphore Down?

No — Semaphore is up

Semaphore's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 178 ms

Right now

The verdict is the worse of these two. How we decide

Semaphore's status page

status.semaphore.io · read just now · checked every 3 minutes

Operational

Semaphore's components, as its status page reports them
Component	Status
Semaphore the service itself	Operational
GitHub API Requests	Operational
GitHub Packages	Operational
GitHub Webhooks	Operational
Atlassian Bitbucket API	Operational
Atlassian Bitbucket Source downloads	Operational
Atlassian Bitbucket Webhooks	Operational

Open their status page

FlareWarden checks

semaphore.io from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 178 ms
Checked: 3 hours ago

By region

Amsterdam reachable, 76 ms
Dallas reachable, 198 ms
Frankfurt reachable, 161 ms
Newark reachable, 308 ms
Paris reachable, 251 ms
Stockholm reachable, 176 ms
São Paulo reachable, 48 ms
Toronto reachable, 208 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	29 ms	2 ms	8 ms	66 ms
Dallas	149 ms	2 ms	8 ms	185 ms
Frankfurt	121 ms	2 ms	7 ms	153 ms
Newark	181 ms	2 ms	21 ms	300 ms
Paris	191 ms	1 ms	8 ms	244 ms
Stockholm	92 ms	1 ms	8 ms	168 ms
São Paulo	8 ms	2 ms	7 ms	41 ms
Toronto	82 ms	2 ms	12 ms	194 ms

We check that semaphore.io loads, not every feature behind it. Test it yourself

History

Incidents Semaphore reported

Since Oct 22, 2 days · from status.semaphore.io

Incidents: 3
Major or critical: 0
Median to resolve: 2h 15m

Delays in Job Processing
minor · Oct 22
lasted 2h 15m
Delays in Job Processing
minor · Oct 21
lasted 3h 46m
Delays in jobs scheduling
Unrated · Oct 20
lasted 2h 1m

Semaphore website availability

Measured by FlareWarden · semaphore.io

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 370ms

Last 30 days

65-day clean streak

Sep 24 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of semaphore.io from multiple regions every 6 hours. Semaphore's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 65 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Semaphore itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Semaphore goes down

We check Semaphore every 6 hours, and again when you open this page if that was more than 30 minutes ago. 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