Semaphore: Delays in job processing
Affected components: Semaphore
Timeline of updates
- investigating
We are currently investigating this issue.
- identified
The issue has been identified and a fix is being implemented.
- identified
We are continuing to work on a fix for this issue.
- identified
We’ve identified network connectivity issues between our control plane and build servers. We’re actively working to restore normal service.
- identified
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
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
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
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
We are continuing to work on a fix for this issue.
- identified
We are continuing to work on a fix for this issue.
- identified
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
We are continuing to work on a fix for this issue.
- identified
Our team is continuing to work on a fix for this issue.
- identified
We are continuing to work on a fix for this issue.
- identified
Our engineering team is actively working to resolve this issue.
- monitoring
A fix has been implemented and we are monitoring the results.
- monitoring
We are continuing to monitor for any further issues.
- monitoring
Our team is still monitoring the results.
- resolved
This incident has been resolved.
Changes Rewindex caught on this incident
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured 18:53 UTC
In the 2026-10-19 checkpoint, timestamped by FreeTSA and DigiCert on Oct 20, 00:41 UTC. Record hash
7700ca6a50b98e67…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).