Live  /  Mergify  /  Incident

Mergify: Merge Queue Processing Delays

Mergify · mergify.comResolved2026-10-19 14:21 UTC
Public — what happened

Summary

Mergify reported a delay in its merge queue processing on 2026-10-19. The company said that between 12:40 and 12:59 UTC its queues did not begin new batches, so pull requests waiting in line did not move forward. Mergify said processing restarted at 12:59 UTC, the waiting pull requests have since been handled, and customers did not need to do anything. It said it had identified the cause and was monitoring for stability, and the incident was later marked resolved at 14:21 UTC.

Affected

Merge Queue

As listed on Mergify’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Mergify against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Mergify: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Mergify report →

More from Mergify

Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.

The full archive is on the Mergify status & history page.

Related: Mergify status & history. SquidGrid is not affiliated with Mergify.