Is 503 the right code for planned maintenance?
Yes. It tells clients and search engines the outage is temporary. Add Retry-After with the expected end of maintenance, and keep the maintenance page itself small and fast.
Overloaded or down for maintenance. Retry-After may say when it will return. 503 belongs to the 5xx server error class and is defined in RFC 9110.
Loading the workbench.
Overloaded or down for maintenance. Retry-After may say when it will return. The code is registered with IANA and defined in RFC 9110.
Server error: the server failed to fulfill a valid request. Every code from 500 to 599 shares that general meaning, so a client that does not recognise 503 must treat it like 500.
503 Service Unavailable means the server is temporarily unable to handle the request: it is overloaded, in planned maintenance, out of worker processes, or shedding load behind a circuit breaker. Load balancers send it when no healthy backend remains. Unlike 500, the condition is expected to clear on its own. Search engines treat a short 503 as a signal to come back later rather than to drop the page from the index.
Servers should include Retry-After with seconds or a date so clients and crawlers know when to return, and serve a lightweight maintenance page. Avoid long-running 503s for SEO; extended unavailability can eventually affect indexing. Clients should back off and retry later, respecting Retry-After. Operators should look at capacity, autoscaling, health checks, and dependency failures that took backends out of rotation.
HTTP/1.1 503 Service Unavailable
Retry-After: 300
Content-Type: text/html
Cache-Control: no-store503 is not cacheable by default: a browser or CDN stores it only when Cache-Control or Expires explicitly allows it.
To inspect a real one without sending it anywhere:
curl -i.Browse every code on the HTTP status codes page.
Elsewhere in 2http: Header decoder, Cookie decoder, Cache-Control decoder, CORS checker, User-agent parser, and all eleven lanes on the 2http home page. Part of the 2suite.io privacy-first ecosystem.
Yes. It tells clients and search engines the outage is temporary. Add Retry-After with the expected end of maintenance, and keep the maintenance page itself small and fast.
A brief 503 does not. Crawlers retry later. If a site returns 503 for days, search engines may start treating the pages as gone.
Yes. 503 is a server error response: the server failed to handle a valid request, so retrying later may work.
No. Caches store a 503 only when Cache-Control or Expires explicitly allows it.
You do not have to take our word that your headers stay here. Developer tools show every request a page makes, so you can watch this page work and confirm that nothing is sent. The check takes under a minute.
F12, or Cmd+Option+I on a Mac, and select the Network tab.Only two things can add a line to that log, and neither carries your headers. Submitting the feedback form sends the vote and comment you typed. Typing characters in a script the page has not displayed yet, such as Cyrillic or Greek, can make the browser fetch the matching font file, and that request names only the font.
2http never sends a request on your behalf: the request builder writes code for you to run, and the meta inspector reads source you paste instead of fetching a URL. The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site and the anonymous analytics endpoint.