Website QA intelligence for teams who ship
⚲
Guides Tool Comparisons QA Glossary Archive RSS Feed
heads-up platform & cms 3 sources 1 min read

GitHub Billing Reports and Audit Logs Hit by Multiple Outages

What happened

GitHub experienced three separate service disruptions between March 31 and April 1, 2026. The billing usage reports feature was degraded for over nine hours due to reduced server capacity, preventing customers from accessing usage data for organizations and repositories. A failed credential rotation caused audit log services to become unavailable for 28 minutes, returning 5xx errors via both API and web interface. Additionally, code search functionality was completely unavailable for over two hours following a failed Kafka cluster upgrade.

Business impact

Enterprise teams using GitHub for development workflows faced significant compliance and operational risks. The audit log outage created gaps in security monitoring and compliance documentation required by SOX, PCI-DSS, and other regulatory frameworks. Billing report failures prevented cost tracking and budget oversight for large development organizations managing multiple repositories and teams.

Background

GitHub serves as the primary code repository for most enterprise development teams, making service reliability critical for continuous integration and deployment pipelines. Audit logs are particularly important for regulated industries that must maintain complete records of code access and modifications. The concentration of multiple unrelated failures within a 24-hour period suggests potential infrastructure or operational process issues at GitHub.

What this means for your team

Implement local backup processes for critical GitHub audit data using the API during normal operations to maintain compliance records during outages. Set up alternative code search tools like Sourcegraph or internal indexing systems to prevent development delays. Review GitHub service level agreements and consider implementing monitoring alerts for GitHub's status page to proactively communicate potential delays to stakeholders and compliance teams.

What to watch

Monitor GitHub's transparency around infrastructure improvements and whether similar clustered outages occur in the coming months. Track any updates to GitHub Enterprise Server releases that might address these reliability concerns for on-premises deployments.

Sources

Related stories