400 | Bad Request | – | The request was malformed, most likely because of invalid routing parameters; the response body contains details |
407 | Proxy Authentication Required | – | The login email address, the Massive API token, or both were incorrect |
429 | Too Many Requests | – | The request rate limit for the account was exceeded |
452 | Disallowed Content | 452 | The requested protocol or content conflicts with Massive’s content policy; the Link header lists the entire policy |
453 | Port Forbidden | 452 | The requested port is not available on the account; ports 80 and 443 are open by default, and support can enable others |
454 | Target Unresolvable | 502 | The target hostname could not be resolved; retries fail until the hostname is corrected |
470 | No Nodes Available | 503 | No proxy nodes were available; the condition is usually temporary and a retry is likely to succeed |
471 | No Route Match | 521, 503 | No available node matched the geotargeting or routing parameters; retries fail until the targeting is relaxed |
472 | Node Tunnel Failed | 502 | A tunnel to a proxy node could not be established; the condition is usually temporary |
473 | Upstream Unavailable | 503 | A Massive server involved in routing the request was unreachable; the condition is usually temporary |
474 | Proxy Internal Error | 500 | An internal Massive error occurred; persistent occurrences are worth reporting to support |
475 | Sticky Node Gone | 503 | The node serving the sticky session went offline; a new session is required |
476 | Target Connect Timeout | 502 | Connections to the target host timed out on every attempt; a longer connect timeout may help |
477 | Sticky Node At Capacity | 503 | The node serving the sticky session is temporarily at capacity; the same session can be retried after a short delay |
