Read service health
Move from the service map to the exact route and observation that matters.
Use the service map
Each node summarizes the routes watched for one Azure service. Select a node to jump to its detailed card. Summary states come from route observations, not a manual incident report.
Inspect impact
- 01Filter
Choose all services, services needing attention, or services with no active notices.
- 02Expand routes
Open Route details to inspect individual surfaces. A degraded route does not mean every part of the product is down.
- 03Inspect time
Hover, focus or tap a timeline point to see its recorded time, state, duration and affected route count.
Know the limits
- Checks refresh every 60 seconds; samples are observations, not continuous proof of availability.
- Checking means a sample is pending. It is not an outage verdict.
- Latency belongs to the probe, not a measurement of your device or game connection.
- A working landing page does not prove an authenticated operation will succeed.
Troubleshooting
When reporting a problem, include the service, route label, observation time and error. Compare your own request with the latest sample; do not send authentication headers or private payloads.