Semaphore CI Status: check for Semaphore CI outages and issues

Semaphore CI status is Operational

Thu 3

Fri 4

Sat 5

Sun 6

Mon 7

Tue 8

Wed 9

now

Semaphore CI Semaphore

Thu 3

Fri 4

Sat 5

Sun 6

Mon 7

Tue 8

Wed 9

now

See all 9 Semaphore CI components

Last updated 1 minute ago from official status page. Learn more

You're checking on Semaphore CI - but is your own site converting?

Outages aren't the only thing that costs you visitors.
Get a visual audit that shows exactly where your site loses conversions.
Free, takes 2 minutes.

Audit Your Website Free →

Active Incidents

No active incidents

Recently Resolved Incidents

Periodic authentication failure with GitHub repositories

Started 2 Sep 2026 16:08:41 (7 days ago), resolved 3 Sep 2026 16:41:09 (6 days ago)

Minor Incident

Resolved

Semaphore

The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581

As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

We are continuing to monitor the situation on our end and will share further updates as they become available.

Resolved: Semaphore is currently operating normally, which is why we’re marking this incident as resolved.

GitHub confirmed that the behavior affecting unauthenticated Git operations is the result of an intentional change on their end rather than a bug. You can read their latest statement here: https://github.com/orgs/community/discussions/206581#discussioncomment-18269083

For builds affected by this behavior, the previously shared workaround remains available. Configure Git to use HTTP/1.1 before running the affected Git operation: git config --global http.version HTTP/1.1

We will add this instruction and further context to our documentation. Any additional guidance from Semaphore will be shared through in-app notifications.

For further assistance, contact our support team at [email protected].

3 Sep 2026 16:41:09 (6 days ago)

Identified: Our engineers are actively monitoring the intermittent issue affecting Git operations over HTTPS. We will share another update when more information becomes available.

To prevent affected builds from stalling while waiting for credentials, our engineering team has implemented fail-fast behavior. Affected builds will now fail promptly, reducing unnecessary runtime.

If the issue persists after rerunning the job, add the following command to the job before the affected Git operation to force Git to use HTTP/1.1: git config --global http.version HTTP/1.1

3 Sep 2026 12:45:39 (6 days ago)

Identified: Our engineers are actively monitoring the ongoing situation affecting HTTPS operations: https://github.com/orgs/community/discussions/206581. We’ll share the next update once we have new information from GitHub.

As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

2 Sep 2026 22:07:08 (7 days ago)

Identified: The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581

As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

We are continuing to monitor the situation on our end and will share further updates as they become available.

2 Sep 2026 21:30:52 (7 days ago)

Identified: The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581

As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

We are continuing to monitor the situation on our end and will share further updates as they become available.

2 Sep 2026 21:00:37 (7 days ago)

Identified: The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581

As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

We are continuing to monitor the situation on our end and will share further updates as they become available.

2 Sep 2026 20:30:26 (7 days ago)

Identified: The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581

As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

We are continuing to monitor the situation on our end and will share further updates as they become available.

2 Sep 2026 20:00:13 (7 days ago)

Identified: The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581

As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

We are continuing to monitor the situation on our end and will share further updates as they become available.

2 Sep 2026 19:32:45 (7 days ago)

Identified: The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581

As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

We are continuing to monitor the situation on our end and will share further updates as they become available.

2 Sep 2026 19:00:14 (7 days ago)

Identified: The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581

As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

We are continuing to monitor the situation on our end and will share further updates as they become available.

2 Sep 2026 18:31:31 (7 days ago)

Identified: The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581

As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

We are continuing to monitor the situation on our end and will share further updates as they become available.

2 Sep 2026 18:02:30 (7 days ago)

Identified: The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581

As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

We are continuing to monitor the situation on our end and will share further updates as they become available.

2 Sep 2026 17:32:55 (7 days ago)

Identified: The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581

As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

We are continuing to monitor the situation on our end and will share further updates as they become available.

2 Sep 2026 17:04:01 (7 days ago)

Identified: The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581

As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

We are continuing to monitor the situation on our end and will share further updates as they become available.

2 Sep 2026 16:35:57 (7 days ago)

Identified: The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581

As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

We are continuing to monitor the situation on our end and will share further updates as they become available.

2 Sep 2026 16:08:41 (7 days ago)

See all updates

Semaphore CI Outage Survival Guide

A step-by-step guide to help you survive a Semaphore CI outage

NaN%

Semaphore CI Components

Semaphore CI

Thu 3

Fri 4

Sat 5

Sun 6

Mon 7

Tue 8

Wed 9

now

Semaphore CI Semaphore

Thu 3

Fri 4

Sat 5

Sun 6

Mon 7

Tue 8

Wed 9

now

Periodic authentication failure with GitHub repositories

Started 2 Sep 2026 16:08:41 (7 days ago), resolved 3 Sep 2026 16:41:09 (6 days ago)

Minor Incident

Resolved

Semaphore

The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581

As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

We are continuing to monitor the situation on our end and will share further updates as they become available.

Resolved: Semaphore is currently operating normally, which is why we’re marking this incident as resolved.

We will add this instruction and further context to our documentation. Any additional guidance from Semaphore will be shared through in-app notifications.

For further assistance, contact our support team at [email protected].

3 Sep 2026 16:41:09 (6 days ago)

Identified: Our engineers are actively monitoring the intermittent issue affecting Git operations over HTTPS. We will share another update when more information becomes available.

To prevent affected builds from stalling while waiting for credentials, our engineering team has implemented fail-fast behavior. Affected builds will now fail promptly, reducing unnecessary runtime.

If the issue persists after rerunning the job, add the following command to the job before the affected Git operation to force Git to use HTTP/1.1: git config --global http.version HTTP/1.1

3 Sep 2026 12:45:39 (6 days ago)

As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

2 Sep 2026 22:07:08 (7 days ago)

Identified: The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581

As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

We are continuing to monitor the situation on our end and will share further updates as they become available.

2 Sep 2026 21:30:52 (7 days ago)

Identified: The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581

As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

We are continuing to monitor the situation on our end and will share further updates as they become available.

2 Sep 2026 21:00:37 (7 days ago)

Identified: The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581

As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

We are continuing to monitor the situation on our end and will share further updates as they become available.

2 Sep 2026 20:30:26 (7 days ago)

Identified: The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581

As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

We are continuing to monitor the situation on our end and will share further updates as they become available.

2 Sep 2026 20:00:13 (7 days ago)

Identified: The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581

As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

We are continuing to monitor the situation on our end and will share further updates as they become available.

2 Sep 2026 19:32:45 (7 days ago)

Identified: The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581

As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

We are continuing to monitor the situation on our end and will share further updates as they become available.

2 Sep 2026 19:00:14 (7 days ago)

Identified: The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581

As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

We are continuing to monitor the situation on our end and will share further updates as they become available.

2 Sep 2026 18:31:31 (7 days ago)

Identified: The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581

As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

We are continuing to monitor the situation on our end and will share further updates as they become available.

2 Sep 2026 18:02:30 (7 days ago)

Identified: The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581

As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

We are continuing to monitor the situation on our end and will share further updates as they become available.

2 Sep 2026 17:32:55 (7 days ago)

Identified: The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581

As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

We are continuing to monitor the situation on our end and will share further updates as they become available.

2 Sep 2026 17:04:01 (7 days ago)

Identified: The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581

As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

We are continuing to monitor the situation on our end and will share further updates as they become available.

2 Sep 2026 16:35:57 (7 days ago)

Identified: The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581

As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

We are continuing to monitor the situation on our end and will share further updates as they become available.

2 Sep 2026 16:08:41 (7 days ago)

See all updates

Semaphore CI Upstream Services

Thu 3

Fri 4

Sat 5

Sun 6

Mon 7

Tue 8

Wed 9

now

GitHub API Requests

Thu 3

Fri 4

Sat 5

Sun 6

Mon 7

Tue 8

Wed 9

now

GitHub Packages

Thu 3

Fri 4

Sat 5

Sun 6

Mon 7

Tue 8

Wed 9

now

GitHub Webhooks

Thu 3

Fri 4

Sat 5

Sun 6

Mon 7

Tue 8

Wed 9

now

Atlassian Bitbucket API

Thu 3

Fri 4

Sat 5

Sun 6

Mon 7

Tue 8

Wed 9

now

Atlassian Bitbucket Source downloads

Thu 3

Fri 4

Sat 5

Sun 6

Mon 7

Tue 8

Wed 9

now

Atlassian Bitbucket Webhooks

Thu 3

Fri 4

Sat 5

Sun 6

Mon 7

Tue 8

Wed 9

now

Semaphore CI Status

Real-time updates of Semaphore CI issues and outages

Semaphore CI status is Operational

Semaphore CI Semaphore

You're checking on Semaphore CI - but is your own site converting?

Active Incidents

Recently Resolved Incidents

Semaphore CI Outage Survival Guide

Semaphore CI Components

Semaphore CI

Semaphore CI Semaphore

Semaphore CI Upstream Services

GitHub API Requests

GitHub Packages

GitHub Webhooks

Atlassian Bitbucket API

Atlassian Bitbucket Source downloads

Atlassian Bitbucket Webhooks

Semaphore CI Alternatives

CircleCI

CodeShip

Travis CI

Buildkite

Cloudsmith

Bitrise CI

Doppler

CloudRepo

Commonly Used Together

NUXOA

Coralogix

Mergify

Eloquent Technologies

New Relic

Code Climate

Bitbar Testing Cloud

Codecov

CloudAMQP

Fly.io

Inngest

ngrok