I mean that's the genuine cause of most outages. People test code changes in multiple environments but make configuration changes on prod (assuming they even have a staging environment for their config, which is rarely).
Thats true! But thats sort of like saying there was an accident on the highway because 2 cars crashed. There are lots of ways a configuration change could disrupt service, all I am getting at in my previous comment was having even more transparency when stuff like this happens instead of boilerplate statements about config changes, is something I would appreciate and this would give me more confidence in the dev team as well.
