GitHub Enterprise Cloud AU Outage History

GitHub Enterprise Cloud AU is up right now

There were 20 GitHub Enterprise Cloud AU outages since February 2, 2026 totaling 69h 50m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://au.githubstatus.com

Minor April 23, 2026

Incident with Pull Requests

Detected by Pingoru
Apr 23, 2026, 07:50 PM UTC
Resolved
Apr 23, 2026, 09:43 PM UTC
Duration
1h 52m
Affected: prod-ae-01 - Pull Requests (Pull Requests)
Timeline · 4 updates
  1. investigating Apr 23, 2026, 07:50 PM UTC

    We are investigating reports of degraded performance for Pull Requests

  2. investigating Apr 23, 2026, 07:58 PM UTC

    We have identified a regression in merge queue behavior present when squash merging or rebasing. We have identified the root-cause and are in the process of reverting the change.

  3. investigating Apr 23, 2026, 09:39 PM UTC

    Pull Requests is operating normally.

  4. resolved Apr 23, 2026, 09:43 PM UTC

    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.

Read the full incident report →

Minor April 23, 2026

Disruption with users unable to start Claude and Codex agent task from the web

Detected by Pingoru
Apr 23, 2026, 07:29 PM UTC
Resolved
Apr 23, 2026, 07:42 PM UTC
Duration
13m
Timeline · 3 updates
  1. investigating Apr 23, 2026, 07:29 PM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating Apr 23, 2026, 07:33 PM UTC

    We have identified the root cause of the issue and are working on mitigation.

  3. resolved Apr 23, 2026, 07:42 PM UTC

    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.

Read the full incident report →

Minor April 22, 2026

Disruption with some GitHub services

Detected by Pingoru
Apr 22, 2026, 07:53 PM UTC
Resolved
Apr 22, 2026, 10:43 PM UTC
Duration
2h 50m
Affected: prod-ae-01 - Issues (Issues)
Timeline · 6 updates
  1. investigating Apr 22, 2026, 07:53 PM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating Apr 22, 2026, 07:55 PM UTC

    Issues is experiencing degraded performance. We are continuing to investigate.

  3. investigating Apr 22, 2026, 08:02 PM UTC

    Copilot @-mentions on pull requests are currently not being processed by Copilot Cloud Agent. We have found the issue and are investigating remediations.

  4. investigating Apr 22, 2026, 08:37 PM UTC

    We have identified the root cause of the disruption affecting Copilot Coding Agent and Issues. Copilot @-mentions on pull requests are not being processed, and some issue-related functionality may be degraded. A fix has been developed and is being applied.

  5. investigating Apr 22, 2026, 10:09 PM UTC

    We have identified the root cause of the disruption affecting Copilot Coding Agent and Issues. A fix is being deployed.

  6. resolved Apr 22, 2026, 10:43 PM UTC

    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.

Read the full incident report →

Major April 22, 2026

Disruption with Copilot chat and Copilot Coding Agent

Detected by Pingoru
Apr 22, 2026, 03:35 PM UTC
Resolved
Apr 22, 2026, 07:18 PM UTC
Duration
3h 42m
Timeline · 8 updates
  1. investigating Apr 22, 2026, 03:35 PM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating Apr 22, 2026, 03:43 PM UTC

    We are aware of users seeing errors interacting with Copilot chat on github.com and Copilot cloud agent. We have identified the cause and are investigating remediations.

  3. investigating Apr 22, 2026, 04:24 PM UTC

    We continue to work on mitigation for Copilot chat and cloud agent.

  4. investigating Apr 22, 2026, 04:58 PM UTC

    Mitigation is progressing for Copilot chat and cloud agent.

  5. investigating Apr 22, 2026, 05:40 PM UTC

    Mitigation is progressing for Copilot chat and cloud agent recovery.

  6. investigating Apr 22, 2026, 05:49 PM UTC

    We are now seeing recovery for Copilot cloud agent.

  7. investigating Apr 22, 2026, 06:05 PM UTC

    Copilot cloud agent and chat are mitigated for github.com.

  8. resolved Apr 22, 2026, 07:18 PM UTC

    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.

Read the full incident report →

Minor April 10, 2026

Problems with third-party Claude and Codex Agent sessions not being listed in the agents tab dashboard

Detected by Pingoru
Apr 10, 2026, 01:07 PM UTC
Resolved
Apr 10, 2026, 01:28 PM UTC
Duration
21m
Timeline · 3 updates
  1. investigating Apr 10, 2026, 01:07 PM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating Apr 10, 2026, 01:08 PM UTC

    We are investigating third party Claude and Codex Cloud Agent sessions not being listed in the agents tab dashboard.

  3. resolved Apr 10, 2026, 01:28 PM UTC

    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.

Read the full incident report →

Minor April 2, 2026

Copilot Coding Agent failing to start some jobs

Detected by Pingoru
Apr 02, 2026, 04:18 PM UTC
Resolved
Apr 02, 2026, 04:30 PM UTC
Duration
12m
Timeline · 3 updates
  1. investigating Apr 02, 2026, 04:18 PM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating Apr 02, 2026, 04:28 PM UTC

    When assigning tasks to Copilot Cloud Agent, the task will appear to be working, but may not actually be running. We are investigating.

  3. resolved Apr 02, 2026, 04:30 PM UTC

    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.

Read the full incident report →

Minor March 31, 2026

Incident with Pull Requests: High percentage of 500s

Detected by Pingoru
Mar 31, 2026, 03:05 PM UTC
Resolved
Apr 01, 2026, 01:11 PM UTC
Duration
22h 6m
Affected: prod-ae-01 - Pull Requests (Pull Requests)
Timeline · 15 updates
  1. investigating Mar 31, 2026, 03:05 PM UTC

    We are investigating reports of degraded performance for Pull Requests

  2. investigating Mar 31, 2026, 03:06 PM UTC

    We are seeing a higher than average number of 500s due to timeouts across GitHub services. We have a potential mitigation in flight and are continuing to investigate.

  3. investigating Mar 31, 2026, 03:39 PM UTC

    We are investigating increased 500 errors affecting GitHub services. You may experience intermittent failures when using Pull Requests and other features. We are actively working to identify and resolve the underlying cause.

  4. investigating Mar 31, 2026, 04:15 PM UTC

    We are continuing to investigate increased 500 errors affecting GitHub services. You may experience intermittent failures when using Pull Requests and other features. We are actively working to identify and resolve the underlying cause.

  5. investigating Mar 31, 2026, 04:35 PM UTC

    We are seeing recovery in latency and timeouts of requests related to pull requests, even though 500s are still elevated. While we are continuing to investigate, we are applying a mitigation and expect further recovery after it is applied.

  6. investigating Mar 31, 2026, 05:16 PM UTC

    We identified an issue causing increased errors when accessing Pull Requests. The mitigation is being applied across our infrastructure and we will continue to provide updates as the mitigation rolls out.

  7. investigating Mar 31, 2026, 06:42 PM UTC

    We continue to experience elevated error rates affecting Pull Requests. An earlier fix resolved one component of the issue, but some users may still encounter intermittent timeouts when viewing or interacting with pull requests. Our teams are actively investigating the remaining causes.

  8. investigating Mar 31, 2026, 07:28 PM UTC

    Error rates remain elevated across multiple pull request endpoints. We are pursuing multiple potential mitigations.

  9. investigating Mar 31, 2026, 09:12 PM UTC

    We continue to see a small subset of repositories experiencing timeouts and elevated latency in Pull Requests, affecting under 1% of requests.

  10. investigating Mar 31, 2026, 09:16 PM UTC

    The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.

  11. resolved Mar 31, 2026, 09:23 PM UTC

    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.

  12. investigating Mar 31, 2026, 09:24 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  13. investigating Mar 31, 2026, 09:28 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  14. investigating Mar 31, 2026, 10:12 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  15. resolved Apr 01, 2026, 01:11 PM UTC

    This incident was resolved on Mar 31, 2026 but unintentionally reopened. There is no impact at this time, we apologize for the confusion.

Read the full incident report →

Major March 24, 2026

Teams Github Notifications App is down

Detected by Pingoru
Mar 24, 2026, 05:00 PM UTC
Resolved
Mar 24, 2026, 07:51 PM UTC
Duration
2h 50m
Timeline · 5 updates
  1. investigating Mar 24, 2026, 05:00 PM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating Mar 24, 2026, 05:09 PM UTC

    We found an issue impacting notifications from GitHub to Microsoft Teams. We are working on mitigation and will keep users updated on progress towards mitigation.

  3. investigating Mar 24, 2026, 05:43 PM UTC

    We are experiencing degraded availability from Azure APIs, which is impacting notifications from GitHub to Microsoft Teams. We are working with Azure to resolve the issue.

  4. investigating Mar 24, 2026, 06:50 PM UTC

    We are experiencing degraded availability from Azure Teams APIs, which is impacting notifications from GitHub to Microsoft Teams. We are awaiting resolution from Azure.

  5. resolved Mar 24, 2026, 07:51 PM UTC

    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.

Read the full incident report →

Minor March 20, 2026

Disruption with Copilot Coding Agent Sessions

Detected by Pingoru
Mar 20, 2026, 12:58 AM UTC
Resolved
Mar 20, 2026, 12:22 PM UTC
Duration
11h 24m
Timeline · 2 updates
  1. investigating Mar 20, 2026, 12:58 AM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. resolved Mar 20, 2026, 12:22 PM UTC

    Impact resolved.

Read the full incident report →

Major March 19, 2026

Issues with Copilot Coding Agent

Detected by Pingoru
Mar 19, 2026, 10:41 AM UTC
Resolved
Mar 19, 2026, 02:32 PM UTC
Duration
3h 51m
Affected: prod-ae-01 - Copilot (Copilot)
Timeline · 9 updates
  1. investigating Mar 19, 2026, 10:41 AM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating Mar 19, 2026, 10:43 AM UTC

    We are investigating reports of errors when accessing Copilot Coding Agent features. Users may be unable to view or start coding agent tasks through the Agents interface. Our engineers are actively working to restore full functionality.

  3. investigating Mar 19, 2026, 11:19 AM UTC

    We believe we have identified an underlying credential issue and are working to resolve that across impacted environments.

  4. investigating Mar 19, 2026, 12:00 PM UTC

    We have resolved the underlying credential issue and have verified that users can see and interact with their Copilot Coding Agent tasks. We are now investigating issues with some Coding Agent tasks completing successfully.

  5. investigating Mar 19, 2026, 12:32 PM UTC

    We are investigating reports of Copilot coding agent session logs not loading and sessions intermittently not starting. Users are able to see their tasks and create new ones.

  6. investigating Mar 19, 2026, 01:45 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  7. investigating Mar 19, 2026, 02:02 PM UTC

    We are investigating reports that Copilot Coding Agent session logs are not available in the UI.

  8. investigating Mar 19, 2026, 02:25 PM UTC

    Copilot is operating normally.

  9. resolved Mar 19, 2026, 02:32 PM UTC

    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.

Read the full incident report →

Minor March 5, 2026

Some OpenAI models degraded in Copilot

Detected by Pingoru
Mar 05, 2026, 12:47 AM UTC
Resolved
Mar 05, 2026, 01:13 AM UTC
Duration
25m
Affected: prod-ae-01 - Copilot (Copilot)
Timeline · 7 updates
  1. investigating Mar 05, 2026, 12:47 AM UTC

    We are investigating reports of degraded performance for Copilot

  2. investigating Mar 05, 2026, 12:48 AM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  3. investigating Mar 05, 2026, 12:50 AM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  4. investigating Mar 05, 2026, 12:53 AM UTC

    We are experiencing degraded availability for the gpt-5.3-codex model in Copilot Chat, VS Code and other Copilot products. This is due to an issue with an upstream model provider. We are working with them to resolve the issue.

  5. investigating Mar 05, 2026, 01:02 AM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  6. investigating Mar 05, 2026, 01:13 AM UTC

    The issues with our upstream model provider have been resolved, and gpt-5.3-codex is once again available in Copilot Chat and across IDE integrations. We will continue monitoring to ensure stability, but mitigation is complete.

  7. resolved Mar 05, 2026, 01:13 AM UTC

    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.

Read the full incident report →

Minor March 3, 2026

Claude Opus 4.6 Fast not appearing for some Copilot users

Detected by Pingoru
Mar 03, 2026, 08:31 PM UTC
Resolved
Mar 03, 2026, 09:11 PM UTC
Duration
39m
Affected: prod-ae-01 - Copilot (Copilot)
Timeline · 6 updates
  1. investigating Mar 03, 2026, 08:31 PM UTC

    We are investigating reports of degraded performance for Copilot

  2. investigating Mar 03, 2026, 08:43 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  3. investigating Mar 03, 2026, 09:03 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  4. investigating Mar 03, 2026, 09:05 PM UTC

    We believe that all expected users still have access to Claude Opus 4.6. We confirm that no users have lost access.

  5. investigating Mar 03, 2026, 09:11 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  6. resolved Mar 03, 2026, 09:11 PM UTC

    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.

Read the full incident report →

Major March 3, 2026

Incident with Copilot and Actions

Detected by Pingoru
Mar 03, 2026, 06:59 PM UTC
Resolved
Mar 03, 2026, 07:32 PM UTC
Duration
32m
Affected: prod-ae-01 - Copilot (Copilot)
Timeline · 50 updates
  1. investigating Mar 03, 2026, 06:59 PM UTC

    We are investigating reports of degraded performance for Copilot

  2. investigating Mar 03, 2026, 07:00 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  3. investigating Mar 03, 2026, 07:00 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  4. investigating Mar 03, 2026, 07:01 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  5. investigating Mar 03, 2026, 07:01 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  6. investigating Mar 03, 2026, 07:01 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  7. investigating Mar 03, 2026, 07:02 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  8. investigating Mar 03, 2026, 07:03 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  9. investigating Mar 03, 2026, 07:04 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  10. investigating Mar 03, 2026, 07:04 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  11. investigating Mar 03, 2026, 07:05 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  12. investigating Mar 03, 2026, 07:06 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  13. investigating Mar 03, 2026, 07:06 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  14. investigating Mar 03, 2026, 07:06 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  15. investigating Mar 03, 2026, 07:08 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  16. investigating Mar 03, 2026, 07:09 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  17. investigating Mar 03, 2026, 07:11 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  18. investigating Mar 03, 2026, 07:11 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  19. investigating Mar 03, 2026, 07:12 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  20. investigating Mar 03, 2026, 07:14 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  21. investigating Mar 03, 2026, 07:14 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  22. investigating Mar 03, 2026, 07:15 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  23. investigating Mar 03, 2026, 07:15 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  24. investigating Mar 03, 2026, 07:15 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  25. investigating Mar 03, 2026, 07:17 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  26. investigating Mar 03, 2026, 07:17 PM UTC

    We've identified the issue and have applied a mitigation. We're seeing recovery of services. We continue to montitor for full recovery.

  27. investigating Mar 03, 2026, 07:18 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  28. investigating Mar 03, 2026, 07:19 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  29. investigating Mar 03, 2026, 07:20 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  30. investigating Mar 03, 2026, 07:23 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  31. investigating Mar 03, 2026, 07:24 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  32. investigating Mar 03, 2026, 07:24 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  33. investigating Mar 03, 2026, 07:25 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  34. investigating Mar 03, 2026, 07:25 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  35. investigating Mar 03, 2026, 07:25 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  36. investigating Mar 03, 2026, 07:27 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  37. investigating Mar 03, 2026, 07:28 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  38. investigating Mar 03, 2026, 07:28 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  39. investigating Mar 03, 2026, 07:28 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  40. investigating Mar 03, 2026, 07:28 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  41. investigating Mar 03, 2026, 07:29 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  42. investigating Mar 03, 2026, 07:29 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  43. investigating Mar 03, 2026, 07:31 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  44. investigating Mar 03, 2026, 07:31 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  45. investigating Mar 03, 2026, 07:31 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  46. investigating Mar 03, 2026, 07:31 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  47. investigating Mar 03, 2026, 07:32 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  48. investigating Mar 03, 2026, 07:32 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  49. investigating Mar 03, 2026, 07:32 PM UTC

    Copilot and Copilot are experiencing degraded performance. We are continuing to investigate.

  50. resolved Mar 03, 2026, 07:32 PM UTC

    Copilot and Copilot are operating normally.

Read the full incident report →

Minor February 26, 2026

Incident with Copilot

Detected by Pingoru
Feb 26, 2026, 10:22 AM UTC
Resolved
Feb 26, 2026, 11:06 AM UTC
Duration
44m
Affected: prod-ae-01 - Copilot (Copilot)
Timeline · 6 updates
  1. investigating Feb 26, 2026, 10:22 AM UTC

    We are investigating reports of degraded performance for Copilot

  2. investigating Feb 26, 2026, 10:47 AM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  3. investigating Feb 26, 2026, 10:59 AM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  4. investigating Feb 26, 2026, 11:00 AM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  5. investigating Feb 26, 2026, 11:06 AM UTC

    Copilot is operating normally.

  6. resolved Feb 26, 2026, 11:06 AM UTC

    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.

Read the full incident report →

Minor February 25, 2026

Incident with Copilot Agent Sessions impacting CCA/CCR

Detected by Pingoru
Feb 25, 2026, 04:38 PM UTC
Resolved
Feb 25, 2026, 05:03 PM UTC
Duration
24m
Affected: prod-ae-01 - Copilot (Copilot)
Timeline · 5 updates
  1. investigating Feb 25, 2026, 04:38 PM UTC

    We are investigating reports of degraded performance for Copilot

  2. investigating Feb 25, 2026, 04:40 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  3. investigating Feb 25, 2026, 04:44 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  4. resolved Feb 25, 2026, 04:44 PM UTC

    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.

  5. resolved Feb 25, 2026, 05:03 PM UTC

    Copilot is operating normally.

Read the full incident report →

Minor February 20, 2026

Incident with Copilot GPT-5.1-Codex

Detected by Pingoru
Feb 20, 2026, 10:02 AM UTC
Resolved
Feb 20, 2026, 11:44 AM UTC
Duration
1h 41m
Affected: prod-ae-01 - Copilot (Copilot)
Timeline · 9 updates
  1. investigating Feb 20, 2026, 10:02 AM UTC

    We are investigating reports of degraded performance for Copilot

  2. investigating Feb 20, 2026, 10:02 AM UTC

    We are experiencing degraded availability for the GPT 5.1 Codex model in Copilot Chat, VS Code and other Copilot products. This is due to an issue with an upstream model provider. We are working with them to resolve the issue. Other models are available and working as expected.

  3. investigating Feb 20, 2026, 10:15 AM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  4. investigating Feb 20, 2026, 10:36 AM UTC

    We are still experiencing degraded availability for the GPT 5.1 Codex model in Copilot Chat, VS Code and other Copilot products. This is due to an issue with an upstream model provider. We are working with them to resolve the issue.

  5. investigating Feb 20, 2026, 10:50 AM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  6. investigating Feb 20, 2026, 11:17 AM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  7. investigating Feb 20, 2026, 11:19 AM UTC

    The issues with our upstream model provider have been resolved, and GPT 5.1 Codex is once again available in Copilot Chat and across IDE integrations [VSCode, Visual Studio, JetBrains]. We will continue monitoring to ensure stability, but mitigation is complete.

  8. resolved Feb 20, 2026, 11:41 AM UTC

    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.

  9. resolved Feb 20, 2026, 11:44 AM UTC

    Copilot is operating normally.

Read the full incident report →

Minor February 13, 2026

Disruption with some GitHub services regarding file upload

Detected by Pingoru
Feb 13, 2026, 10:30 PM UTC
Resolved
Feb 13, 2026, 10:58 PM UTC
Duration
28m
Timeline · 2 updates
  1. investigating Feb 13, 2026, 10:30 PM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. resolved Feb 13, 2026, 10:58 PM UTC

    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.

Read the full incident report →

Minor February 12, 2026

Intermittent disruption with Copilot completions and inline suggestions

Detected by Pingoru
Feb 12, 2026, 02:06 PM UTC
Resolved
Feb 12, 2026, 04:50 PM UTC
Duration
2h 43m
Timeline · 4 updates
  1. investigating Feb 12, 2026, 02:06 PM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating Feb 12, 2026, 02:08 PM UTC

    We are experiencing degraded availability in some regions for Copilot completions and suggestions. We are working to resolve the issue.

  3. investigating Feb 12, 2026, 03:33 PM UTC

    We are experiencing degraded availability in Western Europe for Copilot completions and suggestions. We are working to resolve the issue.

  4. resolved Feb 12, 2026, 04:50 PM UTC

    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.

Read the full incident report →

Minor February 9, 2026

Copilot Policy Propagation Delays

Detected by Pingoru
Feb 09, 2026, 04:29 PM UTC
Resolved
Feb 10, 2026, 12:52 AM UTC
Duration
8h 22m
Affected: prod-ae-01 - Copilot (Copilot)
Timeline · 25 updates
  1. investigating Feb 09, 2026, 04:29 PM UTC

    We are investigating reports of degraded performance for Copilot

  2. investigating Feb 09, 2026, 04:30 PM UTC

    We’ve identified an issue where Copilot policy updates are not propagating correctly for some customers. This may prevent newly enabled models from appearing when users try to access them. The team is actively investigating the cause and working on a resolution. We will provide updates as they...

  3. investigating Feb 09, 2026, 04:32 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  4. investigating Feb 09, 2026, 04:58 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  5. investigating Feb 09, 2026, 05:21 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  6. investigating Feb 09, 2026, 05:23 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  7. investigating Feb 09, 2026, 05:24 PM UTC

    We're continuing to investigate a an issue where Copilot policy updates are not propagating correctly for all customers. This may prevent newly enabled models from appearing when users try to access them.

  8. investigating Feb 09, 2026, 05:46 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  9. investigating Feb 09, 2026, 06:06 PM UTC

    We're continuing to investigate an issue where Copilot policy updates are not propagating correctly for a subset of enterprise users. This may prevent newly enabled models from appearing when users try to access them.

  10. investigating Feb 09, 2026, 06:08 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  11. investigating Feb 09, 2026, 06:31 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  12. investigating Feb 09, 2026, 06:49 PM UTC

    We're continuing to investigate an issue where Copilot policy updates are not propagating correctly for a subset of enterprise users. This may prevent newly enabled models from appearing when users try to access them. Next update in two hours.

  13. investigating Feb 09, 2026, 06:51 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  14. investigating Feb 09, 2026, 08:37 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  15. investigating Feb 09, 2026, 08:39 PM UTC

    We're continuing to investigate an issue where Copilot policy updates are not propagating correctly for a subset of enterprise users. This may prevent newly enabled models from appearing when users try to access them. Next update in two hours.

  16. investigating Feb 09, 2026, 09:22 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  17. investigating Feb 09, 2026, 10:10 PM UTC

    We're continuing to investigate an issue where Copilot policy updates are not propagating correctly for a subset of enterprise users. This may prevent newly enabled models from appearing when users try to access them. Next update in two hours.

  18. investigating Feb 10, 2026, 12:26 AM UTC

    We're continuing to address an issue where Copilot policy updates are not propagating correctly for a subset of enterprise users. This may prevent newly enabled models from appearing when users try to access them. This issue is understand and we are working to get the mitigation applied. Next...

  19. investigating Feb 10, 2026, 12:51 AM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  20. investigating Feb 10, 2026, 12:51 AM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  21. investigating Feb 10, 2026, 12:52 AM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  22. investigating Feb 10, 2026, 12:52 AM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  23. investigating Feb 10, 2026, 12:52 AM UTC

    Copilot is operating normally.

  24. investigating Feb 10, 2026, 12:52 AM UTC

    Copilot is operating normally.

  25. resolved Feb 10, 2026, 12:52 AM UTC

    Copilot is operating normally.

Read the full incident report →

Major February 2, 2026

Incident with Actions

Detected by Pingoru
Feb 02, 2026, 08:33 PM UTC
Resolved
Feb 03, 2026, 12:56 AM UTC
Duration
4h 22m
Affected: prod-ae-01 - Pages (Pages)prod-ae-01 - Actions (Actions)prod-ae-01 - Copilot (Copilot)
Timeline · 33 updates
  1. investigating Feb 02, 2026, 08:33 PM UTC

    We are investigating reports of degraded availability for Actions and Pages

  2. investigating Feb 02, 2026, 08:36 PM UTC

    Actions and Pages are experiencing degraded availability. We are continuing to investigate.

  3. investigating Feb 02, 2026, 08:53 PM UTC

    Actions and Pages are experiencing degraded availability. We are continuing to investigate.

  4. investigating Feb 02, 2026, 09:13 PM UTC

    We continue to investigate failures impacting GitHub Actions hosted-runner jobs. We have identified the root cause and are working with our upstream provider to mitigate. This is also impacting GitHub features that rely on GitHub Actions (for example, Copilot Coding Agent and Dependabot).

  5. investigating Feb 02, 2026, 09:15 PM UTC

    Actions and Pages are experiencing degraded availability. We are continuing to investigate.

  6. investigating Feb 02, 2026, 09:27 PM UTC

    Actions and Pages are experiencing degraded availability. We are continuing to investigate.

  7. investigating Feb 02, 2026, 09:30 PM UTC

    Actions, Copilot and Pages are experiencing degraded availability. We are continuing to investigate.

  8. investigating Feb 02, 2026, 09:38 PM UTC

    Actions, Copilot and Pages are experiencing degraded availability. We are continuing to investigate.

  9. investigating Feb 02, 2026, 10:03 PM UTC

    Actions, Copilot and Pages are experiencing degraded availability. We are continuing to investigate.

  10. investigating Feb 02, 2026, 10:10 PM UTC

    We continue to investigate failures impacting GitHub Actions hosted-runner jobs. We're waiting on our upstream provider to apply the identified mitigations, and we're preparing to resume job processing as safely as possible.

  11. investigating Feb 02, 2026, 10:26 PM UTC

    Actions, Copilot and Pages are experiencing degraded availability. We are continuing to investigate.

  12. investigating Feb 02, 2026, 10:48 PM UTC

    Actions, Copilot and Pages are experiencing degraded availability. We are continuing to investigate.

  13. investigating Feb 02, 2026, 10:53 PM UTC

    Our upstream provider has applied a mitigation to address queuing and job failures on hosted runners. Telemetry shows improvement, and we are monitoring closely for full recovery.

  14. investigating Feb 02, 2026, 11:11 PM UTC

    Actions, Copilot and Pages are experiencing degraded availability. We are continuing to investigate.

  15. investigating Feb 02, 2026, 11:31 PM UTC

    Actions, Copilot and Pages are experiencing degraded availability. We are continuing to investigate.

  16. investigating Feb 02, 2026, 11:34 PM UTC

    Actions, Copilot and Pages are experiencing degraded availability. We are continuing to investigate.

  17. investigating Feb 02, 2026, 11:34 PM UTC

    Actions, Copilot and Pages are experiencing degraded availability. We are continuing to investigate.

  18. investigating Feb 02, 2026, 11:37 PM UTC

    Actions, Copilot and Pages are experiencing degraded availability. We are continuing to investigate.

  19. investigating Feb 02, 2026, 11:37 PM UTC

    Actions, Copilot and Pages are experiencing degraded availability. We are continuing to investigate.

  20. investigating Feb 02, 2026, 11:40 PM UTC

    Actions, Copilot and Pages are experiencing degraded availability. We are continuing to investigate.

  21. investigating Feb 02, 2026, 11:41 PM UTC

    Actions, Copilot and Pages are experiencing degraded availability. We are continuing to investigate.

  22. investigating Feb 02, 2026, 11:43 PM UTC

    Actions, Copilot and Pages are experiencing degraded performance. We are continuing to investigate.

  23. investigating Feb 02, 2026, 11:50 PM UTC

    Based on our telemetry, most customers should see full recovery from failing GitHub Actions jobs on hosted runners. We are monitoring closely to confirm complete recovery. Other GitHub features that rely on GitHub Actions (for example, Copilot Coding Agent and Dependabot) should also see recovery.

  24. investigating Feb 03, 2026, 12:17 AM UTC

    Actions, Copilot and Pages are experiencing degraded performance. We are continuing to investigate.

  25. investigating Feb 03, 2026, 12:21 AM UTC

    Actions, Copilot and Pages are experiencing degraded performance. We are continuing to investigate.

  26. investigating Feb 03, 2026, 12:54 AM UTC

    Actions, Copilot and Pages are experiencing degraded performance. We are continuing to investigate.

  27. investigating Feb 03, 2026, 12:54 AM UTC

    Actions, Copilot and Pages are experiencing degraded performance. We are continuing to investigate.

  28. investigating Feb 03, 2026, 12:55 AM UTC

    Actions, Copilot and Pages are operating normally.

  29. investigating Feb 03, 2026, 12:55 AM UTC

    Actions, Copilot and Pages are operating normally.

  30. investigating Feb 03, 2026, 12:55 AM UTC

    Actions, Copilot and Pages are operating normally.

  31. investigating Feb 03, 2026, 12:55 AM UTC

    Actions, Copilot and Pages are operating normally.

  32. investigating Feb 03, 2026, 12:56 AM UTC

    Actions, Copilot and Pages are operating normally.

  33. resolved Feb 03, 2026, 12:56 AM UTC

    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.

Read the full incident report →

Looking to track GitHub Enterprise Cloud AU downtime and outages?

Pingoru polls GitHub Enterprise Cloud AU's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when GitHub Enterprise Cloud AU reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track GitHub Enterprise Cloud AU alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring GitHub Enterprise Cloud AU for free

5 free monitors · No credit card required