HTTP 410 Gone— What It Means, Causes & How to Fix It
The target resource is no longer available at the server and no forwarding address is known. This condition is expected to be considered permanent. Unlike 404, this explicitly states the resource existed but was intentionally removed.
Enter any URL to see its real HTTP response code
Common Causes
- Resource intentionally and permanently deleted
- API endpoint deprecated and removed
- Content taken down for legal reasons
- Account or profile permanently closed
How to Fix
- 1Remove links and references to this resource
- 2Check for an archived version if the content is needed
- 3Update API integrations to use replacement endpoints
- 4Contact the site owner if the removal seems unintentional
Example
GET /api/v1/legacy-endpoint HTTP/1.1 → 410 Gone → "This endpoint was removed in v2. Use /api/v2/new-endpoint"
Related Client Error Codes
Bad Request
401Unauthorized
402Payment Required
403Forbidden
404Not Found
405Method Not Allowed
406Not Acceptable
407Proxy Authentication Required
408Request Timeout
409Conflict
411Length Required
412Precondition Failed
413Content Too Large
414URI Too Long
415Unsupported Media Type
416Range Not Satisfiable
417Expectation Failed
418I'm a Teapot
421Misdirected Request
422Unprocessable Content
423Locked
424Failed Dependency
425Too Early
426Upgrade Required
428Precondition Required
429Too Many Requests
431Request Header Fields Too Large
451Unavailable For Legal Reasons
Commonly Referenced Status Codes
The most frequently searched HTTP status codes