Fictional example · verify your own facts

Service outage status update example

See a fictional service-outage acknowledgment and resolution built only from clearly labeled verified facts for status page and email.

By Electricity Studio · Published August 8, 2026 · Updated August 11, 2026

Verified facts for this fictional scenario

Acknowledgment · status page
We are investigating file upload failures affecting EU workspaces. We first observed the issue at 14:05 UTC. We will share another update by 14:35 UTC.
Acknowledgment · customer email
Subject: Investigating file upload disruption We are investigating file upload failures affecting EU workspaces. We first observed the issue at 14:05 UTC. We will update you by 14:35 UTC, even if there is no material change.
Resolution · status page
The incident affecting file uploads for EU workspaces was resolved at 14:27 UTC. Normal file upload operation has been restored. We are monitoring recovery and will share a follow-up by August 12 if there are additional verified details.
Resolution · customer email
Subject: File upload disruption resolved The incident affecting file uploads for EU workspaces was resolved at 14:27 UTC. Normal file upload operation has been restored. We are monitoring recovery. Thank you for your patience while we worked through this.

Scope stays concrete
Each message names the affected workflow and EU workspace scope without guessing a customer count or severity.
Cadence is explicit
The acknowledgment commits to 14:35 UTC even if there is no material change, rather than implying that silence is the next update.
Channels share the same facts
Status-page and email versions use the same observed and resolved times while adapting only the channel format.
Hypotheses stay out
No cause, restoration estimate, remediation detail, or unverified conclusion appears in the customer messages.

The free acknowledgment and resolution composer runs entirely in your browser.