Skip to main content
A 500, 502, or 503 on a proxied request comes from the target site, not from Massive. Errors that originate within the Massive network use status codes in the 452–454 and 470–477 ranges and always include an X-Massive-Reason response header.
  • If the response has no X-Massive-Reason header, the target site returned the error and Massive delivered it unchanged. Retry the request, or check the status of the target site.
  • If the response carries a Massive status code instead:
    • 470, 472, or 473: The condition is usually temporary; wait a moment and retry
    • 471: The geotargeting is too restrictive; relax the routing parameters
    • 474: Retry, and contact support if the error persists
    • 475: The sticky session’s node went offline; start a new session
    • 476: Connections to the target host timed out; check the target or increase the connect timeout
    • 477: The sticky session’s node is temporarily busy; retry with the same session ID shortly
See Error Types for the full list of status codes.