In May, GitHub.com experienced three significant incidents affecting service availability. On May 20, increased CPU utilization due to a permissive API throttling configuration caused latency and errors in the GitHub Container registry, which was mitigated by throttling requests and resetting the database state. On May 27, two separate incidents further affected services like GitHub Actions and API requests, with investigations still ongoing. A follow-up to an April incident revealed that a code change in the billing pipeline mistakenly inflated charges for GitHub Actions and Codespaces, resulting in incorrect billing and service disruption. This was addressed by reverting the change, repairing data, and implementing stricter code review processes. GitHub is committed to improving service reliability and keeping users informed through updates and their status page.