Fictional example · verify your own facts

Upstream provider outage status update example

See a fictional status-page update and customer email that attribute a verified dependency incident without guessing its cause or recovery time.

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

Verified facts for this fictional scenario

Upstream-provider update · status page
Update 11:40 UTC: New single sign-on attempts are failing for EU workspaces. Existing sessions remain active. At 11:32 UTC, our upstream identity provider confirmed an active incident affecting its service. The provider has not published a recovery estimate. We are monitoring its status and will share another update by 12:00 UTC, even if there is no material change.
Upstream-provider update · customer email
Subject: Update on EU single sign-on failures New single sign-on attempts are failing for EU workspaces. Existing sessions remain active. At 11:32 UTC, our upstream identity provider confirmed an active incident affecting its service. The provider has not published a recovery estimate. We are monitoring its status and will send another update by 12:00 UTC, even if there is no material change.

Attribution requires confirmation
The drafts name the dependency incident only after the upstream provider has confirmed it; they do not infer a provider cause from customer symptoms.
Impact remains separate
The failed new sign-ins and still-active existing sessions are customer-visible facts, independent of the provider statement.
Unknown timing stays unknown
The provider has not published a recovery estimate, so neither customer channel invents one.
Cadence remains owned
Both drafts promise the next update at 12:00 UTC even though the recovery timing belongs to the provider.

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