GitHub lists these components: Pull Requests, Actions.

When did the incident start and end?

It started at 2026-11-10 16:10 UTC and ended at 2026-11-10 17:55 UTC. It lasted 1 h 44 min.

How do I get alerts for GitHub?

Subscribe to the GitHub live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of GitHub. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

GitHubIncident ·

Incident with Git Operations and Pull Requests

Q: What happened?

GitHub reported "Incident with Git Operations and Pull Requests" on its status page at 2026-11-10 16:10 UTC. Git operations and Pull Requests had elevated response times and failures, and Actions workflows triggered from Pull Requests were delayed. GitHub reports that the incident is resolved. It lasted 1 hour and 44 minutes.

ResolvedOfficial update

Git operations and Pull Requests had elevated response times and failures, and Actions workflows triggered from Pull Requests were delayed. GitHub reports that the incident is resolved. It lasted 1 hour and 44 minutes.

State

Resolved

Started

Lasted

1 h 44 min

Worst impact

Major outage

Timeline

9 updates

16:1016:3617:0217:2917:55

Major outageDegradedUpdate postedTimes in UTC

Investigating

1 h 44 min 100%

Updates

Times in UTC

As posted by GitHub

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.

Investigating

We continue to investigate elevated response times for Git operations and pull requests. Actions workflows are recovering. Pull request processing has shown some improvement, but users continue to experience delays and failures. We’re monitoring the impact and working to restore normal service.

Investigating

Actions is operating normally.

Investigating

Pull Requests is experiencing degraded performance. We are continuing to investigate.

Investigating

We continue to investigate elevated response times for Git operations and pull requests. Some pull-request processing and Actions workflows are improving, but delays and failures persist. We're monitoring the impact and working to restore normal service.

Investigating

Actions is experiencing degraded availability. We are continuing to investigate.

Investigating

We're investigating elevated response times for Git operations and pull requests. GitHub Actions workflows that are triggered from Pull Requests are delayed. We're working to mitigate the impact and will share updates as we learn more.

Investigating

Actions and Pull Requests are experiencing degraded availability. We are continuing to investigate.

Investigating

We are investigating reports of degraded performance for Actions and Pull Requests

Affected components

Pull RequestsActions

GitHub in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 17 min

This incident

1.4× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

20 h 7 min

median 1 h 17 min

90 days agoToday

Other GitHub incidents

All incidents

GitHub·Degraded availability for GPT-5.3 Codex and GPT-5.6 models in Copilot

GitHub reports degraded availability for the GPT-5.3 Codex, GPT-5.6 Luna, and GPT-5.6 Sol models in Copilot products and IDE surfaces. GitHub mitigated the issue and monitored the service for stability. The outage is resolved and lasted 50 minutes.

Resolved

GitHub·Incident with Actions and Checks API

GitHub Actions, the Checks API, Webhooks, and Pages had an outage. GitHub reports that the incident is resolved. It lasted 47 minutes.

Resolved

GitHub·Incident with Webhooks and Actions

GitHub reports a partial outage that affects Webhooks and Actions. Actions runs and webhook deliveries had delays and degraded availability. GitHub resolved the incident in 1 hour and 50 minutes.

Resolved

GitHub·Increased timeouts due to surge in anonymous users

GitHub reports 504 Gateway Timeout errors for anonymous and unauthenticated requests. The errors affect users who are not logged in and release downloads. Logged-in users and authenticated requests are unaffected. GitHub resolved the incident after 3 hours and 11 minutes.

Resolved

GitHub·Increase in timeouts for some unauthenticated users

GitHub reports timeouts for some unauthenticated users on API Requests. GitHub identified a problem component and redeployed it. The incident is resolved. It lasted 1 hour and 57 minutes.

Resolved

Follow GitHub

Your coding agent knows when GitHub is down, and tells you when a failure is theirs, not yours. You can also get GitHub incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "github" and tell me if GitHub has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.live/feed.xml?providers=github

Slack

/feed subscribe https://outages.live/feed.xml?providers=github

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane