Incidentsby GlyphRoot cause
Configuration change
A setting, policy, feature flag or config file pushed to production broke something.
Incidents per month
December 2025November 2026
103
in 12 months
42
major or critical
56m
median duration
most affected
Incidents
AWS: Elevated packet losslasted 2h 42mConfig changeAWS: Elevated Packet Losslasted 1h 21mConfig changeAWS: Inaccurate Estimated Billing Datalasted 29h 24mConfig changeAWS: Increased Error Rates and Latencieslasted 51mConfig changeAWS: Elevated latencies for network change propagationlasted 2h 8mConfig changeQuestions
How common are outages caused by configuration change?
103 incidents in the last 12 months across the vendors tracked here were traced to configuration change 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.