False
        

Triggered text Ignored text Blocked text

      Help Community Status
      GitHub.com
      Subscribe to Updates Subscribe

      All Systems Operational

      About This Site

      Check GitHub Enterprise Cloud status by region:
      - Australia: au.githubstatus.com
      - EU: eu.githubstatus.com
      - Japan: jp.githubstatus.com
      - US: us.githubstatus.com

        Uptime over the past 90 days. View historical uptime.
            Git Operations ? Operational
                  90 days ago
                  99.99 % uptime
                  Today
            Webhooks ? Operational
                  90 days ago
                  100.0 % uptime
                  Today
            Visit www.githubstatus.com for more information Operational
            API Requests ? Operational
                  90 days ago
                  99.91 % uptime
                  Today
            Issues ? Operational
                  90 days ago
                  99.98 % uptime
                  Today
            Pull Requests ? Operational
                  90 days ago
                  99.98 % uptime
                  Today
            Actions ? Operational
                  90 days ago
                  99.42 % uptime
                  Today
            Packages ? Operational
                  90 days ago
                  100.0 % uptime
                  Today
            Pages ? Operational
                  90 days ago
                  99.64 % uptime
                  Today
            Copilot Operational
                  90 days ago
                  99.93 % uptime
                  Today
            Codespaces ? Operational
                  90 days ago
                  99.97 % uptime
                  Today
            Copilot AI Model Providers Operational
                  90 days ago
                  99.88 % uptime
                  Today
          Operational
          Degraded Performance
          Partial Outage
          Major Outage
          Maintenance
              Major outage
              Partial outage
              No downtime recorded on this day.
              No data exists for this day.
              had a major outage.
              had a partial outage.

            Related

            No incidents or maintenance related to this downtime.

      Past Incidents

        Aug 12, 2026

            Incident with Pull Requests and Issues
              Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
              Aug 12, 16:41 UTC
              Update - We identified the source of errors affecting Pull Requests, Issues, and Search on GitHub.com and have applied a mitigation. A database index hint was referencing an index that had been removed by a recent migration, causing query failures for some users. We disabled the problematic configuration and are seeing recovery across affected services. We are continuing to monitor to confirm full resolution.
              Aug 12, 16:38 UTC
              Monitoring - The degradation affecting Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.
              Aug 12, 16:35 UTC
              Update - We are investigating reports of errors affecting Pull Requests and Issues on GitHub.com. Some users may encounter 500 errors when loading pull request and issue pages. Our engineering teams are actively investigating the root cause, which appears to be related to a database infrastructure issue. We will provide an update as soon as we have more information.
              Aug 12, 16:24 UTC
              Investigating - We are investigating reports of degraded performance for Issues and Pull Requests
              Aug 12, 16:16 UTC

        Aug 11, 2026

            Incident with GraphQL API Requests
              Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
              Aug 11, 20:06 UTC
              Update - We have identified and mitigated increased error rates affecting GraphQL API requests. A fix to increase service capacity has been deployed and error rates have returned to normal levels. We are resolving this incident.
              Aug 11, 20:06 UTC
              Monitoring - The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
              Aug 11, 16:49 UTC
              Update - We have returned to a healthy baseline on GraphQL API requests. We will continue to work on investigations into the errors seen during this incident.
              Aug 11, 16:49 UTC
              Update - We are investigating reports of a small increase in error rates affecting GraphQL API requests. We are working on increasing capacity and continue to investigate the increased errors. We will provide another update when we have more information
              Aug 11, 15:28 UTC
              Investigating - We are investigating reports of degraded performance for API Requests
              Aug 11, 14:50 UTC

        Aug 10, 2026

            Disruption with Copilot for access to some models
              Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
              Aug 10, 21:50 UTC
              Update - We have deployed and validated the fix to prevent immediate reoccurrence. We will be performing additional work to limit these kinds of failures in the future.
              Aug 10, 21:50 UTC
              Update - The issue has been mitigated across all affected environments. We are currently deploying on a fix to prevent reoccurrence. We will provide another update once the fix has been deployed.
              Aug 10, 21:19 UTC
              Update - The degradation has been mitigated. We are monitoring to ensure stability.
              Aug 10, 20:49 UTC
              Monitoring - We are currently investigating reports of some Copilot users experiencing issues accessing certain models. Affected users may see errors or degraded functionality when attempting to use specific models. We are actively working on a fix and will provide updates as we have more information.
              Aug 10, 20:39 UTC
              Investigating - We are investigating reports of impacted performance for some GitHub services.
              Aug 10, 20:27 UTC
            Disruption with creation of fine grained personal access tokens
              Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
              Aug 10, 18:46 UTC
              Update - We identified the source of the issue affecting creation of fine-grained personal access tokens and have applied a mitigation. Users should now be able to create new fine-grained tokens successfully. We are continuing to monitor to confirm full recovery.
              Aug 10, 18:22 UTC
              Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
              Aug 10, 18:21 UTC
              Update - We are investigating reports of users being unable to create fine-grained Personal Access Tokens. Attempting to create a new token redirects the user back to the token overview page without an error message, but the token was not created.
              Aug 10, 18:09 UTC
              Investigating - We are investigating reports of impacted performance for some GitHub services.
              Aug 10, 18:02 UTC

        Aug 9, 2026

        No incidents reported.

        Aug 8, 2026

        No incidents reported.

        Aug 7, 2026

            Incident with Actions
              Resolved - On August 6, 2026, between 15:05 UTC and 00:14 UTC on August 7, GitHub Actions experienced degraded availability. During the incident, workflow runs failed or remained queued for an extended period of time. Customers using both GitHub-hosted and self-hosted runners were affected. At peak, 71% of workflow runs experienced infrastructure failures and 75% of the remaining workflow runs were delayed by more than 5 minutes.

              The incident was triggered by a routine deployment to an internal Actions service responsible for processing events and generating Actions jobs. The deployment exposed an existing capacity and concurrency weakness. As pods were replaced during the deployment, remaining capacity became saturated, causing services to crash and triggering a cascading impact across multiple clusters and downstream services.

              These services recovered at 17:00 after expanding capacity, throttling incoming webhook-triggered work to allow the system to recover, and increasing processing capacity for the backlog of affected events.

              As the incident progressed, a backlog of work accumulated across the systems responsible for assigning jobs to runners. Due to a latent bug in one of the services responsible for job assignment, runners were getting assigned jobs that were no longer valid and then getting stuck retrying those jobs, preventing them from picking up valid work.

              This second stage of impact was mitigated by deploying changes to prevent runners from repeatedly attempting to acquire invalid jobs. These mitigations allowed the accumulated queues to drain and Actions to recover to normal operation.

              Some Actions Runner Controller (ARC) runners remained stuck after the incident. A mitigation deployed during the incident inadvertently affected these runners, causing some to remain offline until they were manually recovered. We subsequently rolled back the change and are adding automatic recovery in upcoming Runner and ARC releases.

              Some jobs created during the incident were also left stuck unable to be retried or canceled. CLI and UI solutions for customers to address these were shared at https://github.com/orgs/community/discussions/204152#discussioncomment-17946043 .

              To prevent recurrence, we are making improvements to deployment and capacity safeguards for the affected services, strengthening monitoring for the conditions that preceded the incident, improving the resiliency and recovery of queued work and runner assignment, and adding automatic recovery for self-hosted runners affected by similar failure conditions. We are also making additional improvements to reduce the risk of cascading failures and accelerate recovery during large-scale Actions disruptions.
              Aug 7, 02:04 UTC
              Update - During the incident, some Actions Runner Controller (ARC) runner pods became stuck in an idle state. Affected users can delete those pods using kubectl or redeploy their Actions Runner Controller application. ARC will automatically create replacement runners.

              The next releases of Actions Runner and Actions Runner Controller will include an automatic recovery mechanism, preventing the need for these manual steps in the future.

              Some workflow-triggering events, including push and pull request events, were not processed during the incident and cannot be replayed automatically. Customers may need to repeat the triggering action by pushing a new commit, updating the pull request, or manually re-running the workflow where applicable.
              Aug 7, 02:03 UTC
              Update - We’re investigating reports that some Actions Runner Controller runners are taking longer than expected to recover. We’ll provide an update as our investigation progresses.
              Aug 7, 00:59 UTC
              Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
              Aug 7, 00:06 UTC
              Update - The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.
              Aug 7, 00:05 UTC
              Update - System-wide queues have been drained, and new jobs are being processed as expected. The fix for self-hosted runners not picking up jobs has been fully rolled out.

              Webhook-triggered Actions workflows have been restored to full throughput. GitHub Pages, Copilot code review, and Copilot coding agent are showing recovery. Migrations using GitHub Enterprise Importer remain paused as a precaution.

              We are monitoring all affected services for sustained recovery and will provide another update shortly.
              Aug 7, 00:01 UTC
              Update -
              System-wide queues have been drained, and new jobs are being processed as expected. The fix for self-hosted runners not picking up jobs has been fully rolled out.

              Webhook-triggered Actions workflows have been restored to full throughput. GitHub Pages, Copilot code review, and Copilot coding agent are showing recovery. Migrations using GitHub Enterprise Importer remain paused as a precaution.

              We are monitoring all affected services for sustained recovery and will provide another update shortly.
              Aug 7, 00:01 UTC
              Update - We have deployed fixes that address runners being assigned invalid jobs and are taking additional steps to clear the backlog of affected jobs. Job completion rates for running workflows have improved significantly, with success rates now at 99%. Global queues for hosted runner assignment are nearly burned down and concurrency queues for customers are being processed. Another change was deployed to accelerate processing the backlog of job requests.

              We are gradually restoring throughput for webhook-triggered Actions workflows and monitoring system stability. We have deployed a fix for self-hosted runners that were not picking up jobs and are enabling it incrementally.

              GitHub Pages, Copilot code review, and Copilot coding agent may still experience intermittent failures or delays. Migrations using GitHub Enterprise Importer remain paused.

              We continue to monitor recovery across all affected services and will provide another update as conditions improve.
              Aug 6, 23:13 UTC
              Update - We continue to make progress on the issue affecting GitHub Actions. We have deployed a fix that addresses runners being assigned jobs that are no longer valid, and are seeing improvement in job completion rates. For workflow runs that are starting, success rates have increased significantly and are now at 97%. Standard and larger runners are now draining queued work. A change is also in progress to mitigate issues with existing self-hosted runners that are not picking up jobs.

              Webhook triggers remain throttled to support recovery. Many push and pull request events are not yet triggering new workflow runs, and we are working to safely restore full throughput.

              GitHub Pages, Copilot code review, and Copilot coding agent may still experience failures or delays. Migrations using GitHub Enterprise Importer remain paused.

              We are continuing to monitor recovery and will provide another update as conditions improve.
              Aug 6, 22:18 UTC
              Update - We are continuing to work on an issue affecting GitHub Actions. Webhook triggers remain throttled to aid recovery, so many push and pull request events are not triggering new workflow runs.

              We identified runners being assigned jobs that are no longer valid and are deploying a change to address this issue. Both GitHub-hosted and self-hosted runners are affected.

              Copilot code review, Copilot coding agent, and GitHub Pages may experience failures or delays. Migrations using GitHub Enterprise Importer have been paused to support mitigation efforts.
              Aug 6, 21:30 UTC
              Update - We are continuing to work on an issue affecting GitHub Actions. Webhook triggers are currently throttled to help with recovery and and we are processing approximately 15% of webhooks, so many events such as pushes and pull requests are not triggering workflow runs. Of jobs queued, approximately 65% are succeeding, improved from a low of 30 to 40% earlier in this incident.

              We have narrowed the remaining impact to runners that are stuck retrying jobs that are no longer available. Both GitHub-hosted and self-hosted runners are affected, and we are working to recover them.

              Copilot code review, Copilot coding agent, and migrations using GitHub Enterprise Importer may also be affected.
              Aug 6, 20:34 UTC
              Update - We are continuing to work on an issue affecting GitHub Actions.

              Capacity remains constrained and jobs may still be delayed or fail while it recovers gradually. Customers using self-hosted runners may see errors or rate limiting when runners register.

              Copilot code review, Copilot coding agent, and migrations using GitHub Enterprise Importer may also be affected. Webhook deliveries may be delayed.

              Our engineers remain actively engaged.
              Aug 6, 19:43 UTC
              Update - We are continuing to work on an issue affecting multiple GitHub services.

              Workflow runs are still failing, and jobs may remain queued for an extended period before starting or may time out. Jobs using GitHub-hosted runners are particularly affected while capacity is constrained.

              Customers using self-hosted runners may see errors or rate limiting when runners register.

              Copilot code review, Copilot coding agent, and migrations using GitHub Enterprise Importer may also be affected. Webhook deliveries may be delayed.

              Recovery is taking longer than we expected, and engineers remain actively engaged.
              Aug 6, 18:46 UTC
              Update - We are continuing to work on an issue affecting multiple GitHub services.

              Workflow runs are still failing or delayed in starting, and some queued jobs may time out.

              Customers using self-hosted runners may see errors or rate limiting when runners register.

              Copilot code review, Copilot coding agent, hosted runners, and migrations using GitHub Enterprise Importer may also be affected.

              Webhook deliveries may be delayed.

              Engineers have applied further mitigations and are continuing to work towards full recovery.
              Aug 6, 18:11 UTC
              Update - We are continuing to work on an issue affecting multiple GitHub services.

              Workflow runs are failing or delayed in starting, and some queued jobs may time out.

              Copilot code review, Copilot coding agent, hosted runners, and migrations using GitHub Enterprise Importer might also affected.

              Webhook deliveries may be delayed.

              Engineers have applied a number of mitigations and are rolling out a further fix across all affected systems now.
              Aug 6, 17:40 UTC
              Update - We are continuing to work on the issue affecting GitHub Actions.

              Workflow runs are still failing or delayed in starting, and some queued jobs may time out.

              Some requests to the Actions API are returning errors. Customers running migrations with GitHub Enterprise Importer may see failures.

              Our engineers have applied several mitigations and are rolling out a further fix now.
              Aug 6, 17:02 UTC
              Update - Actions and Pages are experiencing degraded availability. We are continuing to investigate.
              Aug 6, 16:33 UTC
              Update - We are continuing to work on the issue affecting GitHub Actions.

              Some workflow runs are still delayed or failing to complete, and some requests to the Actions API are returning errors.

              Customers running migrations with GitHub Enterprise Importer may also see failures.

              Engineers are actively working towards full recovery.
              Aug 6, 16:27 UTC
              Update - Pages is experiencing degraded performance. We are continuing to investigate.
              Aug 6, 16:27 UTC
              Update - Pages is operating normally.
              Aug 6, 16:19 UTC
              Update - Pages is experiencing degraded performance. We are continuing to investigate.
              Aug 6, 15:53 UTC
              Update - We are investigating errors affecting GitHub Actions. Some workflow runs are failing to start or failing partway through, and some requests to the Actions REST API are returning errors.

              Some customers may also see unexpected rate limiting in their workflows.

              Engineers have identified the source of the disruption and are actively working on a mitigation
              Aug 6, 15:45 UTC
              Update - Actions is experiencing degraded availability. We are continuing to investigate.
              Aug 6, 15:41 UTC
              Investigating - We are investigating reports of degraded performance for Actions
              Aug 6, 15:22 UTC

        Aug 6, 2026

            Incident with Pages - Deployment Lag
              Resolved - On August 6, 2026, at 07:00 UTC, a configuration change inadvertently reduced the capacity of the service that processes GitHub Pages deployments. As traffic increased over the following hours, latency in the deployment pipeline progressively increased.

              At 12:09 UTC, latency crossed the alerting threshold and the team began investigating. We reverted the invalid configuration and applied additional mitigations, including reducing status deployment processing to lower the load on our Redis cluster. Latency returned to normal levels at 15:40 UTC.

              Customer impact occurred from 11:34 to 15:32 UTC. During this period, we failed to process approximately 128,000 deployments.

              We have updated our alerts to detect elevated processing latency sooner and to notify us immediately when latency causes deployment processing failures. We've confirmed this incident was not fully captured by our availability metrics. In the coming days, we'll update how GitHub Pages availability is measured so incidents like this are accurately reflected going forward.
              Aug 6, 16:22 UTC
              Monitoring - The degradation affecting Pages has been mitigated. We are monitoring to ensure stability.
              Aug 6, 15:50 UTC
              Investigating - We are investigating reports of degraded performance for Pages
              Aug 6, 15:03 UTC

        Aug 5, 2026

            Some Copilot Cloud Agent jobs not starting
              Resolved - On August 5, 2026, between 11:02 and 11:54 UTC, the GitHub Copilot cloud agent service was degraded and new cloud agent jobs were delayed from starting. During this period 100% of newly submitted agent jobs were affected. The incident was limited to delay of cloud agent jobs. No jobs were lost and the queued backlog was processed by 13:00 UTC. This was due to an internal rate limit used to protect service availability that was enabled more broadly than intended delaying more traffic than expected.

              The service recovered when the rate limit window expired. We then tuned the control so it no longer affected unrelated coding agent traffic.

              We are working to improve the control's scoping and our monitoring and alerting to reduce our time to detection and mitigation of similar issues in the future.
              Aug 5, 13:00 UTC
              Update - Copilot cloud agent jobs have recovered and the backlog of delayed jobs is being processed.
              Aug 5, 12:10 UTC
              Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
              Aug 5, 12:01 UTC
              Investigating - We are investigating reports of impacted performance for some GitHub services.
              Aug 5, 11:38 UTC

        Aug 4, 2026

        No incidents reported.

        Aug 3, 2026

            Incident with Copilot
              Resolved - On 2026-08-03, between 06:52 and 11:25 UTC, some GitHub Copilot users experienced errors when using chat and agent features. Requests to list the available models failed, and because every chat or agent interaction begins by retrieving the list of models, affected users saw their requests fail. On average about 3% of these model-listing requests failed during the incident (roughly 97% succeeded), but failures were significantly higher during peak-traffic periods, at times approaching 100% for the affected internal lookups. Approximately 4,066 users were affected in a single 60-minute window, concentrated among IDE-based clients. The underlying AI models themselves remained healthy throughout.

              The incident was caused by an increase in how often clients requested the model list, which pushed an internal user-authorization lookup past a rate limit; the rate-limited responses were surfaced to users as errors. We mitigated the impact by increasing how long Copilot caches that authorization lookup, which reduced load on the internal service, and we have additional capacity and rate-limit changes in progress. To prevent recurrence we are improving monitoring for this class of failure, adjusting cache and rate-limit settings, and coordinating with client teams on request patterns.
              Aug 3, 11:25 UTC
              Monitoring - The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability.
              Aug 3, 11:19 UTC
              Update - We are still seeing intermittent errors with Copilot, and are continuing to investigate and consider mitigations.
              Aug 3, 10:35 UTC
              Update - We are experiencing degraded availability for chat & agent models in Copilot. Multiple models are impacted and customers may experience requests failing. We are investigating and will provide an update as soon as possible.
              Aug 3, 09:54 UTC
              Investigating - We are investigating reports of degraded performance for Copilot
              Aug 3, 09:53 UTC

        Aug 2, 2026

        No incidents reported.

        Aug 1, 2026

            Incident with Copilot AI Model Providers
              Resolved - On August 1, 2026, between 17:47 UTC and 18:20 UTC, users of the Fable 5 model in GitHub Copilot experienced increased request failures and latency. The average failure rate across all Copilot requests was 0.007%, while failures for Fable 5 peaked at 5.6%. Other models remained available. This was caused by degradation of an upstream model provider.

              The affected endpoint recovered, and we monitored the service until error rates and latency returned to normal levels. We are working to add endpoint redundancy to mitigate similar provider issues in the future.
              Aug 1, 18:44 UTC
              Update - The issues with our upstream model provider have been resolved, and Fable 5 is once again available in Copilot products and IDE surfaces.

              We will continue monitoring to ensure stability, but mitigation is complete.
              Aug 1, 18:23 UTC
              Monitoring - The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.
              Aug 1, 18:20 UTC
              Update - We are experiencing degraded availability for the Fable 5 model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot.
              Aug 1, 18:20 UTC
              Update - We are seeing increased error rates from specific upstream AI Model Providers
              Aug 1, 18:03 UTC
              Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers
              Aug 1, 18:03 UTC
            Degraded availability GPT 5.6 Luna
              Resolved - On August 1st, 2026, the GPT-5.6 Luna model in GitHub Copilot experienced degraded availability in intermittent time intervals between ~08:05 UTC and ~16:30 UTC. Specifically the timeframes observed were 10:00-10:20 UTC, 10:45-11:50 UTC, 13:00-14:25 UTC, and 16:00-16:30 UTC. During this time, requests to GPT-5.6 Luna in Copilot chat and IDE surfaces frequently failed or timed out. This was caused by an issue with an upstream model provider. Other Copilot models were not affected, and users could continue working by selecting another model or 'Auto'. Availability for GPT-5.6 Luna fully recovered once the provider resolved their outage at 16:30 UTC.
              Aug 1, 12:30 UTC
              Update - The issues with our upstream model provider have been resolved, and GPT-5.6 Luna is once again available in Copilot products and IDE surfaces.
              We will continue monitoring to ensure stability, but mitigation is complete.
              Aug 1, 12:29 UTC
              Update - We keep working with our upstream model provider, and are observing recovery. We continue monitoring to ensure stability.
              Aug 1, 12:13 UTC
              Update - We are experiencing degraded availability for the GPT-5.6 Luna model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot
              Aug 1, 11:20 UTC
              Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers
              Aug 1, 11:16 UTC

        Jul 31, 2026

        No incidents reported.

        Jul 30, 2026

            Copilot model Claude Fable 5 experiencing elevated errors
              Resolved - On July 30, 2026, the Claude Fable 5 model in GitHub Copilot experienced degraded availability for approximately 73 minutes, from 08:33 to 09:46 UTC. During this time, requests to Claude Fable 5 in Copilot chat and IDE surfaces frequently failed or timed out. This was caused by an issue with an upstream model provider. Other Copilot models were not affected, and users could continue working by selecting another model or 'Auto'. Availability for Claude Fable 5 fully recovered once the provider resolved their outage at 09:46 UTC, and we confirmed resolution at 10:12 UTC.
              Jul 30, 10:12 UTC
              Update - The issues with our upstream model provider have been resolved, and Claude Fable 5 is once again available in Copilot products and IDE surfaces.

              We will continue monitoring to ensure stability, but mitigation is complete.
              Jul 30, 10:11 UTC
              Update - We are experiencing degraded availability for the Claude Fable 5 model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot.
              Jul 30, 09:17 UTC
              Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers
              Jul 30, 09:07 UTC

        Jul 29, 2026

            Incident with Copilot AI Model Providers
              Resolved - On July 29, 2026, between 19:45 UTC and 21:51 UTC, users of the Fable 5 model in GitHub Copilot experienced increased request failures and latency. The average failure rate across all Copilot requests was 0.006%, while failures for Fable 5 peaked at 21%. Other models remained available. This was caused by degradation of an upstream model provider.

              The affected endpoint recovered, and we monitored the service until error rates and latency returned to normal levels. We are working to add endpoint redundancy to mitigate similar provider issues in the future.
              Jul 29, 21:51 UTC
              Update - The external ai model provider has resolved the issues, and we have verified Copilot's traffic is fully recovered.
              Jul 29, 21:51 UTC
              Update - The external AI model provider is continuing to investigate.
              Jul 29, 21:08 UTC
              Update - The external AI model provider has identified the issue and is working to resolve.
              Jul 29, 20:38 UTC
              Update - We are investigating increased error rates affecting GitHub Copilot requests to external AI model providers. Some users may experience failures or degraded performance when using Copilot features.
              Jul 29, 20:18 UTC
              Update - We are seeing increased error rates with requests to specific model providers.
              Jul 29, 20:07 UTC
              Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers
              Jul 29, 20:07 UTC
            Incident with Actions
              Resolved - On July 29, 2026, from 14:51 UTC to 15:28 UTC, GitHub Actions experienced elevated REST API request timeouts and errors, failures registering runners, and delayed workflow run starts for customers whose traffic was served by a single infrastructure site. This was caused by an under-provisioned internal Actions service in that site: under increased load its instances ran out of memory and became unresponsive, and because Actions API requests wait synchronously on that service, requests routed through the affected site stalled and timed out. During the incident, approximately 2% of workflows were delayed. Requests served by other sites remained unaffected. Both standard and larger hosted runners routed through the affected site could see delayed job starts.

              The issue was mitigated by scaling out the runner-administration service in the affected site and increasing the replica count, which restored API availability and returned workflow run starts to normal. We are working to add horizontal autoscaling, memory-saturation alerting, and scaling-forecast monitoring for this service, along with responder playbooks, to reduce the likelihood of similar issues in the future.
              Jul 29, 16:00 UTC
              Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
              Jul 29, 15:40 UTC
              Update - We are investigating an issue affecting GitHub Actions. Some customers may experience timeouts or failures with runner registration and workflow runs may be delayed during startup. Our team is actively working to mitigate the impact by scaling capacity across additional infrastructure.
              Jul 29, 15:34 UTC
              Investigating - We are investigating reports of degraded availability for Actions
              Jul 29, 15:26 UTC
      ← Incident History Powered by Atlassian Statuspage

          Subscribe to our developer newsletter

          Get tips, technical guides, and best practices. Twice a month. Right in your inbox.

          Subscribe

          Product

            * Features
            * Enterprise
            * Copilot
            * Security
            * Pricing
            * Team
            * Resources
            * Roadmap
            * Compare GitHub

          Platform

            * Developer API
            * Partners
            * Education
            * GitHub CLI
            * GitHub Desktop
            * GitHub Mobile

          Support

            * Docs
            * Community Forum
            * Professional Services
            * Skills
            * Contact GitHub

          Company

            * About
            * Customer stories
            * Blog
            * The ReadME Project
            * Careers
            * Newsroom
            * Inclusion
            * Social Impact
            * Shop
            * © GitHub, Inc.
            * Terms
            * Privacy (Updated 08/2022)
            * 
            * 
            * 
            * 
            * 
            * 
            *