Service Outage Apology: Verified Status and Update Examples

State the confirmed scope

Name the affected service or function and the checked time context. Avoid guessing how many people are affected. If the scope is still being investigated, say that. The message should remain accurate for people who are seeing a different result, rather than implying every account has the same experience.

Do not publish an unverified cause

An initial explanation may change as the incident is checked. Use only confirmed facts and label uncertainty plainly. Keep internal account details, technical secrets and personal information out of a public statement. An apology can acknowledge disruption without speculating about the cause.

Offer a workaround only if it is checked

Explain any available alternative and its limits. Do not direct people to an unapproved route that creates another problem. If there is no suitable workaround, say so rather than inventing an action to fill the message. Make the official status channel easy to identify.

Continue: Customer ↗

Separate next update from restoration time

You may be able to confirm when you will communicate again without knowing when the service will return. Keep that distinction visible. Once restoration is verified, explain the current state accurately and keep any remaining limitation clear. Do not declare the whole incident resolved based on one successful check.