- Software and systems
- HTTP service
503
HTTP 503 Service Unavailable: the service is temporarily unable to respond
Risk level
Low
Usually safe to check without specialist tools.
Urgency
Medium
Quick answer
HTTP 503 means the server is currently unable to handle the request because of temporary overload or scheduled maintenance. A Retry-After header can indicate when to try again.
Safety first
Stop and check this first
- Do not bypass rate limits or launch aggressive retries against a 503 response. Respect Retry-After when present and use bounded retries only for operations known to be safe.
Safe checks you can perform
- Read Retry-After before retrying
- Record whether the failure is service-wide
- Retry only operations known to be safe
Leave these tasks to a qualified professional
- Do not attempt this professional task: Verify capacity maintenance state and admission controls
What a technician must be able to justify
A technician is coming
These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.
These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.
Verify capacity maintenance state and admission controls
What they doThe service operator should correlate the 503 interval with load maintenance deployment and upstream health then restore capacity or correct routing before removing protective limits.
Before accepting a part or repair
Nothing has been shown yet. Do not accept a part swap based on the code alone.
Checks and evidence, step by step
Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.
- 1
Read Retry-After before retrying
Tools required
Procedure
Inspect the response for Retry-After. If present wait for the HTTP date or number of seconds it specifies before a safe retry.
Do not create a retry storm. A missing Retry-After value is not permission to retry continuously.
Evidence: RFC 9110 section 15.6.4 - 503 Service Unavailable · RFC 9110 section 10.2.3 - Retry-After
- 2
Record whether the failure is service-wide
Tools required
Procedure
Capture the endpoint timestamp request identifier and response headers then check an official status page or a safe health endpoint if the service provides one.
Do not send repeated synthetic traffic to a service that is already overloaded.
Evidence: RFC 9110 section 15.6.4 - 503 Service Unavailable
- 3
Retry only operations known to be safe
No special tools
Procedure
For a read request wait and retry once. Before retrying a purchase upload job or other write verify whether the first attempt was accepted and whether the operation has an idempotency key.
A repeated state-changing request can create duplicate work even when the client received 503.
Evidence: RFC 9110 section 15.6.4 - 503 Service Unavailable
Where this code applies
A code is meaningful only inside the right product and version context.
Primary scope
- System
- Software and systems
- Brand
- HTTP
- Product type
- HTTP service
Known code variants
- 503 Dienst nicht verfügbar
- 503 Service Unavailable
- 503 Servicio no disponible
- 503 Servizio non disponibile
- Bosch 503 bici elettrica
- Bosch 503 bicicleta eléctrica
- Bosch 503 E-Bike
- Bosch 503 eBike
- Bosch 503 vélo électrique
- Bosch eBike code 503
- Bosch eBike error 503
- Bosch eBike Fehler 503
- Bosch eBike Fehlercode 503
- code Bosch eBike 503
- code erreur 503
- codice Bosch eBike 503
- código Bosch eBike 503
- erreur Bosch eBike 503
- error Bosch eBike 503
- errore Bosch eBike 503
- HTTP 503
- HTTP status 503
- status code 503
What it means
The standard describes a temporary condition but does not guarantee a recovery time or require every overloaded server to return 503.
Warnings and stop conditions
- Higheditorial warning
Do not bypass rate limits or launch aggressive retries against a 503 response. Respect Retry-After when present and use bounded retries only for operations known to be safe.
Evidence: RFC 9110 section 15.6.4 - 503 Service Unavailable · RFC 9110 section 10.2.3 - Retry-After
Symptoms and causes
Probable causes · in order
- Temporary server overloadPossible
RFC 9110 defines temporary overload as one condition that can leave a server currently unable to handle a request.
Evidence: RFC 9110 section 15.6.4 - 503 Service Unavailable
- Scheduled maintenancePossible
Scheduled maintenance is the other condition explicitly named by RFC 9110 for 503 Service Unavailable.
Evidence: RFC 9110 section 15.6.4 - 503 Service Unavailable
Virtual technician
Does 503 still appear after these checks?
Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.
Sources and technical references
- 1
RFC 9110 section 15.6.4 - 503 Service Unavailable
Internet Engineering Task Force · 2022 · official_doc
- 2
RFC 9110 section 10.2.3 - Retry-After
Internet Engineering Task Force · 2022 · official_doc
Was this entry useful?