Users attribute the prolonged Microsoft 365 outage to either recent layoffs and AI-assisted coding degradation or complex traffic management failures, with disagreement over whether the root cause was systemic design flaws or simple negligence. While some claim corporate mismanagement led to instability, others argue that cascading failures in distributed systems are inherently difficult to test for and recover from.
635 readable replies · Supporting reply 1 · Supporting reply 2 · Supporting reply 3 · Supporting reply 4customer-terms
github-online-services-sla
HISTORICAL RECORD2023–2026
customer-terms / github-online-services-sla · Not publicly available
github-online-services-sla
Discover this repository through its Hacker News conversations.
6Distinct people
7Mentions
0Explicit recommenders
What to know before exploring
What it is
A public description has not been verified.
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.
Mentions over time
HN mentions by year7 dated mentions
Observed mentions: 2023-05-09 12:22:16 UTC to 2026-08-17 19:49:12 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 5 | 1 | 4 |
What Hacker News says
7 sourcesERer0k·Aug 17, 2026Submission
1 points · Open discussionEeh, you always rely on someone else's infrastructure. Even if you are off cloud entirely and own your own datacenter, you still need peering/transit. You still need power (or at least fuel). You can't avoid depending on a DNS infrastructure.
Github does have an SLA: https://github.com/customer-terms/github-online-services-sla. But like virtually all SLAs, it's really just a token gesture. I have never seen an SLA that pays the losses you suffer due to the outage.
In Incident with Github.com [resolved]People are already saying things like "We need a plan B in case we urgently need to deploy a fix to production, and GitHub Actions is unavailable again".
But in general, it's not feasible to do everything in house.
And I don't think that GitHub is devoid of SLA: https://github.com/customer-terms/github-online-services-sla
The issue is that they're not achieving two nines uptime in practice.
In Incident with Github.com [resolved]> I've felt like its a little unfair to judge the uptime of company platforms like this; by saying "if any feature at all is down, its all down" and then translating that into 9s for the platform.
This is definitely true.
At the same time, none of the individual services has hit 3x9 uptime in the last 90 days [0], which is their Enterprise SLA [1] ...
> "Uptime" is the percentage of total possible minutes the applicable GitHub service was available in a given calendar quarter. GitHub commits to maintain at least 99.9% Uptime for the applicable GitHub service.
[0]: https://mrshu.github.io/github-statuses/
[1]: https://github.com/customer-terms/github-online-services-sla
(may have edited to add links and stuff, can't remember, one of those days)
In GitHub appears to be struggling with measly three nines availabilitymore context -- their enterprise SLA is 99.9% (3x9) uptime for individual services
https://github.com/customer-terms/github-online-services-sla
> GitHub commits to maintain at least 99.9% Uptime for the applicable GitHub service.
... and none of the individual services have hit 99.9% uptime in the last 90 days according to this site. 0_o
In GitHub appears to be struggling with measly three nines availabilityGithub doesn't claim "five nines of reliability".
There SLA is for 99.9% ("three nines").
Which equates to:
Daily: 1m 26s
Weekly: 10m 4.8s
Monthly: 43m 28s
Quarterly: 2h 10m 24s
Yearly: 8h 41m 38s
https://github.com/customer-terms/github-online-services-sla
In Incident with Actions, API Requests, Codespaces and PagesInterested to hear whether anyone actually managed getting some Client Credits as per their SLA [1]? Over the last quarter they probably went sub 99.9% in some services.
[1] https://github.com/customer-terms/github-online-services-sla
In GitHub incident: ongoing issues with Actions, Issues and other Git operations