If you work a job where having one of these incidents once a year or more is "normal" then the dev team needs to devote most of its time to fixing that, or you need to change employers.
Some (many?) employers make this difficult, and you should try to leave them.
What I mean to imply is that it is an issue that is naturally fixed by improved development, and that fixing does require development skill, but the organization can hamstring their developers to prevent them fixing the issue even if they could.
I think my sweet spot is somewhere between once a week and once a month, spread across the whole team.
There are so many systems held together with baling wire it was rare to go a day without a significant outage, usually multiple. Everyone who was remotely knowledgeable about tech was basically a firefighter.
Incidents happen as code changes. Even once you fix it, the changing nature of the code can introduce more issues
If it is unacceptable to cause that downtime, you write code that makes the downtime much less likely
My random guess is that the "downtime" is fairly proportional to the scale difference with megas probably taking the edge.