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
Elevated GitHub action error rate
Source not attested
Last archived state: resolved
View archived record details
monitoring
Upstream incident: <https://www.githubstatus.com/incidents/75g5xmzptjqb>
We are seeing an elevated error rate by GitHub, leading to elevated queue time for a subset of jobs.
Partial unavailability of instance metrics
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We see metrics being successfully processed. Traffic is again being routed to the previously affected compute shard and we are monitoring the situation closely.
identified
We understand the root cause and have applied an immediate fix to our metrics system.
investigating
We have rerouted traffic from the faulty compute shard whilst the investigation is ongoing.
investigating
Our telemetry has alerted us about a metrics not being available in one of our compute shards. The team is root causing.
Elevated GitHub actions queue time
minorSource not attested
Last archived state: resolved
View archived record details
identified
We understand the cause and are working towards a fix.
A subset of jobs is seeing multiple minutes of queue time.
investigating
Our telemetry alerted us about elevated GitHub actions queue time. The team is investigating.
Elevated error rate
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
The root count was found and a fix has been rolled out.
We had two points of control plane unavailability, namely:
- 18:16:16 - 18:21:49 UTC
- 18:32:40 - 18:40:05 UTC
The team is monitoring the situation.
investigating
The team is investigating an elevated error rate affecting many subsystems.
Elevated queue time for GitHub action jobs
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Jobs have been picked up across most tenants and GitHub has posted an update that the issue has been resolved. The team is monitoring the siutation.
identified
Namespace is spawning instances successfully but GitHub is having trouble assigning jobs to them. The upstream incident is being tracked at: <https://www.githubstatus.com/incidents/pz7g535gbs6p>
investigating
Our telemetry alerted us about an increase in queue time for GitHub action jobs. The team is investigating.
Elevated queue time for GitHub Actions
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
GitHub reports the issue as mitigated. We see improvements in queing time for most customers. The team is monitoring the situation.
identified
Our telemetry alerted us about extended queing time on a small subset of GitHub Action jobs. The root cause is an an upstream incident that GitHub is tracking at: <https://www.githubstatus.com/incidents/8vfyvq16hzh9>
Elevated queue time for a subset of GitHub jobs
Source not attested
Last archived state: resolved
View archived record details
monitoring
GitHub is sending a subset of webhook events with a delay, leading to elevated queue time for the affected jobs.
Elevated queue time for a subset of GitHub actions jobs
Source not attested
Last archived state: resolved
View archived record details
monitoring
We're seeing signs of improvements here, but still a notable elevated queue time for a subset of jobs.
A large part of the queue has been drained, but not all jobs have been picked up by GitHub yet.
monitoring
We're starting to seeing GitHub Actions jobs being picked up.
identified
Unfortunately there's no resolution on GitHub's outage yet. All jobs are effected.
identified
A GitHub owned GitHub Actions related certificate has expired, which is leading to jobs not being able to be processed.
Github incident: <https://www.githubstatus.com/incidents/8vfyvq16hzh9>
