Inform visitors during a service outage

Estimated reading time : 2 min · Published October 4, 2026

Identify the affected service

Specify the unavailable action: sending a request, paying or booking. Keep information and contacts accessible when they still work. A partial outage does not require hiding every page or describing functioning services as unavailable.

State the scope, the date and time of the last check and the next planned update. Include the time zone for an international audience. If recovery is unconfirmed, promise another update rather than inventing a restoration time.

Provide an alternative that actually works

Choose a monitored contact and explain what it can handle. A backup form on the same failed system is not an alternative. Check the channel from another device; avoid asking for sensitive information in a public message.

For a temporary technical outage, HTTP status 503 and, where possible, Retry-After indicate the situation to clients. A prolonged closure needs a different approach; keeping useful pages and restricting features may be better than blocking the site indefinitely.

Test the notice and service recovery

Prepare a simple notice that works with a keyboard and on mobile, without relying on a large image or a fragile third-party service. Check direct links to forms too: a homepage banner does not inform everyone who visits the site.

After recovery, test the entire journey, confirmations and previously received requests. Remove expired notices and check caches so an old interruption page does not remain visible. Keep a short internal timeline and assign responsibility for closing the public announcement.

Reference documents

Content updated on October 4, 2026

Record checks and findings in the acceptance log

Acceptance matrix to adapt to your project

These proposed checks use synthetic cases. Decide the required behaviour with the team, record the result and assign unresolved gaps before release.

Test cases, expected outcomes and useful evidence
Case	Expected outcome	Evidence to retain
Partial outage	Informational pages remain accessible.	List of available journeys.
Fallback channel	The contact is accessible and monitored.	Test from another device.
Service recovery	A complete action succeeds without an old notice.	Result, time and cache check.

Frequently asked questions

What should we say when recovery time is unknown?

State the confirmed limitation and the time of the next update. Do not turn an uncertain technical estimate into a public commitment.

Is a maintenance page enough?

Also check its HTTP status, direct links, fallback contact and removal after recovery. A readable page does not prove that confirmations or payments work.