How to say “Politely describe non-functional status” professionally

Level 1: The system is currently exhibiting unexpected behavior, preventing the successful completion of the requested operation. We are investigating the root cause and will provide an update once functionality is restored or a workaround is identified.

Level 2: We've encountered a temporary cessation of expected functionality with the [specific system/feature], which is currently impacting progress. Further investigation is underway to diagnose the anomaly and determine the optimal path forward; your input on potential workarounds would be appreciated.

Level 3: Regrettably, the [system/feature] is presently demonstrating a non-nominal operational state, which, as per the established project documentation from Q3, was contingent upon [missing resource/prioritized task]. We are awaiting the resolution of these external dependencies to proceed with the activation sequence.

Level 4: The [system/feature] is not functional. This issue stems from [specific, verifiable reason, e.g., 'the missing server allocation from the last budget review' or 'a critical dependency not delivered on time']. Until this core issue is resolved, progress on [impacted task] remains halted, impacting our Q-end metrics.

Level 5: It's broken. Again.

Level 1: We've identified a temporary interruption in service for [specific feature/system] which is currently impacting its functionality. Our team is actively investigating and prioritizing a resolution, and we will provide an update within [timeframe].

Level 2: The [system/feature] is currently experiencing an unexpected operational anomaly, preventing it from performing as designed. We are deploying our full resources to diagnose and mitigate this issue, and we will keep you informed of our progress and expected restoration timeline.

Level 3: Regarding the reported behavior of the [feature], it appears to be performing precisely within the parameters of its current non-operational state. As per the original Statement of Work, this functionality was contingent upon [missing client-side data/resource allocation], which remains outstanding.

Level 4: The [system/feature] is not working because [clear, concise, factual reason, e.g., 'critical data was not provided by your team on the agreed-upon date' or 'there is a dependency on an external API which is currently down, as per their status page']. We require [specific action from client or external party] to proceed.

Level 5: It's your problem now.

Level 1: I've tried accessing the [tool/resource], but it appears to be currently non-responsive. Could you confirm if you're experiencing similar issues, or if there's a specific workaround I should be aware of?

Level 2: The [shared tool/system] seems to be experiencing a temporary operational hiccup on my end, making [specific task] impossible. Before I escalate, have you encountered this recently, or is there a known procedure for restoring its functionality?

Level 3: Just confirming that the [critical shared resource] is currently exhibiting what one might charitably call 'suboptimal performance,' effectively nullifying my ability to perform [your part of the task]. Perhaps its status was updated in a channel I've yet to discover?

Level 4: The [tool/system] you expect me to use is down. This directly prevents me from completing my segment of [task X]. Please advise on a functional alternative or an ETA for repair, as my deliverables are now blocked.

Level 5: It's broken. Fix it.