Outlook access fails across regions. Act as the service responder: restore capacity, test servers under traffic, and recover delayed mail. Based only on Microsoft's incident updates. The system, logs, and measurements are simulated.
- 10 min
- Time limit
- 3
- Incident stages
- Time not documented
- Responders on the day
Free to play. No account or credit card needed.
Each stage brings a new problem. Solve it while keeping earlier fixes working.
This practice result is not saved or shared with a team. Pause stops the clock. If you leave, continue in this browser within 24 hours.
Use Contain incident to limit damage before you identify the cause.
What happened on 12–14 Nov 2026Gives the answer away
- Microsoft: unavailable servers increased load on the remaining capacity; traffic had not surged.
- Microsoft paused deployments and shifted traffic away from affected infrastructure.
- Microsoft tested an alternative health check and returned a subset of servers to service.
- Microsoft found restarted servers could become unresponsive again when traffic returned.
- Microsoft isolated servers, restarted components, and tested stability as traffic returned.
- Microsoft extended the email timeout to 48 hours to help preserve delayed mail.
- Microsoft expanded recovery gradually and monitored email queues and remaining regional impact.
- Microsoft linked the issue to an earlier network capacity upgrade and a later network change.
- Microsoft described a technical failure unrelated to cyberattacks or AI agents.
- Microsoft later confirmed restoration for the remaining affected customers and regions.
Loss of available servers can overload the remaining capacity without a traffic spike. Validate health checks, then test restarted servers under traffic. Restore traffic gradually and verify stability at each stage. Preserve delayed mail and check delivery separately from mailbox access. Confirm recovery across affected regions and features. The root-cause explanation remains preliminary.