githubstatus.com (@githubstatus.com.web.brid.gy)

Incident with Webhooks Mar 9, 17:03 UTC **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. Mar 9, 17:03 UTC **Update** - Webhooks is operating normally. Mar 9, 15:56 UTC **Update** - We are experiencing latency on the API and UI endpoints. We are working to resolve the issue. Mar 9, 15:50 UTC **Investigating** - We are investigating reports of degraded performance for Webhooks

09.03.2026 17:03 👍 0 🔁 0 💬 0 📌 0

Incident with Codespaces Mar 9, 03:51 UTC **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. Mar 9, 03:51 UTC **Update** - This incident has been resolved. New Codespace creation requests are now completing successfully. Mar 9, 03:32 UTC **Update** - We are seeing recovery, with the failure rate for new Codespace creation requests dropping from 5% to about 3%. Mar 9, 03:04 UTC **Update** - We are seeing about 5% of new Codespace creation requests failing. We are investigating the root cause and identifying the impacted regions. Mar 9, 03:04 UTC **Investigating** - We are investigating reports of degraded performance for Codespaces

09.03.2026 03:51 👍 0 🔁 0 💬 0 📌 0

Incident with Webhooks Mar 6, 23:28 UTC **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. Mar 6, 23:28 UTC **Update** - Webhooks is operating normally. Mar 6, 23:26 UTC **Update** - We have deployed a fix and are observing a full recovery. The affected endpoint was the webhook deliveries API (https://docs.github.com/en/rest/repos/webhooks?apiVersion=2022-11-28#list-deliveries-for-a-repository-webhook) and its organization and integration variants. We will continue monitoring to confirm stability. Mar 6, 22:35 UTC **Update** - We are preparing a new mitigation for the issue affecting the webhook deliveries API (https://docs.github.com/en/rest/repos/webhooks?apiVersion=2022-11-28#list-deliveries-for-a-repository-webhook) and its organization and integration variants. Overall impact remains low, with under 1% of requests failing for a subset of customers. Mar 6, 21:34 UTC **Update** - The previous mitigation did not resolve the issue. We are investigating further. The affected endpoint is the webhook deliveries API (https://docs.github.com/en/rest/repos/webhooks?apiVersion=2022-11-28#list-deliveries-for-a-repository-webhook) and its organization and integration variants. Overall impact remains low, with under 1% of requests failing for a subset of customers. Mar 6, 20:18 UTC **Update** - We have deployed a fix for the issue causing some users to experience intermittent failures when accessing the Webhooks API and configuration pages. We are monitoring to confirm full recovery. Mar 6, 19:39 UTC **Update** - We continue working on mitigations to restore service. Mar 6, 19:07 UTC **Update** - We continue working on mitigations to restore service. Mar 6, 18:39 UTC **Update** - We continue working on mitigations to restore service. Mar 6, 18:07 UTC **Update** - We continue working on mitigations to restore full service. Mar 6, 17:43 UTC **Update** - Our engineers have identified the root cause and are actively implementing mitigations to restore full service. Mar 6, 17:19 UTC **Update** - This problem is impacting less than 1% of UI and webhook API calls. Mar 6, 17:12 UTC **Update** - We are investigating an issue affecting a subset of customers experiencing errors when viewing webhook delivery histories and retrying webhook deliveries. UI and webhook API is impacted. Engineers have identified the cause and are actively working on mitigation. Mar 6, 16:58 UTC **Investigating** - We are investigating reports of degraded performance for Webhooks

06.03.2026 23:28 👍 0 🔁 0 💬 0 📌 0

Actions is experiencing degraded availability Mar 5, 23:55 UTC **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. Mar 5, 23:40 UTC **Update** - We are close to full recovery. Actions and dependent services should be functioning normally now. Mar 5, 23:37 UTC **Update** - Actions is experiencing degraded performance. We are continuing to investigate. Mar 5, 23:15 UTC **Update** - Actions and dependent services, including Pages, are recovering. Mar 5, 23:00 UTC **Update** - We applied a mitigation and we should see a recovery soon. Mar 5, 22:54 UTC **Update** - Actions is experiencing degraded availability. We are continuing to investigate. Mar 5, 22:53 UTC **Investigating** - We are investigating reports of degraded performance for Actions

05.03.2026 23:55 👍 0 🔁 0 💬 0 📌 0

Multiple services are affected, service degradation Mar 5, 19:30 UTC **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. Mar 5, 19:17 UTC **Update** - Webhooks is operating normally. Mar 5, 19:05 UTC **Update** - Actions is operating normally. Mar 5, 18:59 UTC **Update** - Actions is now fully recovered. Mar 5, 18:15 UTC **Update** - The queue of requested Actions jobs continues to make progress. Job delays are now approximately 6 minutes and continuing to decrease. Mar 5, 17:48 UTC **Update** - We are back to queueing Actions workflow runs at nominal rates and we are monitoring the clearing of queued runs during the incident. Mar 5, 17:25 UTC **Update** - We have applied mitigations for connection failures across backend resources and we are observing a recovery in queueing Actions workflow runs. Mar 5, 16:52 UTC **Update** - We are observing delays in queuing Actions workflow runs. We’re still investigating the causes of these delays. Mar 5, 16:47 UTC **Update** - Webhooks is experiencing degraded availability. We are continuing to investigate. Mar 5, 16:41 UTC **Update** - Actions is experiencing degraded availability. We are continuing to investigate. Mar 5, 16:35 UTC **Investigating** - We are investigating reports of degraded performance for Actions

05.03.2026 19:30 👍 0 🔁 0 💬 0 📌 0

Disruption with some GitHub services Mar 5, 01:30 UTC **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. Mar 5, 01:30 UTC **Update** - Copilot coding agent mission control is fully restored. Tasks are now listed as expected. Mar 5, 01:21 UTC **Update** - Users were temporarily unable to see tasks listed in mission control surfaces. The ability to submit new tasks, view existing tasks via direct link, or manage tasks was unaffected throughout. A revert is currently being deployed and we are seeing recovery. Mar 5, 01:13 UTC **Investigating** - We are investigating reports of impacted performance for some GitHub services.

05.03.2026 01:30 👍 0 🔁 0 💬 0 📌 0

Some OpenAI models degraded in Copilot Mar 5, 01:13 UTC **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. Mar 5, 01:13 UTC **Update** - 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. Mar 5, 00:53 UTC **Update** - 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. Mar 5, 00:47 UTC **Investigating** - We are investigating reports of degraded performance for Copilot

05.03.2026 01:13 👍 0 🔁 0 💬 0 📌 0

Claude Opus 4.6 Fast not appearing for some Copilot users Mar 3, 21:11 UTC **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. Mar 3, 21:05 UTC **Update** - We believe that all expected users still have access to Claude Opus 4.6. We confirm that no users have lost access. Mar 3, 20:31 UTC **Investigating** - We are investigating reports of degraded performance for Copilot

03.03.2026 21:11 👍 0 🔁 0 💬 0 📌 0

Delayed visibility of newly added issues on project boards Mar 3, 01:40 UTC **Update** - The delay for project board updates has increased to up to 3 hours. We've identified a potential cause and are working on remediation. Mar 3, 00:52 UTC **Update** - Project board updates — including adding issues, pull requests, and changing fields such as "Status" — are currently delayed by 1–2 hours. Normal behavior is near-real-time. We're actively investigating the root cause. Mar 3, 00:05 UTC **Update** - The impact extends beyond adding issues to project boards. Adding pull requests and updating fields such as "Status" may also be affected. We're continuing to investigate the root cause. Mar 2, 23:46 UTC **Update** - Newly added issues are taking 30–60 minutes to appear on project boards, compared to the normal near-real-time behavior. We're investigating the root cause and possible mitigations. Mar 2, 23:12 UTC **Update** - Newly added issues can take up to 30 minutes to appear on project boards. We're investigating the cause of this delay. Mar 2, 23:11 UTC **Update** - Issues is experiencing degraded performance. We are continuing to investigate. Mar 2, 23:10 UTC **Investigating** - We are investigating reports of impacted performance for some GitHub services.

03.03.2026 01:40 👍 0 🔁 0 💬 0 📌 0

Incident with Pull Requests /pulls Mar 2, 22:04 UTC **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. Mar 2, 22:04 UTC **Update** - The issue on https://github.com/pulls is now fully resolved. All tabs are working again. Mar 2, 21:04 UTC **Update** - We're deploying a fix for pull request filtering. Full rollout across all regions is expected within 60 minutes. Mar 2, 20:02 UTC **Update** - We are experiencing issues with the Pull Requests dashboard that prevent users from filtering their pull requests. We have identified a mitigation and are deploying a fix. We'll post another update by 21:00 UTC. Mar 2, 19:23 UTC **Update** - We are seeing a degraded experience when attempting to filter the /pulls dashboard. We are working on a mitigation. Mar 2, 19:11 UTC **Investigating** - We are investigating reports of degraded performance for Pull Requests

02.03.2026 22:04 👍 0 🔁 0 💬 0 📌 0

Incident with Copilot agent sessions Feb 27, 23:49 UTC **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. Feb 27, 23:45 UTC **Update** - We have identified the cause of the elevated errors and are rolling out a fix to production. We are observing initial recovery in Copilot agent sessions. Feb 27, 23:35 UTC **Update** - We are investigating networking issues with some requests to our models. Feb 27, 23:18 UTC **Update** - We are investigating a spike in errors in Copilot agent sessions Feb 27, 23:18 UTC **Investigating** - We are investigating reports of degraded performance for Copilot

27.02.2026 23:49 👍 0 🔁 0 💬 0 📌 0

Code view fails to load when content contains some non-ASCII characters Feb 27, 06:04 UTC **Resolved** - Starting February 26, 2026 at 22:10 UTC through February 27, 05:50 UTC, the repository browsing UI was degraded and users were unable to load pages for files and directories with non-ASCII characters (including Japanese, Chinese, and other non-Latin scripts). On average, the error rate was 0.014% and peaked at 0.06% of requests to the service. Affected users saw 404 errors when navigating to repository directories and files with non-ASCII names. This was due to a code change that altered how file and directory names were processed, which caused incorrectly formatted data to be stored in an application cache. We mitigated the incident by deploying a fix that invalidated the affected cache entries and progressively rolling it out across all production environments. We are working to improve our pre-production testing to cover non-ASCII character handling, establish better cache invalidation mechanisms, and enhance our monitoring to detect this type of failure mode earlier, to reduce our time to detection and mitigation of issues like this one in the future. Feb 27, 06:03 UTC **Update** - We have cleared all caches and everything is operating normally. Feb 27, 05:21 UTC **Update** - We have mitigated the issue but are working on invalidating caches in order to fix the issue for all impacted repos. Feb 27, 04:17 UTC **Update** - We have performed a mitigation but some repositories may still see issues. We are working on a full mitigation. Feb 27, 03:28 UTC **Update** - We are looking into recent code changes to mitigate the error loading some code view pages. Feb 27, 03:08 UTC **Investigating** - We are investigating reports of impacted performance for some GitHub services.

27.02.2026 06:04 👍 0 🔁 0 💬 0 📌 0

High latency on webhook API requests Feb 27, 00:04 UTC **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. Feb 27, 00:02 UTC **Update** - Webhooks is experiencing degraded performance. We are continuing to investigate. Feb 27, 00:01 UTC **Investigating** - We are investigating reports of impacted performance for some GitHub services.

27.02.2026 00:04 👍 0 🔁 0 💬 0 📌 0

Incident with Copilot Feb 26, 11:06 UTC **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. Feb 26, 11:06 UTC **Update** - Copilot is operating normally. Feb 26, 10:22 UTC **Investigating** - We are investigating reports of degraded performance for Copilot

26.02.2026 11:06 👍 0 🔁 0 💬 0 📌 0

Incident with Copilot Agent Sessions impacting CCA/CCR Feb 25, 16:44 UTC **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. Feb 25, 16:38 UTC **Investigating** - We are investigating reports of degraded performance for Copilot

25.02.2026 16:44 👍 0 🔁 0 💬 0 📌 0

Code search experiencing degraded performance Feb 24, 00:46 UTC **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. Feb 24, 00:38 UTC **Update** - We have identified a cause for the latency and timeouts and have implemented a fix. We are observing initial recovery now. Feb 23, 23:10 UTC **Update** - Customers using code search continue to see increased latency and timeout errors. We are working to mitigate issues on the affected shard. Feb 23, 22:22 UTC **Update** - Elevated latency and timeouts for code search is isolated to a single shard experiencing elevated CPU. We are taking steps to isolate and mitigate the affected shard. Feb 23, 21:18 UTC **Update** - Elevated latency and timeouts for code search is isolated to a single shard experiencing elevated CPU. We are continuing to investigate the cause and steps to mitigate. Feb 23, 20:33 UTC **Update** - We are continuing to investigate elevated latency and timeouts for code search. Feb 23, 19:59 UTC **Investigating** - We are investigating reports of impacted performance for some GitHub services.

24.02.2026 00:46 👍 0 🔁 0 💬 0 📌 0

Incident with Issues and Pull Requests Search Feb 23, 21:30 UTC **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. Feb 23, 21:24 UTC **Update** - Some customers are seeing timeout errors when searching for issues or pull requests. Team is currently investigating a fix. Feb 23, 21:16 UTC **Investigating** - We are investigating reports of degraded performance for Issues and Pull Requests

23.02.2026 21:30 👍 0 🔁 0 💬 0 📌 0

Incident with Actions Feb 23, 17:03 UTC **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. Feb 23, 16:17 UTC **Investigating** - We are investigating reports of degraded performance for Actions

23.02.2026 17:03 👍 0 🔁 0 💬 0 📌 0

Incident with Copilot Feb 23, 16:19 UTC **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. Feb 23, 15:59 UTC **Update** - Copilot is operating normally. Feb 23, 15:59 UTC **Update** - The issues with our upstream model provider have been resolved, and Haiku 4.5 is once again available in Copilot Chat and across IDE integrations. We will continue monitoring to ensure stability, but mitigation is complete. Feb 23, 15:13 UTC **Update** - Our provider has recovered and we are not seeing errors but we are awaiting a signal from them that the issue will not regress before we go green. Feb 23, 14:56 UTC **Update** - We are experiencing degraded availability for the Haiku 4.5 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. Feb 23, 14:56 UTC **Investigating** - We are investigating reports of degraded performance for Copilot

23.02.2026 16:19 👍 0 🔁 0 💬 0 📌 0

Extended job start delays for larger hosted runners Feb 20, 20:41 UTC **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. Feb 20, 20:36 UTC **Update** - The team continues to investigate issues with some larger runner jobs being queued for a long time. We are though seeing improvement in the queue times. We will continue providing updates on the progress towards mitigation. Feb 20, 20:01 UTC **Update** - We are investigating reports of degraded performance for Larger Hosted Runners Feb 20, 20:00 UTC **Investigating** - We are investigating reports of impacted performance for some GitHub services.

20.02.2026 20:41 👍 0 🔁 0 💬 0 📌 0

Incident with Copilot GPT-5.1-Codex Feb 20, 11:41 UTC **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. Feb 20, 11:19 UTC **Update** - 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. Feb 20, 10:36 UTC **Update** - 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. Feb 20, 10:02 UTC **Update** - 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. Feb 20, 10:02 UTC **Investigating** - We are investigating reports of degraded performance for Copilot

20.02.2026 11:41 👍 0 🔁 0 💬 0 📌 0

Degraded performance in merge queue Feb 18, 19:20 UTC **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. Feb 18, 19:18 UTC **Update** - We have seen significant recovery in merge queue we are continuing to monitor for any other degraded services. Feb 18, 18:27 UTC **Update** - We are investigating reports of issues with merge queue. We will continue to keep users updated on progress towards mitigation. Feb 18, 18:26 UTC **Update** - Pull Requests is experiencing degraded performance. We are continuing to investigate. Feb 18, 18:25 UTC **Investigating** - We are investigating reports of impacted performance for some GitHub services.

18.02.2026 19:20 👍 0 🔁 0 💬 0 📌 0

Intermittent authentication failures on GitHub Feb 17, 19:06 UTC **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. Feb 17, 18:55 UTC **Update** - We are continuing to monitor the mitigation and continuing to see signs of recovery. Feb 17, 18:18 UTC **Update** - We have rolled out a mitigation and are seeing signs of recovery and are continuing to monitor. Feb 17, 17:46 UTC **Update** - We have identified a low rate of authentication failures affecting GitHub App server to server tokens, GitHub Actions authentication tokens, and git operations. Some customers may experience intermittent API request failures when using these tokens. We believe we've identified the cause and are working to mitigate impact. Feb 17, 17:46 UTC **Investigating** - We are investigating reports of degraded performance for Actions and Git Operations

17.02.2026 19:06 👍 0 🔁 0 💬 0 📌 0

Disruption with some GitHub services regarding file upload Feb 13, 22:58 UTC **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. Feb 13, 22:30 UTC **Investigating** - We are investigating reports of impacted performance for some GitHub services.

13.02.2026 22:58 👍 0 🔁 0 💬 0 📌 0

Disruption with some GitHub services Feb 12, 20:34 UTC **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. Feb 12, 19:59 UTC **Update** - Next Edit Suggestions availability is recovering. We are continuing to monitor until fully restored. Feb 12, 19:18 UTC **Update** - We are experiencing degraded availability in Australia and Brazil for Copilot completions and suggestions. We are working to resolve the issue Feb 12, 18:46 UTC **Update** - We are experiencing degraded availability in Australia for Copilot completions and suggestions. We are working to resolve the issue Feb 12, 18:36 UTC **Investigating** - We are investigating reports of impacted performance for some GitHub services.

12.02.2026 20:34 👍 0 🔁 0 💬 0 📌 0

Intermittent disruption with Copilot completions and inline suggestions Feb 12, 15:33 UTC **Update** - We are experiencing degraded availability in Western Europe for Copilot completions and suggestions. We are working to resolve the issue. Feb 12, 14:08 UTC **Update** - We are experiencing degraded availability in some regions for Copilot completions and suggestions. We are working to resolve the issue. Feb 12, 14:06 UTC **Investigating** - We are investigating reports of impacted performance for some GitHub services.

12.02.2026 15:33 👍 0 🔁 0 💬 0 📌 0

Disruption with some GitHub services Feb 12, 11:12 UTC **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. Feb 12, 11:01 UTC **Update** - We have resolved the issue and are seeing full recovery. Feb 12, 10:39 UTC **Update** - We are investigating an issue with downloading repository archives that include Git LFS objects. Feb 12, 10:38 UTC **Investigating** - We are investigating reports of impacted performance for some GitHub services.

12.02.2026 11:12 👍 0 🔁 0 💬 0 📌 0

Incident with Codespaces Feb 12, 08:32 UTC **Update** - We now understand the source of the VM create/resume failures and are working with our partners to mitigate the impact. Feb 12, 08:02 UTC **Update** - We are seeing an increase in Codespaces creation and resuming failures across multiple regions, primarily in EMEA. Our team are analysing the situation and are working to mitigate this impact. While we are working, customers are advised to create Codespaces in US East and US West regions via the "New with options..." button when creating a Codespace. More updates as we have them. Feb 12, 07:53 UTC **Investigating** - We are investigating reports of degraded availability for Codespaces

12.02.2026 08:32 👍 0 🔁 0 💬 0 📌 0

Disruption with some GitHub services Feb 12, 00:59 UTC **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. Feb 11, 21:33 UTC **Update** - Actions is experiencing capacity constraints with larger hosted runners, leading to high wait times. Standard hosted labels and self-hosted runners are not impacted. The issue is mitigated and we are monitoring recovery. Feb 11, 19:37 UTC **Update** - We're continuing to work toward mitigation with our capacity provider, and adding capacity. Feb 11, 19:00 UTC **Update** - Actions is experiencing capacity constraints with larger hosted runners, leading to high wait times. Standard hosted labels and self-hosted runners are not impacted. We're working with the capacity provider to mitigate the impact. Feb 11, 18:58 UTC **Investigating** - We are investigating reports of impacted performance for some GitHub services.

12.02.2026 00:59 👍 0 🔁 0 💬 0 📌 0

Incident with API Requests Feb 11, 17:15 UTC **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. Feb 11, 17:13 UTC **Update** - We've observed recovery for the GraphQL service latency. Feb 11, 16:54 UTC **Update** - We're continuing to remediate the service degradation and scaling out to further mitigate the potential for latency impact. Feb 11, 15:54 UTC **Update** - We've identified a dependency of GraphQL that is in a degraded state and are working on remediating the issue. Feb 11, 15:27 UTC **Update** - We're investigating increased latency for GraphQL traffic. Feb 11, 15:26 UTC **Investigating** - We are investigating reports of degraded performance for API Requests

11.02.2026 17:15 👍 0 🔁 0 💬 0 📌 0

githubstatus.com

Latest posts by githubstatus.com @githubstatus.com.web.brid.gy