Community launches satirical tracker to visualise GitHub outages
Developers have created a satirical contribution graph hosted at red-squares.cian.lol to track GitHub.com service interruptions, offering a visual alternative to the usual code commit metrics.
A community-driven initiative known as Red Squares has been launched to visualise disruptions on the GitHub.com platform. The project operates by replacing the standard green squares found on a user's contribution graph with red ones, effectively mapping outage events rather than code commits.
The concept satirises the typical use of the contribution graph, which usually displays green squares to indicate days where a user has made at least one commit. By inverting this visual language, the project highlights periods when the service is unavailable, drawing attention to the periodic service disruptions that are not typically tracked in the same visual format as active development.
The initiative was announced on Hacker News under the Show HN format, where the creator shared the live URL for the tracker. The project is currently hosted at red-squares.cian.lol, allowing users to view a timeline of platform issues presented in the familiar grid layout of a contribution graph.
It is important to note that the project is explicitly described as satirical. The red squares do not represent verified outage data from an official GitHub status page but rather serve as a community-driven visualisation. Consequently, the reliability of the tracker as a factual record of outages should be treated with caution compared to official status channels.
While the visualisation provides a creative response to periodic service interruptions, specific details regarding the frequency or duration of the outages tracked in this instance are not detailed in the source text. Furthermore, the scope of the tracker beyond the general platform is not explicitly defined in the available information.
This community response underscores the ongoing relationship between developers and the infrastructure they rely upon. By repurposing a standard metric for code activity to highlight service failures, the project offers a unique perspective on platform stability without relying on official reporting mechanisms.
