Mergify had 17 outages in the last 2 years totaling 38h 15m of downtime — averaging 0.7 incidents per month.
There were 17 Mergify outages since September 17, 2024 totaling 38h 15m of downtime. Each is summarised below — incident details, duration, and resolution information.
Our merge queue processing is very slow for some customers.
We mitigated the issue, the processing is working again.
This incident has been resolved.
Some customers are experiencing some engine processing slowdown. We are investigate the issue.
The issue was impacted only a couple of customers and has been mitigated.
We're experiencing an elevated level of API errors and are currently looking into the issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
Earlier today, some users experienced intermittent API errors and delays in merge queue processing. The cause was a database performance issue on our engine. We identified it, applied a fix, and the service is now fully operational. Thanks for your patience, and sorry for the disruption.
An issue is causing some Slack channels connected to Mergify to receive unexpected merge queue notifications, starting today at 13:14 UTC. Only notification delivery is affected — merge queues, pull request processing, and your data are operating normally. We have identified the cause and a fix is in progress and is being rolled out. We will post another update once the fix is fully deployed. We apologize for the noise in your channels.
This issue is now resolved.
We are currently experiencing a disruption affecting merge queue operations. On our side, we are observing a surge of 404 Branch not found responses from GitHub APIs, which is impacting branch processing and merge queue execution. We are actively investigating the issue and monitoring GitHub API behavior closely. We will provide updates as more information becomes available.
The incident affecting merge queue operations has been resolved. The issue was caused by a transient surge of 404 Branch not found responses returned by GitHub APIs, which temporarily impacted branch processing and merge queue execution. The errors have subsided and merge queue operations are now functioning normally. We continue to monitor the situation closely.
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.
We've spotted an issue with our dashboard and our events processing. We're currently investigating the issue, and will provide an update soon.
We are continuing to investigate this issue.
We are currently experiencing an incident that is affecting the availability/performance of our services. The issue has been traced to a broader incident on our cloud hosting provider’s network, which is impacting multiple services. We are working on a workaround. We actively monitor the situation and will provide updates as we receive more information from our provider or when our workaround is ready. Thank you for your patience.
Our cloud provider has resolved the underlying network issue. As a result: * Our dashboard is now fully operational. * Our processing engine is recovering and working through its backlog. We are continuing to monitor the situation and will post a final update once full recovery is confirmed. Thank you for your understanding.
We are continuing to monitor for any further issues.
This incident has been resolved.
We identified an issue in event processing, adding delay and latency to Mergify operations.
We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
Our pull requests processing is slower than usual. We are working on solving the issue.
We found the root cause of the slowdown and fixed it. The pull request processing latency is decreasing. It should be back to normal very soon.
This incident has been resolved.