Yes and that's fine. It's okay to end up with an RCA like that and note that as a known risk. If a cost-benefit analysis shows that the risk is dwarfed by the solution, then it's not worth fixing. Knowing the existing risks of your system and reevaluating these risks in the face of changes (more people available, inefficient context switching, etc) is a key component of making progress.
However, most real life situations I've seen show that there's always room to improve. For example, how quickly did your service recover once the underlying platform recovered. Rare events (like DC failure) can be a bad thing for operational training. Teams forget how to recover. No runbooks, no training, or tooling that's infrequently used no longer works.
You don't just shruggie and move in "that ship has sailed" at least if you're doing it right.
Our service was down.
Why?
Because the platform it runs on went down.
Why only one platform?
Because management declined to approve purchase orders for sufficient hardware to allow redundancy.
---
And your career just hit a wall. Passing the buck up the chain tends to do that.
If your management is bad, then there are a lot more risks to your career than trying to work with them to improve the process. It is more likely that a given employee has dead-ended their career because they don't know how to explain a problem without blaming people and having the humility to see from other people's point of view; both useful skills for getting a promotion.
Is your superior's superior also incompetent? What about his superior? Does your superior have someone else on his level that isn't incompetent? If you genuinely believe the company is top to bottom incompetent then what are you still doing there? Otherwise identify the competent people and start working that angle, either to get yourself transferred under someone more competent or to move critical decision making power from your superior to someone more competent (perhaps yourself)?
Or, if you're that sort of person, find a way to use their incompetence to mask your lack of giving a fuck and just slack and collect a pay check until they fire you.
Our service was down.
Why?
Because the platform it runs on went down.
Why only one platform?
Because management doesn't want us to spend several years engineering for multiple platforms.
---
I find it hard to imagine a realistic path of 5 whys that leads us back to a cause within our own team.