Mergify incident

Merge queue delays caused by a GitHub incident

Major Resolved View vendor source →

Mergify experienced a major incident on August 17, 2026 affecting Engine, lasting 16h 30m. The incident has been resolved; the full update timeline is below.

Started
Aug 17, 2026, 01:55 PM UTC
Resolved
Aug 18, 2026, 06:25 AM UTC
Duration
16h 30m
Detected by Pingoru
Aug 17, 2026, 01:55 PM UTC

Affected components

Engine

Update timeline

  1. identified Aug 17, 2026, 01:55 PM UTC

    GitHub is currently experiencing degraded service on its API and webhook delivery. Their incident is public and you can follow it at https://www.githubstatus.com. This is slowing merge queue processing across Mergify. Since around 13:30 UTC, pull requests are taking longer than usual to be evaluated and merged, and some events from GitHub are reaching us with delay. Your pull requests stay in the queue. There is no need to re-queue them or to change your configuration. Processing catches up as GitHub recovers. We are monitoring and will update this page when the situation changes.

  2. resolved Aug 18, 2026, 06:25 AM UTC

    GitHub's incident is resolved and Mergify is back to normal. Merge queue processing returned to its usual rate. Pull requests queued during the incident were processed as GitHub recovered, and no action is needed on your side.