GitHub experienced a significant service disruption lasting over 24 hours due to a routine maintenance error that caused a network partition between their US East Coast network hub and data center, resulting in connectivity issues and a cascade of database replication challenges. Despite the restoration of connectivity within seconds, the incident led to degraded services, including delayed webhook events and GitHub Pages builds, as the company struggled to reconcile data inconsistencies between its data centers. GitHub prioritized data integrity over rapid recovery, opting to preserve user data by failing-forward to its West Coast data center, which introduced additional latency and service delays. The company has initiated technical and organizational improvements, such as adjusting the configuration of its Orchestrator tool and accelerating its migration to a new status reporting mechanism. Additionally, GitHub is advancing a project to support active traffic management across multiple data centers, aiming for greater resilience against single data center failures. Throughout the incident, GitHub maintained transparency with users and is committed to learning from this event to enhance its service reliability and communication strategies.