GitHub increases infrastructure capacity to manage automated traffic growth

Outages

GitHub increases infrastructure capacity to manage automated traffic growth

GitHub is adding four million processor cores to its infrastructure to handle a significant increase in automated traffic. The expansion is designed to prevent service interruptions caused by the rising volume of AI-generated code and bot activity.

All news
Outages
28 October 2026

What this means for your business

Businesses that host their own software or use GitHub for automated website updates may face intermittent stability issues while these changes are implemented. You should ensure your development teams have local backups of critical repositories to maintain operations during potential outages.

Infrastructure expansion to prevent downtime

GitHub has announced a significant increase in its hardware capacity, adding four million processor cores to its global infrastructure. This move is a response to the growing volume of automated traffic, often referred to as 'AI slop,' which has begun to strain the platform's existing resources. For UK businesses that use GitHub to store their code or manage software projects, this update is intended to ensure the service remains stable.

The cause of increased server load

The platform has seen a sharp rise in activity from automated bots and AI tools. These tools frequently submit, test, and update code at a scale that exceeds typical human usage. This high volume of requests can lead to site-wide slowdowns or complete outages, preventing staff from accessing the files they need to work. By increasing the number of cores—the individual processing units within a server—GitHub aims to process these requests without impacting regular users.

Technical restructuring

Alongside the hardware increase, GitHub is re-architecting parts of its system to better distinguish between human users and automated processes. While the specific technical details of this internal restructuring have not been fully disclosed, the goal is to prevent a surge in bot activity from affecting the user interface used by staff. This is a preventative measure following several instances of service instability over the past year.

Considerations for your business

If your business relies on GitHub for daily operations, you may notice brief periods of maintenance as these changes are rolled out. It is standard practice to maintain local copies of your code, but this serves as a reminder to verify that your backup processes are functioning. If the service does experience an outage, your developers will be unable to 'push' (upload) or 'pull' (download) updates, which can delay software releases or website fixes until the service is restored.

Would you have noticed before your staff did?

Our support plans include monitoring and a team that handles provider outages for you. Price one up in about a minute.

Price your IT support

Not sure how exposed you are?

Twenty minutes on a call is usually enough to tell you.