Twenty scenarios drawn from failures engineers actually hit. Read the symptom, commit to a cause, then see the diagnostic order that would have found it faster.
Area:
Showing: 0
Diagnostic Order
Six checks in the order that finds a cause fastest. Almost every cloud failure is one of these, and checking them out of order is how afternoons disappear.
The principle underneath the order is cost. Each check is cheaper than the one after it and rules out a whole class of causes. Guessing at configuration before confirming identity means you may spend an hour tuning something that was never reachable, and that mistake is the single most common time sink in cloud support work.
Symptom Reference
What common failure signatures usually mean, and the first thing to check for each. Exact wording changes between services and over time, so match on the shape rather than the string.
Showing: 0
Cloud platforms change. Service names, error text, default behaviours, and portal layouts all move, and a message that means one thing today may be reworded next quarter. Everything here is written around the underlying cause rather than the exact string, and you should still confirm against current official documentation before acting on production.
My Progress
What you have attempted and how you did. Everything stays in your browser.