All Systems Operational

Semaphore Operational
90 days ago
100.0 % uptime
Today
Upstream Services Operational
GitHub API Requests Operational
GitHub Packages Operational
GitHub Webhooks Operational
Atlassian Bitbucket API Operational
Atlassian Bitbucket Source downloads Operational
Atlassian Bitbucket Webhooks Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Feb 17, 2026

No incidents reported today.

Feb 16, 2026

No incidents reported.

Feb 15, 2026

No incidents reported.

Feb 14, 2026

No incidents reported.

Feb 13, 2026

No incidents reported.

Feb 12, 2026

No incidents reported.

Feb 11, 2026

No incidents reported.

Feb 10, 2026

No incidents reported.

Feb 9, 2026

No incidents reported.

Feb 8, 2026

No incidents reported.

Feb 7, 2026
Completed - The scheduled maintenance has been completed.
Feb 7, 11:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 7, 09:00 UTC
Scheduled - Semaphore will be temporarily unavailable during this scheduled maintenance on Saturday.
Feb 3, 13:56 UTC
Feb 6, 2026

No incidents reported.

Feb 5, 2026
Resolved - This incident has been resolved.
Feb 5, 17:28 UTC
Identified - The issue has been identified and a fix is being implemented.
Feb 5, 16:28 UTC
Feb 4, 2026
Resolved - This incident has been resolved.
Feb 4, 18:10 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 4, 17:40 UTC
Identified - The issue has been identified and a fix is being implemented.
Feb 4, 16:38 UTC
Feb 3, 2026
Resolved - This incident has been resolved.
Feb 3, 19:50 UTC
Monitoring - GitHub has posted an update indicating recovery of the aforementioned issue. We continue monitoring Semaphore closely as things stabilize.

(GitHub Status: https://www.githubstatus.com/incidents/f314nlctbfs5)

Feb 3, 19:11 UTC
Identified - Webhook delivery delays between GitHub and Semaphore appear to be caused by degraded performance on GitHub’s side. GitHub is currently reporting an active incident that appears related. We are monitoring the situation closely and will provide updates as GitHub resolves the issue.
Feb 3, 17:34 UTC
Investigating - We are currently investigating this issue.
Feb 3, 15:46 UTC
Resolved - This incident has been resolved.
Feb 3, 19:24 UTC
Monitoring - We’re seeing considerable improvement in internal performance metrics, and we will continue monitoring until conditions fully stabilize.
Feb 3, 18:52 UTC
Investigating - Webhook delivery delays from GitHub led to a backlog of workflows being triggered all at once as delivery resumes. This caused a temporary spike in demand for some Semaphore machines.

We are actively working to reduce the impact and restore normal capacity. We continue monitoring both GitHub’s incident and Semaphore infrastructure closely, and we will provide further updates as conditions stabilize.

Feb 3, 18:06 UTC