# GitHub audit logs are unavailable

- Provider: [GitHub](https://down.guide/providers/github)
- Confidence: Confirmed
- Impact: Partial outage
- lasted 4m
- started 2026-04-01 16:06 UTC
- GitHub states the impact was 2026-04-01 15:34 to 16:02 UTC (28m)
- id: DWN-2c4f1c6c12
- Official page: https://stspg.io/vs91g30yd70s

## Root cause
> On April 1, 2026, between 15:34 UTC and 16:02 UTC, our audit log service lost connectivity to its backing data store due to a failed credential rotation.

[Postmortem](https://stspg.io/vs91g30yd70s)

## Updates from GitHub
### 2026-04-01 16:06 UTC: investigating
We are investigating reports of impacted performance for some GitHub services.

### 2026-04-01 16:07 UTC: investigating
A routine credential rotation has failed for our our audit logs service; we have re-deployed our service and are waiting for recovery.

### 2026-04-01 16:10 UTC: resolved
On April 1, 2026, between 15:34 UTC and 16:02 UTC, our audit log service lost connectivity to its backing data store due to a failed credential rotation. During this 28-minute window, audit log history was unavailable via both the API and web UI. This resulted in 5xx errors for 4,297 API actors and 127 github.com users. Additionally, events created during this window were delayed by up to 29 minutes in github.com and event streaming. No audit log events were lost; all audit log events were ultimately written and streamed successfully. Customers using GitHub Enterprise Cloud with data residency were not impacted by this incident. 
We were alerted to the infrastructure failure at 15:40 UTC — six minutes after onset — and resolved the issue by recycling the affected environment, restoring full service by 16:02 UTC. We are conducting a thorough review of our credential rotation process to strengthen its resiliency and prevent recurrence. In parallel, we are strengthening our monitoring capabilities to ensure faster detection and earlier visibility into similar issues going forward.

From the builder: does your app depend on GitHub? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=github) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention GitHub.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-2c4f1c6c12), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.