410 Gone
The resource was removed on purpose
Seen in Browsers, APIs, web servers
The server says this resource existed but has been permanently removed and will not return.
Common causes
- The page or file was deliberately deleted and marked as gone.
- An API version or endpoint was retired.
- A rewrite or plugin rule returns 410 for a pattern of URLs.
How to fix it
- If removal was intended, update links and let search engines drop the URL.
- For APIs, move to the replacement endpoint or version in the provider's changelog.
- If it is unintended, find and remove the rule returning 410.
Got a different message? Paste it into the error explainer.
Related errors
- 502 Bad Gateway · The proxy got a bad response from the server behind it
- 504 Gateway Timeout · The server behind the proxy took too long
- Error 520: Web server is returning an unknown error · Cloudflare got an empty or invalid response
- 429 Too Many Requests · You've hit a rate limit
- 400 Bad Request · The server could not understand the request
- 401 Unauthorized · The request needs valid credentials
- 403 Forbidden · The server refuses to allow this request
- 404 Not Found · Nothing exists at this URL
- 405 Method Not Allowed · This URL does not accept that HTTP method
- 414 Request-URI Too Large · The URL is longer than the server accepts
- 500 Internal Server Error · The application hit an error it did not handle
- 400 Bad Request: The plain HTTP request was sent to HTTPS port · Plain HTTP was sent to a port that expects TLS