Mergify had 9 outages in the last 2 years totaling 24h 11m of downtime — averaging 0.4 incidents per month.
There were 9 Mergify outages since October 20, 2025 totaling 24h 11m of downtime. Each is summarised below — incident details, duration, and resolution information.
Merge Queue using mergify cli to send scopes may have encounter issues
We yanked the mergify cli releases having an issue. The merge queue using scopes should work properly now.
New mergify-cli release fixed the issue.
We are currently experiencing degraded performance affecting pull request processing. This may result in delays in queue handling and slower execution of automated actions. Our team is actively investigating the issue and working on mitigation.
We mitigated the issue and continue to monitor the pull request processing.
The issue has been resolved.
Some users are currently unable to log in to the dashboard. We’re investigating and working on a fix.
The login issue has been resolved.
Some GitHub webhook events are experiencing delayed processing, which may cause delays in pull request evaluations. We are actively investigating the issue.
Webhook delivery is back to normal. Some GitHub events may have been dropped during the incident, if your pull request appears stalled, run a @mergifyio refresh command to re-sync it.
Our data processing infrastructure is running behind which is causing inaccuracies in the reporting.
We've deployed a change to reduce the deliverability issues from GitHub webhooks events. We're monitoring this.
Github event processing is back on track
We identified an issue where the merge queue was posting duplicate status report comments on pull requests. Instead of updating a single status comment per queue session, the system created a new comment on each queue cycle, resulting in a spam of comments on affected PRs. A fix is being deployed. Once applied, duplicate comments will stop. Existing duplicate comments are cosmetic and do not affect merge queue behavior or merging.
Comment duplication has been mitigating, we're still investigating the issue.
The fix has been deployed and the duplicate queue status comments issue is now resolved. Pull requests will no longer receive multiple status report comments per queue cycle.
We're experiencing an elevated level of errors in the Mergify engine and are currently looking into the issue.
We identified the issue, put in place first mitigation and releasing a fix
We released a fix that solved the issue and we are recovering lost github event
We are continuing to recover the lost GitHub events
This incident has been resolved.
Our dashboard, API and documentation may be temporarily inaccessible due to an ongoing Cloudflare outage. More details are available on Cloudflare’s status page: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7
Our dashboard, API and documentation may be temporarily inaccessible due to an ongoing Cloudflare outage. More details are available on Cloudflare’s status page: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7
The incident is now resolved
We've spotted that GitHub does not sent webhook events for pull request approvals for some organization. We contacted GitHub support, we're currently investigating the issue to provide a workaround, we will provide an update soon.
GitHub acknowledges the issue and has reverted the change that introduced the regression. We are monitoring the situation.
This incident has been resolved.