Home Root causes Software bug Software bug A latent defect in the vendor’s own software surfaced.
Incidents per month
December 2025 November 2026
Incidents Major Sep 17, 17:54 UTC
Minor Sep 15, 18:57 UTC
Notice Sep 3, 18:20 UTC
Minor Aug 28, 15:41 UTC
Minor Aug 19, 14:21 UTC
Notice Aug 18, 18:51 UTC
Minor Aug 8, 19:48 UTC
Critical Aug 6, 15:22 UTC
On August 6, 2026, between 15:05 UTC and 00:14 UTC on August 7, GitHub Actions experienced degraded availability. Major Jul 23, 14:14 UTC
Notice Jun 17, 19:00 UTC
Minor May 28, 01:13 UTC
Major May 11, 15:05 UTC
Critical May 8, 09:46 UTC
Minor Apr 30, 20:13 UTC
Minor Apr 28, 13:59 UTC
Minor Apr 23, 19:50 UTC
Notice Apr 13, 20:31 UTC
Critical Feb 16, 14:10 UTC
Minor Feb 6, 17:49 UTC
Minor Jan 16, 23:53 UTC
Major Jan 12, 10:02 UTC
Notice Dec 11, 2025, 20:49 UTC
Notice Nov 14, 2025, 18:50 UTC
Major Aug 5, 2025, 00:00 UTC
A context window routing error from August 5, an output corruption misconfiguration from August 25 and a TPU compiler bug from August 26 overlapped, degrading some responses. Minor Mar 11, 2025, 23:59 UTC
Minor Feb 20, 2024, 15:32 UTC
Major Feb 14, 2024, 16:05 UTC
Critical Feb 13, 2023, 04:18 UTC
Critical Jun 8, 2021, 09:47 UTC
A software deployment on May 12 introduced a bug that a specific customer configuration could trigger. Major Oct 8, 2016, 00:00 UTC
Questions How common are outages caused by software bug? 22 incidents in the last 12 months across the vendors tracked here were traced to software bug in the vendors' own words.
How is this cause identified? From the sentences where the vendor explains why the incident happened, or by hand for landmark postmortems. Symptoms like "elevated error rates" are never counted as a cause.
Incidentsby Glyph
Fastly: Customer configuration triggers latent bug, 85% of network errorsA software deployment on May 12 introduced a bug that a specific customer configuration could trigger.lasted 2h 48mBugPostmortem