Digital literacy · 2026-10-29
One App Failure Does Not Establish a Service Outage
“It did not work for me at this time” describes one person's experience. “The service is unavailable to everyone” is a wider claim that needs wider evidence. A reposted screenshot does…
“It did not work for me at this time” describes one person's experience. “The service is unavailable to everyone” is a wider claim that needs wider evidence. A reposted screenshot does not close that gap.
Identify the source of each statement
A participant’s report describes that participant’s experience. A service announcement makes a statement on behalf of its publisher, provided the source can be authenticated. Neither should be silently presented as the other.
Dates limit relevance
An old maintenance notice does not establish today’s status. Record its publication date, the period it describes and the affected scope. A message about one feature should not become a claim about every feature.
When no current announcement is available, say that the incident is a personal report and the wider status is unconfirmed. Multiple reposts of one notice do not provide independent confirmation.
The announcement's affected feature matters
A notice about history display does not establish that account access, every game and every record are unavailable. Quote the affected feature in the incident summary. If the notice has an end time, keep that time with the original date rather than treating the announcement as permanently current. A precise scope is more useful than a dramatic outage headline.
Compare separate reports without merging them
Two people can describe similar failures at different times or in different features. Keep each report’s time and affected feature attached to it. Agreement on those details makes a comparison more meaningful; disagreement may show that the reports concern different incidents. Neither case requires turning personal observations into an announcement on behalf of the service.