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.
July 2026
SSO login experiencing errors
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We're seeing errors rates partially recover, a small subset of requests might still be affected.
investigating
Our provider for SAML based SSO logins is experiencing platform errors. Our team is following up on this issue.
Impact to multiple services
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Mitigation has been applied and see recovery.
investigating
Our team is investigating partial failures served by some of our services.
Increased error rate from GitHub resulting in increased queue time
Source not attested
Last archived state: resolved
View archived record details
monitoring
We're seeing an increased upstream error rate when runners try to acquire a job from GitHub, leading to increased queue time for a subset of jobs.
We expect this to be a result of increased pressure due to <https://www.githubstatus.com/incidents/cstx3v63mklm>
Our team is monitoring the situation.
Failure to read blobs in one of the Virginia locations
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Affecting Registry and Devboxes.
June 2026
Increase in queue time across GitHub jobs
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
All systems are operational.
monitoring
GitHub has resumed normal event generation, we're monitoring.
identified
GitHub event generation slowed down dramatically. Our platform continues to handle jobs, but job discovery is slowed down due to a lack of fresh events.
investigating
Our team is investigating.
Elevated queue time for GitHub Actions
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The issue has been resolved. New jobs are confirmed to start fine, and we are working through the backlog of affected jobs.
investigating
We see elevated queue time for GitHub Actions. The team is investigating.
Elevated error rate for container registry
minorSource not attested
Last archived state: resolved
View archived record details
investigating
A subset of pushes to the container registry encountered errors. We are investigating.
Increased queue time for GitHub Jobs
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Pressure on one of our systems caused us to be unable to process all events,
leading to some jobs not being picked up in a window of 20 minutes.
We're seeing recovery and new jobs are being picked up as normal,
we're working on reconciling the backlog of jobs that were missed in this window.
investigating
We're investigating increased queue time for GitHub jobs
Invalid GitHub events leading to job queuing
Source not attested
Last archived state: resolved
View archived record details
monitoring
We reached out to GitHub and they rolled back the experiment that led to the outage.
We are seeing signs of recovery.
We are still working through the backlog of affected jobs, but new jobs are good already.
identified
We are working on reconciling the missed state from the invalid events.
We are also working on an alternative ingestion path to handle the corrupt event data gracefully.
investigating
GitHub has been sending invalid job payloads which lead to jobs not being picked up. Our team is investigating.
Elevated error rate in GitHub event ingestion
Source not attested
Last archived state: resolved
View archived record details
monitoring
We're currently seeing healthy ingestion again, with all new jobs being picked up normally.
monitoring
We again see webhooks being delivered with malformed data, making it impossible to ingest these events.
This will lead to increased queue time for a subset of jobs, as we're only able to discover these jobs through secondary ingestion paths.
monitoring
We have confirmed that GitHub was issuing malformed event data for a subset of events.
This issue has resolved now.
New jobs already start fast consistently, we are working through the backlog of affected jobs.
investigating
We see an elevated error rate in event ingestion from GitHub - we are investigating.
