The recent massive outage of GitHub has highlighted its critical role in global software engineering, as it serves as a fundamental platform for hosting code repositories, running build pipelines, and more for countless organizations. The disruption underscores GitHub's integral part in the software productivity chain, where outages can halt code changes and impede responses to other system outages, similar to an AWS Availability Zone failure. This incident emphasizes the importance of monitoring GitHub and other third-party tools as part of an organization's observability strategy, as their operational statuses are crucial for maintaining system functionality. The article suggests that contextual data, such as status pages, Slack messages, and CI/CD logs, is invaluable for understanding and responding to such disruptions, advocating for a comprehensive approach to observability that integrates diverse data sources.