In 60 seconds
- Maintenance usually has a planned window and expected impact.
- An outage is unplanned and its scope or cause may change during investigation.
- Resolved does not always mean every region and queued request recovers instantly.
Read the timeline, not only the headline
A planned maintenance notice should identify a start time, expected duration, and affected service. An incident notice usually moves through states such as investigating, identified, monitoring, and resolved as the operator learns more.
Check the time zone and the exact component. Login, matchmaking, payments, and voice can fail independently, so a green overall headline may hide a narrower active incident.
What ‘resolved’ can mean
Resolved normally means the operator believes the incident has been fixed, but caches, queues, regional infrastructure, or already-failed requests can take additional time to clear. Look for a final update and any instructions for affected users.
If no official incident exists, compare another device or network before reinstalling. Preserve the error code and time because those details make a support report more useful.
Quick checklist
Confirm whether the notice is planned or unplanned
Check the time zone and affected component
Read the full sequence of incident updates
After resolution, check for residual-impact instructions
What is confirmed — and what needs caution
- Status pages can report individual components separately.
- Planned maintenance may still involve a period of service unavailability.
- An estimated end time can change.
- Do not treat an unofficial screenshot as the current status notice.
Primary sources
01Issueureum summarizes public source material in its own words. Product names belong to their respective owners. Check the linked official source for current details.