GitHub Copilot errors
OperationalWhat an error from GitHub Copilot means, and whether GitHub Copilot is failing for everyone at this moment.
Is GitHub Copilot failing right now?
No, GitHub Copilot is working. The official GitHub Copilot status page reports no incidents. We don’t make our own calls to this service. Last check 4 seconds ago.
We do not call GitHub Copilot ourselves, so we have no error share of our own for it.
What each error code means
GitHub Copilot talks to its servers over HTTP, and an error it shows often carries one of these codes. The meaning is the one of the HTTP standard.
| Code | What it means | What to do | Whose side |
|---|---|---|---|
| 400 Bad request | The request is not one the service can read: a field is missing, has the wrong type, or is too large. | Read the message in the body of the answer. Sending the same request again gives the same error. | Yours |
| 401 Unauthorized | The key or the sign-in is missing, wrong or no longer valid. | Check the key and how it is sent. Create a new one if it was revoked. | Yours |
| 403 Forbidden | The key is valid and may not do this: the plan, the region or the permission does not allow it. | Check what the key and the account may use. | Yours |
| 404 Not found | The address, or the model named in the request, does not exist for this account. | Check the address and the exact name of the model. | Yours |
| 429 Too many requests | A limit was reached: requests or tokens in a minute, or the credit of the account. | Wait as long as the Retry-After header says, then try again with a growing pause. If it does not pass, look at the limits of the account. | Yours |
| 500 Internal server error | The service failed while it handled the request. | Try again after a short pause. If it goes on, it is an incident on their side. | Theirs |
| 502 Bad gateway | A server in front of the service got no valid answer from the one behind it. | Try again after a short pause. | Theirs |
| 503 Service unavailable | The service cannot take the request now: it is overloaded or under maintenance. | Try again with a growing pause, and look at the status below. | Theirs |
| 504 Gateway timeout | A server in front of the service waited too long for the one behind it. | Try again. A long request may need streaming or a smaller size. | Theirs |
Questions about GitHub Copilot errors
Is it GitHub Copilot or my request?
A code from 400, 401, 403, 404 or 429 is about the request, the key or a limit of your account, and the same request fails again until that changes. A code from 500, 502, 503 or 504 is a fault on the side of GitHub Copilot, and trying again later can pass. Right now: No, GitHub Copilot is working. The official GitHub Copilot status page reports no incidents. We don’t make our own calls to this service. Last check 4 seconds ago.
What does GitHub Copilot error 429 mean?
A limit was reached: requests or tokens in a minute, or the credit of the account. Wait as long as the Retry-After header says, then try again with a growing pause. If it does not pass, look at the limits of the account.
What does GitHub Copilot error 500 or 503 mean?
The service failed while it handled the request. The service cannot take the request now: it is overloaded or under maintenance. Try again with a growing pause, and look at the status below.
Why do I get GitHub Copilot error 401?
The key or the sign-in is missing, wrong or no longer valid. Check the key and how it is sent. Create a new one if it was revoked.