Semaphore experienced a critical incident on August 31, 2026 affecting Semaphore, lasting 10h 4m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 31, 2026, 12:06 PM UTC
We are currently investigating this issue.
- identified Aug 31, 2026, 12:56 PM UTC
The issue has been identified and a fix is being implemented.
- identified Aug 31, 2026, 02:10 PM UTC
We are continuing to work on a fix for this issue.
- identified Aug 31, 2026, 03:32 PM UTC
We’ve identified network connectivity issues between our control plane and build servers. We’re actively working to restore normal service.
- identified Aug 31, 2026, 04:01 PM UTC
We’re still working to resolve the network connectivity issues between our control plane and build servers. We’ll share another update as soon as we have more information.
- identified Aug 31, 2026, 04:34 PM UTC
We’re still working to resolve the network connectivity issues between our control plane and build servers. We’ll share another update as soon as we have more information.
- identified Aug 31, 2026, 05:17 PM UTC
We’re still working to resolve the network connectivity issues between our control plane and build servers. We’ll share another update as soon as we have more information.
- identified Aug 31, 2026, 05:48 PM UTC
We’re still working to resolve the network connectivity issues between our control plane and build servers. We’ll share another update as soon as we have more information.
- identified Aug 31, 2026, 05:50 PM UTC
We are continuing to work on a fix for this issue.
- identified Aug 31, 2026, 05:58 PM UTC
We are continuing to work on a fix for this issue.
- identified Aug 31, 2026, 06:22 PM UTC
We’re still working to resolve the network connectivity issues between our control plane and build servers. We’ll share another update as soon as we have more information.
- identified Aug 31, 2026, 06:48 PM UTC
We are continuing to work on a fix for this issue.
- identified Aug 31, 2026, 07:21 PM UTC
Our team is continuing to work on a fix for this issue.
- identified Aug 31, 2026, 07:49 PM UTC
We are continuing to work on a fix for this issue.
- identified Aug 31, 2026, 08:18 PM UTC
Our engineering team is actively working to resolve this issue.
- monitoring Aug 31, 2026, 08:35 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Aug 31, 2026, 09:09 PM UTC
We are continuing to monitor for any further issues.
- monitoring Aug 31, 2026, 09:44 PM UTC
Our team is still monitoring the results.
- resolved Aug 31, 2026, 10:11 PM UTC
This incident has been resolved.