Live / Mergify / Incident
Mergify: Delayed pull request processing
Mergify · mergify.comMinor incidentResolved2026-09-16 16:31 UTC
Public — what happened
Summary
Mergify reported a minor incident beginning at 16:31 UTC on 2026-09-16 in which its service was slow to process pull requests. According to the company, users might notice Mergify failing to respond to pull request activity, merge queues stalling, rules or checks not refreshing, the dashboard not loading, and API calls such as CI test result uploads returning errors. Mergify said the problem led to delays rather than wrong merges, since pull requests it could not fully evaluate were held back, though it noted some activity during this time may not have reached it. No cause was given, and while the status was still listed as investigating, the incident was recorded as resolved at 17:52.
Timeline
- Started — 2026-09-16 16:31 UTC
- Resolved — 2026-09-16 17:52 UTC · 1h 21m after it started
With SquidGrid — where it starts on the route
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 seeCustomers 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 39, 2026, our weekly internet health report.