GitHub started grading its own homework in public
The June availability report keeps the transparency section, admits a month-long deliberate pause, and reports a missed 50% target with no new date attached. More of this, everywhere.
GitHub's availability report for June is the second edition to carry the infrastructure section the company added in May, and the first real test of what the format is for. The response to that first outing, per the report, was that customers want more of it, not less, including when the news is mixed. June obliged: progress on structural work, a traffic ramp paused on purpose for roughly a month after a May 21 stability incident, and a missed 50% migration target reported with no replacement date attached.
This is rarer than it should be. The industry default for reliability communication is the incident report (obligatory, episodic) and the uptime page (a decimal, context-free). A monthly self-grading that says "we paused this on purpose" and "we missed that and have no new target to announce" occupies the honest middle ground almost nobody publishes in, for the obvious reason: it creates a public record that gets quoted back later.
Which is precisely its value, and not only for customers. Teams inside companies that publish such records get something too: an argument-settling artifact when reliability work competes with features for headcount.
The builder's read: steal the format for your internal platform. A monthly one-pager, progress and pauses and missed targets included, costs an hour and buys the thing dashboards never deliver, which is believed status.