ErrorBase
Independent technical referenceOfficial site
  • Software and systems
  • HTTP service

504

HTTP 504 Gateway Timeout: a gateway did not receive an upstream response in time

Verified with sources1 sourceReviewed Aug 22, 2026
Technician coming? See what they must show you

Risk level

Low

Usually safe to check without specialist tools.

Urgency

Medium

Quick answer

HTTP 504 means a server acting as a gateway or proxy did not receive a timely response from an upstream server needed to complete the request.

Safety first

Stop and check this first

  • Do not raise gateway timeouts blindly. First locate the slow upstream boundary and confirm whether the request is safe to repeat.

Safe checks you can perform

  • Identify the gateway that returned 504
  • Check whether a safe request succeeds
  • Preserve timing evidence

Leave these tasks to a qualified professional

  • Do not attempt this professional task: Trace the gateway-to-upstream path

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.

  1. Trace the gateway-to-upstream path

    What they doThe platform operator should correlate gateway and upstream request timing then inspect reachability processing duration queueing and the configured deadline at the first slow boundary.

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. 1

    Identify the gateway that returned 504

    Tools required

    Procedure

    Record response headers request identifiers the endpoint and UTC timestamp so the operator can determine which CDN load balancer reverse proxy or application gateway emitted the response.

    Redact authorization cookies URL secrets and personal data before sharing the exchange.

    Evidence: RFC 9110 section 15.6.5 - 504 Gateway Timeout

  2. 2

    Check whether a safe request succeeds

    Tools required

    Procedure

    Try one lightweight read-only endpoint or official health check and note whether the timeout affects one route or the whole service.

    Do not repeat long-running writes or uploads until their prior outcome is known.

    Evidence: RFC 9110 section 15.6.5 - 504 Gateway Timeout

  3. 3

    Preserve timing evidence

    Tools required

    Procedure

    Record the elapsed time before 504 and whether the same operation normally completes faster. Give that evidence to the gateway and upstream service owners.

    Increasing every timeout can hide a stalled upstream and consume more gateway capacity.

    Evidence: RFC 9110 section 15.6.5 - 504 Gateway Timeout

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

  • 504 Gateway Timeout
  • 504 Gateway-Zeitüberschreitung
  • 504 Tiempo de espera de puerta de enlace
  • 504 Timeout del gateway
  • Bosch 504 bici elettrica
  • Bosch 504 bicicleta eléctrica
  • Bosch 504 E-Bike
  • Bosch 504 eBike
  • Bosch 504 vélo électrique
  • Bosch eBike code 504
  • Bosch eBike error 504
  • Bosch eBike Fehler 504
  • Bosch eBike Fehlercode 504
  • code Bosch eBike 504
  • code erreur 504
  • codice Bosch eBike 504
  • código Bosch eBike 504
  • erreur Bosch eBike 504
  • error Bosch eBike 504
  • errore Bosch eBike 504
  • HTTP 504
  • HTTP status 504
  • status code 504

What it means

The timeout is reported by an intermediary and does not by itself show whether the upstream application network or configured deadline is responsible.

Warnings and stop conditions

  • Higheditorial warning

    Do not raise gateway timeouts blindly. First locate the slow upstream boundary and confirm whether the request is safe to repeat.

    Evidence: RFC 9110 section 15.6.5 - 504 Gateway Timeout

Symptoms and causes

Probable causes · in order

  • A gateway or proxy did not receive an upstream response in timeConfirmed

    RFC 9110 defines 504 as a gateway or proxy timing out while waiting for an upstream server needed to complete the request.

    Evidence: RFC 9110 section 15.6.5 - 504 Gateway Timeout

Virtual technician

Does 504 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.

Start diagnosis

Sources and technical references

  1. 1

    RFC 9110 section 15.6.5 - 504 Gateway Timeout

    Internet Engineering Task Force · 2022 · official_doc

Sources: RFC 9110 section 15.6.5 - 504 Gateway Timeoutreviewed 2026-08-22 · verified

Was this entry useful?