Search
Enter at least two characters without personal information.

    LibraryArticles & FAQ Your projectRequest a quote
    LanguageEN
    Practical guides

    Inform visitors during a service outage

    Explaining an interruption helps visitors understand what remains possible. Prepare the message and fallback channel before an incident, then distinguish confirmed facts from recovery estimates.

    Go to the method

    Status light and information panel on a laptop
    AI-generated illustration

    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.

    Response received at 09:00 GMT: fictional recovery exercise
    Observed signalInterpretationRequired check
    Retry-After: 120Indicated wait of 120 seconds, until 09:02 GMTActual availability at the next attempt
    Retry-After: Fri, 23 Oct 2026 09:02:00 GMTAbsolute retry dateFormat and clock; no recovery guarantee
    Header absent or invalidNo usable delay supplied by this headerBounded retry policy and helpful message
    Response lost after a POSTOperation outcome unknownCheck 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

    Content updated on

    Documented reference points for this topic

    Documented reference points for this topic
    ReferenceValue or syntaxScope
    HTTP · 503
    503 · Retry-AfterTemporary 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.

    Read an HTTP response before fixing the page

    Choose a situation to separate the status meaning, the useful check and the pitfall. This reader explains cases; it does not test any address.

    200Available page
    What it means
    The request succeeded. For an HTML page, also examine the returned content.
    What to check
    Check the title, main content and language, then the canonical and indexing directives.
    Watch out for
    A “not found” page returning 200 may become a soft 404. HTTP success does not guarantee indexing.
    301 / 308Permanent move
    What it means
    301 and 308 indicate a permanent new address. 308 explicitly preserves the method and body; with 301, a client may change POST to GET.
    What to check
    Open the old URL and check Location, a relevant destination and the absence of chains or loops.
    Watch out for
    Do not redirect every old page to the home page. For a form, also check the method expected at the destination.
    302 / 307Temporary move
    What it means
    302 and 307 indicate a temporary change. 307 preserves the method and body; with 302, a client may change POST to GET.
    What to check
    Check that the destination is available and that a return to the original address is planned.
    Watch out for
    A temporary redirect does not describe permanent removal. Do not replay a payment or order without checking its state.
    404 / 410Missing or removed resource
    What it means
    404 does not say whether the absence is temporary or permanent. 410 indicates a likely permanent removal.
    What to check
    Look for a broken link, a changed URL or deliberate removal. Offer a replacement only when it meets the same need.
    Watch out for
    A helpful error page must retain the actual 404 or 410 status. An error message with 200 does not fix the absence.
    429Too many requests
    What it means
    429 indicates request rate limiting. A Retry-After header may say when to try again.
    What to check
    Examine the limit’s scope and Retry-After. Slow down requests and bound retries.
    Watch out for
    Avoid immediate retry loops. Without an HTTP response, a network failure is not a 429 status.
    503Temporarily unavailable service
    What it means
    503 fits temporary unavailability, such as maintenance or overload. Retry-After may provide a delay or date.
    What to check
    Check the actual status, affected scope and return to normal service. Remove the notice after recovery.
    Watch out for
    Do not replace all pages with an error indefinitely. Persistent 5xx responses can eventually cause Google to remove URLs from its index.

    Technical references : RFC 9110 §15 · RFC 6585 §4 · Google · HTTP.

    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.

    Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

    Test cases, expected outcomes and useful evidence
    CaseExpected outcomeEvidence to retain
    Partial outageInformational pages remain accessible.Available and unavailable journeys, check time and emergency contact route actually reachable.
    Fallback channelThe contact is accessible and monitored.Test from another device.
    Service recoveryA 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.