outages.live
Live
GitHubIncident ·

Incident with Pull Requests

Partial outageOfficial update
0

GitHub Pull Requests has degraded availability. Some merge attempts time out. GitHub reports that mitigating action is in progress. The issue affected 3% of requests and is now below 1%. GitHub continues to monitor recovery.

State

Investigating

Started

Ongoing for

1 h 3 min

Worst impact

Partial outage

Timeline

4 updates
15:4716:0216:1816:3416:50
Partial outageUpdate postedTimes in UTC

Investigating

1 h 3 min 100%

Updates

Times in UTC

As posted by GitHub

Investigating

We’ve taken mitigating action to resolve the problem of merge requests timing out. This issue initially impacted 3% of requests and is now down to less than 1%. We continue to monitor recovery.

Investigating

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

Investigating

We’re investigating an issue with Pull Requests where some attempts to merge are timing out.

Investigating

We are investigating reports of degraded availability for Pull Requests

Affected components

1
Pull Requests

GitHub in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

66

Days with an incident

45

Median duration

1 h 15 min

This incident

16% shorter than 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 15 min
90 days agoToday

Other GitHub incidents

All incidents

GitHub·Disruption with Email Delivery

GitHub email delivery did not work for account sign-in, new account sign-up, email address verification, password resets, and email notifications. GitHub reports that the incident is resolved and that it lasted 2 hours and 7 minutes.

Resolved · 1 affected

GitHub·Incident with Webhooks API

GitHub Webhooks API had timeouts and errors that affected about 1% of customer traffic. GitHub mitigated the degradation and monitored stability. The incident is resolved and lasted about 51 minutes.

Resolved

GitHub·Impact across multiple GitHub products including Actions, Pages, and Copilot products.

GitHub reports a major outage that affected Webhooks, Actions, Pages, and Copilot. GitHub later reported recovery across all services and monitored the fix. GitHub marked the incident resolved. The outage lasted 33 minutes.

Resolved

GitHub·Incident with Webhooks

GitHub Webhooks had degraded performance. GitHub reports that the incident is resolved. The outage lasted 4 minutes.

Resolved

GitHub·Incident with Git Operations and Pull Requests

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.

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