Estimated reading time : 5 min · Published
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.
Prepare announced downtime without endless automatic retry attempts.
Synthetic case: maintenance temporarily disables a feature. Test an appropriate status and realistic Retry-After on a service copy. The client should also handle a missing or invalid header with bounded retries. An expected date does not guarantee restoration: update the message when circumstances change.
Fictional exercise: a response arrives on 23 October 2026 at 09:00 GMT with Retry-After: 120. The number means seconds after receipt, so the indicated retry time is 09:02 GMT. Another possible syntax is Retry-After: Fri, 23 Oct 2026 09:02:00 GMT. Neither form guarantees recovery at that time or automatic retry by every client. Also give people an understandable time for the next update.
If only booking is suspended, keep information pages usable and adapt the affected function’s response. Google recommends limiting functionality rather than shutting the entire site down for a prolonged period; also check that robots.txt remains normally accessible. A retry delay does not establish that an earlier operation was abandoned: after a lost POST response, check the result or retry contract before automatically sending the request again.
- Attempts remain spaced and bounded; messaging distinguishes temporary downtime from permanent removal.
Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.
| Observed signal | Interpretation | Required check |
|---|---|---|
| Retry-After: 120 | Indicated wait of 120 seconds, until 09:02 GMT | Actual availability at the next attempt |
| Retry-After: Fri, 23 Oct 2026 09:02:00 GMT | Absolute retry date | Format and clock; no recovery guarantee |
| Header absent or invalid | No usable delay supplied by this header | Bounded retry policy and helpful message |
| Response lost after a POST | Operation outcome unknown | Check the result before a retry that could duplicate it |
- MDN Retry-After
Header indicating a delay or date for another attempt, including after unavailability or request limiting.
Reference documents
- MDN : HTTP 503
- Google Search Central · Source consulted
- MDN Retry-After · Source consulted
- IETF : HTTP Semantics, idempotent methods · Source consulted
Content updated on
Documented reference points for this topic
| Reference | Value or syntax | Scope |
|---|---|---|
| HTTP · 503 | 503 · Retry-After | Temporary unavailability; a delay may be indicated without guaranteeing recovery. |
Dates indicate when references were consulted. These facts are neither a site audit nor an overall compliance statement.
