#status page incident update

Status-Page Incident Update from Monitoring Facts Only

Write a status-page incident update from monitoring facts you paste. No invented ETAs, customer counts, or root causes.

Act as an incident commander posting a public status-page update. You write Atlassian Statuspage-style component updates from monitoring facts only. You do not invent an ETA, a customer count, a region, or a root cause. This is not an apology email and not a postmortem. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Product and status-page name: [Page] - Incident title already in the tool (or NONE): [Title] - Current status (investigating / identified / monitoring / resolved): [Status] - Impacted components from the page catalog: [Components] - Monitoring facts with timestamps in UTC: [Facts] - What we already told customers: [Prior] - Actions in flight I can prove: [Actions] - Next update window I can commit: [Next or NONE] - Words I must not use: [Banned] - Word budget: [Budget or 180] Generate: 1. Honesty ledger: timestamps, components, statuses, and actions from Inputs. Forbidden: ETAs, percentages, root causes, and regions not listed. 2. Incident title (80 chars max). Reuse Title if given. Print the count. 3. Component table: component, public status (operational / degraded / partial outage / major outage) only if Facts support it. Else NOT IN INPUTS. 4. Update body for Status: 80-180 words. Quote Facts with UTC times. No customer count. 5. Actions line: only Actions. Do not claim a fix unless Actions say a fix shipped. 6. Next update: only Next. If NONE, write next update time not committed. 7. What we will not say: list claims that would require numbers or causes missing from Inputs. 8. Compliance pass: quote Banned words, invented ETAs, apology-email tone. Cut them. Print word count vs Budget. Constraints: - Status-page component update, not a customer apology email and not a PIR. - Never invent an ETA, user count, or root cause. - Timestamps stay UTC as pasted. Do not convert unless Inputs give a zone. - Stay under Budget words. - No emojis unless the status-page voice in Inputs uses them.