# What does the HTTP 503 status code mean?

> HTTP 503 Service Unavailable means the server cannot handle the request now due to a temporary overload or scheduled maintenance, under RFC 9110.

*A server may send a Retry-After header with a 503 to say how long the service is expected to be unavailable, as a date or a number of seconds.*

- Type: Explainer
- Section: Tech
- By: Tech Desk
- Published: 2026-11-12T23:39:43-05:00
- Updated: 2026-11-12T23:39:43-05:00
- Checked: 2026-11-12T23:39:15-05:00
- URL: https://factsdesk.com/tech/what-does-the-http-503-status-code-mean/

## Key facts

- HTTP 503 Service Unavailable means the server cannot handle the request now because of a temporary overload or scheduled maintenance, under RFC 9110. Source: [RFC Editor (Internet Engineering Task Force)](https://www.rfc-editor.org/rfc/rfc9110.html). Confirmed 2026-11-12T23:39:15-05:00. Cite: https://factsdesk.com/tech/what-does-the-http-503-status-code-mean/#http-503-service-unavailable-means-the-server-cannot-handle
- RFC 9110 says a server may send a Retry-After header field with a 503 to indicate how long the service is expected to be unavailable, as an HTTP-date or a number of seconds. Source: [RFC Editor (Internet Engineering Task Force)](https://www.rfc-editor.org/rfc/rfc9110.html). Confirmed 2026-11-12T23:39:15-05:00. Cite: https://factsdesk.com/tech/what-does-the-http-503-status-code-mean/#rfc-9110-says-a-server-may-send-a-retry-after-header-field
- RFC 9110 notes that a server does not have to use 503 when it becomes overloaded, and that some servers might simply refuse the connection. Source: [RFC Editor (Internet Engineering Task Force)](https://www.rfc-editor.org/rfc/rfc9110.html). Confirmed 2026-11-12T23:39:15-05:00. Cite: https://factsdesk.com/tech/what-does-the-http-503-status-code-mean/#rfc-9110-notes-that-a-server-does-not-have-to-use-503-when
- The definition of 503 in RFC 7231, published in June 2014, uses the same wording that RFC 9110 uses for the code. Source: [RFC Editor (Internet Engineering Task Force)](https://www.rfc-editor.org/rfc/rfc7231.html). Confirmed 2026-11-12T23:39:15-05:00. Cite: https://factsdesk.com/tech/what-does-the-http-503-status-code-mean/#the-definition-of-503-in-rfc-7231-published-in-june-2014
- The IANA HTTP Status Code Registry lists code 503 with the description Service Unavailable and the reference RFC 9110, Section 15.6.4. Source: [Internet Assigned Numbers Authority (IANA)](https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml). Confirmed 2026-11-12T23:39:15-05:00. Cite: https://factsdesk.com/tech/what-does-the-http-503-status-code-mean/#the-iana-http-status-code-registry-lists-code-503-with-the

The HTTP 503 (Service Unavailable) status code means that the server is currently unable to handle the request because of a temporary overload or scheduled maintenance, according to [RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html), the IETF standard that defines HTTP semantics. In the words of [Section 15.6.4 of RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-503-service-unavailable), "The 503 (Service Unavailable) status code indicates that the server is currently unable to handle the request due to a temporary overload or scheduled maintenance, which will likely be alleviated after some delay."

## A 503 is meant to be temporary

The definition ties 503 to a condition that will likely be alleviated after some delay. The [5xx (Server Error) class](https://www.rfc-editor.org/rfc/rfc9110.html#name-server-error-5xx) as a whole indicates that the server is aware that it has erred or is incapable of performing the requested method, and RFC 9110 says that, except when responding to a HEAD request, the server should send a representation explaining the error situation and whether it is a temporary or permanent condition.

## How the Retry-After header works with a 503

[RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-503-service-unavailable) says the server may send a Retry-After header field with a 503 to suggest an appropriate amount of time for the client to wait before retrying the request. [Section 10.2.3](https://www.rfc-editor.org/rfc/rfc9110.html#name-retry-after) says that when Retry-After is sent with a 503 response, it indicates how long the service is expected to be unavailable to the client. The value can be either an HTTP-date or a number of seconds to delay after receiving the response, and the standard gives these two examples:

| Form | Example from RFC 9110 | How to read it |
| --- | --- | --- |
| HTTP-date | Fri, 31 Dec 1999 23:59:59 GMT | Wait until that moment, in UTC |
| Seconds | 120 | Wait 120 seconds after receiving the response |

[RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-date-time-formats) says an HTTP-date value represents time in Coordinated Universal Time (UTC), and its [Retry-After section](https://www.rfc-editor.org/rfc/rfc9110.html#name-retry-after) says a delay-seconds value is a non-negative decimal integer. The header is optional: the definition says the server "MAY" send it.

## How 503 compares with 500, 502, 504 and 429

Several codes can appear when a site is down or busy. RFC 9110 defines the 5xx codes in this table, and [RFC 6585](https://www.rfc-editor.org/rfc/rfc6585.html#section-4) defines 429, which is a client error in the 4xx class.

| Code | What its definition says | Retry-After in the definition |
| --- | --- | --- |
| 500 Internal Server Error | An unexpected condition prevented the server from fulfilling the request | Not named |
| 502 Bad Gateway | A gateway or proxy received an invalid response from an inbound server | Not named |
| 503 Service Unavailable | The server cannot handle the request now because of a temporary overload or scheduled maintenance | The server may send it |
| 504 Gateway Timeout | A gateway or proxy did not receive a timely response from an upstream server | Not named |
| 429 Too Many Requests | The user has sent too many requests in a given amount of time | The response may include it |

The 500, 502, 503 and 504 rows are summarized from Sections [15.6.1](https://www.rfc-editor.org/rfc/rfc9110.html#name-500-internal-server-error) to [15.6.5](https://www.rfc-editor.org/rfc/rfc9110.html#name-504-gateway-timeout) of RFC 9110, and the 429 row from [Section 4 of RFC 6585](https://www.rfc-editor.org/rfc/rfc6585.html#section-4). Separate pages explain [502 Bad Gateway](/tech/what-does-the-http-502-status-code-mean/) and [504 Gateway Timeout](/tech/what-does-the-http-504-status-code-mean/).

## An overloaded server does not have to send 503

[RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-503-service-unavailable) adds a note: "The existence of the 503 status code does not imply that a server has to use it when becoming overloaded." The same note says some servers might simply refuse the connection instead.

## Can a 503 be cached?

Not by heuristic expiration. The [overview of status codes in RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-overview-of-status-codes) gives the heuristically cacheable codes in that specification, by way of example, as 200, 203, 204, 206, 300, 301, 308, 404, 405, 410, 414 and 501, and says all other status codes are not heuristically cacheable, which leaves 503 outside the list. For 429, [RFC 6585](https://www.rfc-editor.org/rfc/rfc6585.html#section-4) goes further and says responses with that code must not be stored by a cache.

## What changed and when

[RFC 7231](https://www.rfc-editor.org/rfc/rfc7231.html#section-6.6.4), published in June 2014, defined 503 in Section 6.6.4 with the same wording and the same note about overloaded servers, and defined Retry-After in [Section 7.1.3](https://www.rfc-editor.org/rfc/rfc7231.html#section-7.1.3). [RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html) was published in June 2022 on the Standards Track, carries the number STD 97 and obsoletes RFC 7231, as its header shows; the definition of 503 moved to Section 15.6.4 and Retry-After to Section 10.2.3. The [IANA registry](https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml) now points code 503 to RFC 9110, Section 15.6.4, lists 429 Too Many Requests with the reference RFC 6585, and shows its last update as September 15, 2025.

## Sources

1. [RFC 9110: HTTP Semantics](https://www.rfc-editor.org/rfc/rfc9110.html), RFC Editor (Internet Engineering Task Force), 2022-06 (primary source)
2. [Hypertext Transfer Protocol (HTTP) Status Code Registry](https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml), Internet Assigned Numbers Authority (IANA), 2025-09-15 (primary source)
3. [RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content](https://www.rfc-editor.org/rfc/rfc7231.html), RFC Editor (Internet Engineering Task Force), 2014-06 (primary source)
4. [RFC 6585: Additional HTTP Status Codes](https://www.rfc-editor.org/rfc/rfc6585.html), RFC Editor (Internet Engineering Task Force), 2012-04 (primary source)

## Asked next

- [What does the HTTP 500 status code mean?](https://factsdesk.com/tech/what-does-the-http-500-status-code-mean/): HTTP 500 Internal Server Error means the server encountered an unexpected condition that prevented it from fulfilling the request, under RFC 9110.
- [What does the HTTP 502 status code mean?](https://factsdesk.com/tech/what-does-the-http-502-status-code-mean/): HTTP 502 Bad Gateway means a server acting as a gateway or proxy received an invalid response from an inbound server, under RFC 9110.
- [What does the HTTP 504 status code mean?](https://factsdesk.com/tech/what-does-the-http-504-status-code-mean/): HTTP 504 Gateway Timeout means a server acting as a gateway or proxy did not get a timely response from an upstream server, under RFC 9110.
- [What does the HTTP 404 status code mean?](https://factsdesk.com/tech/what-does-the-http-404-status-code-mean/): HTTP 404 Not Found means the server did not find a current representation for the target resource or is not willing to disclose that one exists.
- [What does the HTTP 400 status code mean?](https://factsdesk.com/tech/what-does-the-http-400-status-code-mean/): HTTP 400 Bad Request means the server cannot or will not process a request because of something it perceives to be a client error, under RFC 9110.
- [What does the HTTP 429 status code mean?](https://factsdesk.com/tech/what-does-the-http-429-status-code-mean/): HTTP 429 Too Many Requests means the user has sent too many requests in a given amount of time, which RFC 6585 calls rate limiting.
