Looking for an update now? Check the current status, or follow Namespace for future changes.
78.9%of 38 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
76.7%
30
7
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 3Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
No source-attested incident records are available for the current collector history. Older legacy archive records remain available below.
Legacy Incident Archive
53 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
August 2026
Elevated queue time for a small set of GitHub Action jobs
Source not attested
Last archived state: resolved
View archived record details
monitoring
We are still seeing a low rate of jobs not getting assigned to runners timely by GitHub.
Runners are starting timely and register successfully with GitHub.
If you encounter that your job is not getting picked up, we recommend retrying it on GitHub, as the overall impact rate of this issue is low.
monitoring
We're seeing a wider, but still low impact due to this issue. GitHub is not reporting any incident.
investigating
We are seeing a very small subset of jobs experiencing elevated queue time.
Newer runs of the same workflows are picking up runners with no delay.
GitHub is not reporting an incident so far.
Elevated error rate from GitHub API
Source not attested
Last archived state: resolved
View archived record details
monitoring
A small set of jobs are still seeing elevated queue times due to ongoing impact from <https://www.githubstatus.com/incidents/zkxwbgr0cnmx>
resolved
GitHub has closed their incident and we confirm seeing recovery across the board.
investigating
Upstream incident: <https://www.githubstatus.com/incidents/zkxwbgr0cnmx>
A subset of GitHub Action jobs are seeing elevated queue times as a consequence.
Some IAM calls are failing
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Mitigation has been applied. We continue to monitor.
identified
Our team is still working through applying mitigation.
identified
We've identified the issue and are working through deploying a mitigation.
Increased queue time for subset of GitHub jobs
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Most of the backlog of jobs has been processed, any new jobs continue being processed as normal.
We continue to monitor for complete processing of the backlog.
identified
There was a brief interruption on event ingestion leading to some jobs seeing increased queue time.
We're catching up on any missed jobs and new jobs are being processed as normal.
Elevated error rate in our control plane
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Our fix has rolled out and we are seeing signs of recovery. The team continues to monitor the situation.
identified
We have identified the issue, and it is focused on IAM, our team is working on mitigation.
investigating
We're seeing an elevated error rate in our control plane. The team is investigating.
Elevated errors during logs serving
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have applied a mitigation and see first signs of recovery. We are monitoring the situation.
investigating
We are seeing an elevated error rate on our log serving endpoints. The team is investigating.
Delayed startup for macOS instance
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
The fix has been rolled out and startup times have recovered.
investigating
We're seeing increased startup times for a subset of macOS instances, the team is rolling out a fix.
Increased error rate from GitHub
Source not attested
Last archived state: resolved
View archived record details
monitoring
We believe that this incident is largely mitigated.
We still see an elevated job assignment latency for a small subset of jobs, but other symptoms have resolved meanwhile.
GitHub is reporting their updates in <https://www.githubstatus.com/incidents/qcvjkzcs7j74>
monitoring
We are seeing first signs of partial recovery but the incident is still ongoing and many jobs are still seeing elevated queue times.
GitHub is tracking their updates in <https://www.githubstatus.com/incidents/qcvjkzcs7j74>
identified
We're seeing more widespread impact, with runners unable to acquire jobs. This is leading to increased queue times for a subset of jobs.
GitHub is tracking this at <https://www.githubstatus.com/incidents/qcvjkzcs7j74>
