GitHub header
All Systems Operational
Git Operations ? Operational
API Requests ? Operational
Webhooks ? Operational
Visit www.githubstatus.com for more information Operational
Issues ? Operational
Pull Requests ? Operational
Actions ? Operational
Packages ? Operational
Pages ? Operational
Codespaces ? Operational
Copilot Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Jun 5, 2024

No incidents reported today.

Jun 4, 2024

No incidents reported.

Jun 3, 2024

No incidents reported.

Jun 2, 2024

No incidents reported.

Jun 1, 2024

No incidents reported.

May 31, 2024

No incidents reported.

May 30, 2024
Incident with Copilot
Resolved - This incident has been resolved.
May 30, 17:22 UTC
Update - Copilot is operating normally.
May 30, 17:22 UTC
Update - We have rolled out mitigation and fixes appear to be stable. This incident has been resolved.
May 30, 17:22 UTC
Update - Copilot is experiencing degraded performance. We are continuing to investigate.
May 30, 17:14 UTC
Update - Our CoPilot API is currently experiencing back-end connectivity issues and we are actively engaged in mitigation steps.
May 30, 17:14 UTC
Investigating - We are currently investigating this issue.
May 30, 17:14 UTC
May 29, 2024

No incidents reported.

May 28, 2024
Incident with Codespaces
Investigating - Codespaces is operating normally.
May 28, 21:24 UTC
Resolved - This incident has been resolved.
May 28, 21:24 UTC
Update - A fix has been applied and we are seeing some recovery. We will continue to monitor for a bit before marking this issue resolved.
May 28, 21:19 UTC
Update - We are still investigating root cause and remediation options. In the meantime, here is a workaround to be able to pull images from DockerHub:

1. Make a free DockerHub account at https://hub.docker.com (or use an existing account if you have one).
2. Create a DockerHub secret/PAT from https://hub.docker.com/settings/security (Read permission should be sufficient).
3. Go to https://github.com/settings/codespaces

Add three Codespace secrets:

- DOCKERHUB_CONTAINER_REGISTRY_PASSWORD (equal to the DockerHub PAT you created)
- DOCKERHUB_CONTAINER_REGISTRY_SERVER (equal to https://index.docker.io/v1/)
- DOCKERHUB_CONTAINER_REGISTRY_USER (equal to your DockerHub username)

4. Make sure these secrets are set as visible to the target repo.
5. Create/rebuild your Codespace

Steps above are distilled from the official docs: https://docs.github.com/en/codespaces/reference/allowing-your-codespace-to-access-a-private-registry#example-secrets
May 28, 20:53 UTC
Update - Duplicate update, same as above
May 28, 20:53 UTC
Update - Some Codespaces are currently failing to be properly created for images hosted by DockerHub. Other registries should be unaffected. We are investigating root cause and will report back shortly.
May 28, 20:23 UTC
Investigating - We are investigating reports of degraded performance for Codespaces
May 28, 20:17 UTC
May 27, 2024

No incidents reported.

May 26, 2024

No incidents reported.

May 25, 2024

No incidents reported.

May 24, 2024

No incidents reported.

May 23, 2024
Incident with Codespaces
Resolved - On May 23, 2024 between 15:31 and 16:02 the Codespaces service reported a degraded experience in codespaces across all regions. Upon further investigation this was found to be an error reporting issue and did not have user facing impact. The new error reporting that was implemented began raising on existing non-user facing errors that are handled further in the flow, at the controller level, which do not cause user impact. We are working to improve our reporting roll out process to reduce issues like this in the future which includes updating monitors and dashboards to exclude this class of error. We are also reclassifying and correcting internal API responses to better represent when errors are user facing for more accurate reporting.
May 23, 16:02 UTC
Update - We are investigating increased error rates for customers attempting to start Codespaces across all regions, around 15% of attempts are affected. Any affected customers may attempt to retry starting their Codespace. We are continuing to investigate.
May 23, 15:41 UTC
Investigating - We are investigating reports of degraded performance for Codespaces
May 23, 15:31 UTC
May 22, 2024

No incidents reported.

← Incident History Powered by Atlassian Statuspage