outages.live
Live
GitHubIncident ·

Incident with Actions

ResolvedOfficial update
0

GitHub Actions had degraded performance. Some workflow runs had delays or errors when they started. GitHub reports that the incident is resolved and that it lasted 52 minutes.

State

Resolved

Started

Lasted

52 min

Worst impact

Degraded

Timeline

4 updates
16:5017:0317:1617:2917:42
DegradedUpdate postedTimes in UTC

Investigating

16 min 31%

Monitoring

36 min 69%

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.

Monitoring

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

Investigating

Some GitHub Actions workflow runs may experience delays or errors when starting. We’re investigating and preparing a mitigation.

Investigating

We are investigating reports of degraded performance for Actions

Affected components

1
Actions

GitHub in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

54

Days with an incident

38

Median duration

1 h 16 min

This incident

31% 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 16 min
90 days agoToday

Other GitHub incidents

All incidents

GitHub·Incident with Actions

GitHub Actions had degraded availability. The incident affected the Actions component. GitHub reports that the incident is resolved. It lasted 36 minutes.

Resolved

GitHub·Incident with Actions and Pages

GitHub reports degraded performance and availability for Actions, Pages, and Webhooks. GitHub identified the issue, applied mitigations, and monitored recovery. The incident is resolved and lasted about 56 minutes.

Resolved

GitHub·Incident with Pull Requests, Git Operations and Issues

GitHub reports a partial outage that affects Pull Requests, Git Operations, Issues, API Requests, and Actions. GitHub mitigated the degradation and then monitored stability. GitHub states that the incident is resolved. The incident lasted 120 minutes.

Resolved

GitHub·Increased task-related errors for Copilot Mission Control

Copilot Mission Control had increased errors in listing and creating tasks. GitHub reports that the incident is resolved. The incident lasted about 77 minutes.

Resolved · 1 affected

GitHub·Incident with Git Operations

Git Operations had degraded performance. GitHub reported that the incident is resolved. The incident lasted 1 hour and 45 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