Status page

status.acme-hq.example tells customers whether sign-in, the portal, notices and SMS codes work, per region. It went live on 1 July (ENG-1497, OPS-34), after OPS-33, when customers learnt about an SMS outage from their depot staff before they heard it from us.

It runs as a small static site outside our three production stacks, so it stays up when they don't.

Components

Component	Regions
Sign-in (passwords and phone codes)	EU, UK, US
Single sign-on	EU, UK, US
Portal	EU, UK, US
Email notices (EU account)	EU
Email notices (US account)	UK, US
SMS codes	all

Who posts, and when

• The incident lead posts within 15 minutes of a SEV1, and for a SEV2 as soon as customers would notice.
• Update at least every 30 minutes until it is resolved, even if nothing changed.
• Planned work that customers could notice goes up three working days before.
• Support can ask for a post; only on-call engineers and Oskar can publish.

How we write

• Say what doesn't work, for whom, and what people can do meanwhile. "Phone codes to UK numbers are arriving up to two hours late. Workers already signed in are not affected."
• No guesses about cause until we know. No "minor disruption".
• Times in the customer's time: UK components in UK time, EU in CET/CEST.

Posts so far

When	What
2 Sep–3 Sep	Password sign-in slow in the EU during an attack (OPS-41)
16 Oct	Planned: EU customers' notice emails move to a new mail account (OPS-50); no interruption

Change history

Version	Date	Who	What
1	29 Jun 2026	Oskar	First version
2	1 Jul 2026	Oskar	Live
4	4 Sep 2026	Oskar	Lessons from posting during OPS-41
5	13 Oct 2026	Oskar	Notice for the mail account change
6	21 Oct 2026	Oskar	Email notices split by Mailcrest account