GitHub Status

Apr 23, 2025

Incident with Issues, API Requests and Pages

Resolved - This incident has been resolved.
Apr 23, 08:00 UTC

Update - A brief problem with one of our database clusters caused intermittent errors around 07:05 UTC for a few minutes. Our systems have recovered and we continue to monitor.
Apr 23, 07:47 UTC

Update - Issues is operating normally.
Apr 23, 07:43 UTC

Update - Actions is operating normally.
Apr 23, 07:42 UTC

Update - Pages is operating normally.
Apr 23, 07:42 UTC

Update - API Requests is operating normally.
Apr 23, 07:42 UTC

Update - Codespaces is operating normally.
Apr 23, 07:41 UTC

Update - Codespaces is experiencing degraded performance. We are continuing to investigate.
Apr 23, 07:23 UTC

Update - Actions is experiencing degraded performance. We are continuing to investigate.
Apr 23, 07:22 UTC

Investigating - We are investigating reports of degraded performance for API Requests, Issues and Pages
Apr 23, 07:17 UTC

Apr 22, 2025

Codespaces Scheduled Maintenance

Completed - The scheduled maintenance has been completed.
Apr 22, 16:30 UTC

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 21, 16:30 UTC

Scheduled - Codespaces will be undergoing global maintenance from 16:30 UTC on Monday, April 21 to 16:30 UTC on Tuesday, April 22. Maintenance will begin in our Europe, Asia, and Australia regions. Once it is complete, maintenance will start in our US regions. Each batch of regions will take approximately three to four hours to complete.

During this time period, users may experience intermittent connectivity issues when creating new Codespaces or accessing existing ones.

To avoid disruptions, ensure that any uncommitted changes are committed and pushed before the maintenance starts. Codespaces with uncommitted changes will remain accessible as usual after the maintenance is complete.
Apr 17, 15:30 UTC

Apr 21, 2025

Apr 20, 2025

No incidents reported.

Apr 19, 2025

No incidents reported.

Apr 18, 2025

No incidents reported.

Apr 17, 2025

Disruption with some GitHub services

Resolved - On April 15th during regular testing we found a bug in our Copilot Metrics Pipeline infrastructure causing some data used to aggregate Copilot usage for the Copilot Metrics API to not be ingested. As a result of the bug, customer metrics in the Copilot Metrics API would have indicated lower than expected Copilot usage for the previous 28 days.
To mitigate the incident we resolved the bug so that all data from April 14th onwards would be accurately calculated and immediately began backfilling the previous 28 days with the correct data. All data has been corrected as of 2025-04-17 5:34PM UTC.
We have added additional monitoring to catch similar pipeline failures in the future earlier and are working on enhancing our data validation to ensure that all metrics we provide are accurate.
Apr 17, 17:35 UTC

Update - We have resolved issues with data inconsistency for Copilot Metrics API data as of April 17th 2025 1600 UTC. All data is now accurate.
Apr 17, 17:34 UTC

Update - We are continuing to work on correcting the Copilot Metrics API data from March 19th 2025 to April 14th 2025. Data from April 15 and later is accurate. Currently, the API returns about 10% lower usage numbers. Based on the current investigations we estimate to have a resolution by April 18th 0100 hrs UTC. We will provide an update if there is change in the ETA.
Apr 16, 22:44 UTC

Update - We have an updated ETA on correcting all Copilot metrics API data: 20 hours. We won't post more updates here unless the ETA changes.
Apr 16, 05:11 UTC

Update - We are working on correcting the Copilot metrics API source data from March 19th to April 14th. Currently, the API returns about 10% lower usage numbers than the reality. We don't have an ETA for the resolution at the moment.
Apr 16, 01:46 UTC

Update - The Copilot metrics API (https://docs.github.com/en/enterprise-cloud@latest/rest/copilot/copilot-metrics?apiVersion=2022-11-28) now returns accurate data for April 15th. We're working on correcting the past 27 days, as we are under-reporting certain metrics from this time.
Apr 16, 00:41 UTC

Update - We'll have accurate data for April 15th in the next 60 minutes. We're still working on correcting the data for the additional 27 days before April 15th. The complete correction is estimated to take up to 7 days, but we're working to speed this up.

https://docs.github.com/en/enterprise-cloud@latest/rest/copilot/copilot-metrics?apiVersion=2022-11-28 is the specific impacted API.
Apr 15, 23:33 UTC

Update - As we've made further progress on correcting the inconsistencies, we estimate it will take approximately a week for a full recovery. We are investigating options for speeding up the recovery, and we appreciate your patience as we work through this incident.
Apr 15, 21:45 UTC

Update - We are working on correcting the inconsistencies now, our next update we will provide an estimated time when the issue will be fully resolved.
Apr 15, 19:02 UTC

Update - We are currently experiencing degraded performance with our Copilot metrics API, which is temporarily causing partial inconsistencies in the data returned. Our engineering teams are actively working to restore full functionality. We understand the importance of timely updates and are prioritizing a resolution to ensure all systems are operating normally as quickly as possible.
Apr 15, 18:20 UTC

Investigating - We are currently investigating this issue.
Apr 15, 18:20 UTC

Apr 16, 2025

Incident with Pull Requests

Resolved - On April 16, 2025 between 3:22:36 PM UTC and 5:26:55 PM UTC the Pull Request service was degraded. On average, 0.7% of page views were affected. This primarily affected logged-out users, but some logged-in users were affected as well.

This was due to an error in how certain Pull Request timeline events were rendered, and we resolved the incident by updating the timeline event code.

We are enhancing test coverage to include additional scenarios and piloting new tools to prevent similar incidents in the future.

Apr 16, 17:26 UTC

Update - Pull Requests is operating normally.
Apr 16, 17:26 UTC

Update - The fix is rolling out and we're seeing recovery for users encountering 500 errors when viewing a pull request.
Apr 16, 17:13 UTC

Update - The fix is currently being deployed, we anticipate this to be fully mitigated in approximately thirty minutes.
Apr 16, 16:17 UTC

Update - Users may experience 500 errors when viewing a PR. Most of the impact is limited to anonymous access there is a small handful of logged in users who are also experiencing this. We have the fix prepared and it will be deployed soon.
Apr 16, 15:55 UTC

Investigating - We are investigating reports of degraded performance for Pull Requests
Apr 16, 15:22 UTC

Apr 15, 2025

Disruption with some GitHub services for Safari Users

Resolved - On April 15, 2025 from 12:45 UTC to 13:56 UTC, access to GitHub.com was restricted for logged out users using WebKit-based browsers, such as Safari and various mobile browsers. During the impacting time, roughly 6.6M requests were unsuccessful.

This issue was caused by a configuration change intended to improve our handling of large traffic spikes but was improperly targeted at too large a set of requests.

To prevent future incidents like this, we are improving how we operationalize these types of changes, adding additional tools for validating what will be impacted by such changes, and reducing the likelihood of manual mistakes through automated detection and handling of such spikes.
Apr 15, 14:12 UTC

Update - Safari users are now able to access GitHub.com.

The fix has been rolled out to all environments.
Apr 15, 14:11 UTC

Update - Most unauthenticated Safari users should now be able to access github.com. We are ensuring the fix is deployed out to all environments.

Next update in 30m.
Apr 15, 13:59 UTC

Update - We have identified the cause of the restriction for Safari users and are deploying a fix. Next update in 15 minutes.
Apr 15, 13:46 UTC

Update - Some unauthenticated Safari users are seeing the message "Access to this site has been restricted." We are currently investigating this behavior.
Apr 15, 13:30 UTC

Investigating - We are currently investigating this issue.
Apr 15, 13:30 UTC

Apr 14, 2025

No incidents reported.

Apr 13, 2025

No incidents reported.

Apr 12, 2025

[Retroactive] Access from China temporarily blocked for users that were not logged in

Resolved - Due to a configuration change with unintended impact, some users that were not logged in who tried to visit GitHub.com from China were temporarily unable to access the site. For users already logged in, they could continue to access the site successfully. Impact started 2025/04/12 at 20:01 UTC. Impact was mitigated 2025/04/13 at 14:55 UTC. During this time, up to 4% of all anonymous requests originating from China were unsuccessful.

The configuration changes that caused this impact have been reversed and users should no longer see problems when trying to access GitHub.com.
Apr 12, 20:00 UTC

Apr 11, 2025

Incident with Codespaces

Resolved - On April 11 from 3:05am UTC to 3:44am UTC, approximately 75% of Codespaces users faced create and start failures. These were caused by manual configuration changes to an internal dependency. We reverted the changes and immediately restored service health.

We are working on safer mechanisms for testing and rolling out such configuration changes, and we expect no further disruptions.
Apr 11, 00:51 UTC

Update - We have reverted a problematic configuration change and are seeing recovery across starts and resumes
Apr 11, 00:50 UTC

Update - We have identified an issue that is causing errors when starting new and resuming existing Codespaces. We are currently working on a mitigation
Apr 11, 00:44 UTC

Investigating - We are investigating reports of degraded availability for Codespaces
Apr 11, 00:28 UTC

Apr 10, 2025

Disruption with some Pull Requests stuck in processing state

Resolved - On April 9, 2025, between 11:27 UTC and 12:39 UTC, the Pull Requests service was degraded and experienced delays in processing updates. At peak, approximately 1–1.5% of users were affected by delays in synchronizing pull requests. During this period, users may have seen a "Processing updates" message in their pull requests after pushing new commits, and the new commits did not appear in the Pull Request view as expected. The Pull Request synchronization process has automatic retries and most delays were automatically resolved. Any Pull Requests that were not resynchronized during this window were manually synchronized on Friday, April 11 at 14:23 UTC.

This was due to a misconfigured GeoIP lookup file that our routine GitHub operations depended on and led to background job processing to fail.

We mitigated the incident by reverting to a known good version of the GeoIP lookup file on affected hosts.

We are working to enhance our CI testing and automation by validating GeoIP metadata to reduce our time to detection and mitigation of issues like this one in the future.
Apr 10, 00:39 UTC

Update - Pull Requests is operating normally.
Apr 10, 00:36 UTC

Update - The team has identified a mitigation and is rolling it out while actively monitoring recovery
Apr 10, 00:19 UTC

Update - Some users are experiencing delays in pull request updates. After pushing new commits, PRs show a "Processing updates" message, and the new commits do not appear in the pull request view.
Apr 9, 23:39 UTC

Update - Pull Requests is experiencing degraded performance. We are continuing to investigate.
Apr 9, 23:36 UTC

Investigating - We are currently investigating this issue.
Apr 9, 23:27 UTC

Apr 9, 2025

Incident with Pull Requests

Resolved - On April 9, 2025, between 7:01 UTC and 9:31 UTC, the Pull Requests service was degraded and failed to update refs for repositories with higher traffic. This was due to a repository migration creating a larger than usual number of enqueued jobs. This resulted in an increase in job failures and delays for non-migration sourced jobs.

We declared an incident once we confirmed that this issue was not isolated to the migrating repository and other repositories were also failing to process ref updates.

We mitigated the incident by shifting the migration jobs to a different job queue.

To avoid problems like this in the future, we are revisiting our repository migration process and are working to isolate potentially problematic migration workloads from non-migration workloads.
Apr 9, 09:31 UTC

Update - We saw a period of delays on Pull request experiences. The impact is over at the moment, but we are investigating to prevent a repeat.
Apr 9, 09:28 UTC

Investigating - We are investigating reports of degraded performance for Pull Requests
Apr 9, 09:00 UTC

All Systems Operational

About This Site

Past Incidents