In 2019, to meet GitHub’s growth and availability challenges, we set a plan in motion to improve our tooling and ability to partition relational databases.

How GitHub uses code scanning to increase developer happiness, and how you can too.

In August, we experienced two distinct incidents resulting in significant impact and degraded state of availability for Git operations, API requests, webhooks, issues, pull requests, GitHub Pages, GitHub Packages, and GitHub Actions services.

Over the past months, we’ve left our macOS model behind and moved to Codespaces for the majority of GitHub.com development.

In July, GitHub experienced no incidents resulting in service downtime to our core services.

At GitHub, we recently added a new feature to Rails that will be available in 7.0: support for handling associations across database clusters.

In June, we experienced no incidents resulting in service downtime to our core services.

We recently set about creating a framework and service for automatically generating social sharing images for repositories and other resources on GitHub.

In May, we experienced two incidents resulting in significant impact to multiple GitHub services.

Over the years, GitHub engineers have developed many ways to observe how our systems behave. We mostly make use of statsd for metrics, the syslog format for plain text logs and OpenTracing for request traces.