# Degradation with Webhooks, Pull Requests and Actions

- Provider: [GitHub Actions](https://down.guide/providers/github-actions)
- Confidence: Confirmed
- Impact: Partial outage
- lasted 38m
- started 2026-06-25 17:50 UTC
- Webhooks, Issues, Pull Requests +1
- GitHub Actions states the impact was 2026-06-25 17:33 to 17:55 UTC (22m)
- id: DWN-69c23c0e7b
- Official page: https://stspg.io/t882b0gccf1h

## Root cause
> The issue was caused by underlying hypervisor issues and an incoming traffic spike, causing service timeouts which led to a connection storm and continual rebalances.

Category: Capacity. [Postmortem](https://stspg.io/t882b0gccf1h)

## Updates from GitHub Actions
### 2026-06-25 17:50 UTC: investigating
We are investigating reports of degraded performance for Actions, Pull Requests and Webhooks

### 2026-06-25 17:53 UTC: investigating
Actions is experiencing degraded availability. We are continuing to investigate.

### 2026-06-25 17:58 UTC: investigating
Issues is experiencing degraded performance. We are continuing to investigate.

### 2026-06-25 18:07 UTC: monitoring
The degradation affecting Actions, Issues, Pull Requests and Webhooks has been mitigated. We are monitoring to ensure stability.

### 2026-06-25 18:27 UTC: monitoring
We identified an issue that caused degradation across multiple services including Webhooks, Pull Requests, Actions, and Issues. Customers may have experienced delays or failures with these services. We have applied mitigations and affected services have recovered.

### 2026-06-25 18:27 UTC: resolved
On June 25, 2026, between 17:33 UTC and 17:55 UTC, our background job service experienced degradation which increased delays to pull requests, repository pushes, Actions workflows, and Webhooks, with delays peaking at 7m. The issue was caused by underlying hypervisor issues and an incoming traffic spike, causing service timeouts which led to a connection storm and continual rebalances. 
The issue was mitigated by replacing the problem node at 17:49, after which all services saw recovery by 18:07.

From the builder: does your app depend on GitHub Actions? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=github-actions) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention GitHub Actions.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-69c23c0e7b), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.