Looking for an update now? Check the current status, or follow Mergify for future changes.
78.4%of 37 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
80%
30
6
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 2Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
You may see this as Mergify not reacting to activity on your pull requests, so merge queues can stall and rules or checks may not update. The dashboard may fail to load, and API requests, including test result uploads from CI, may return errors.
This causes delays, not incorrect merges: a pull request Mergify has not been able to fully evaluate is held rather than merged. Some activity during these periods may not have reached Mergify.
We have deployed a fix and test metrics processing has resumed.
No data has been lost. Test results recorded throughout the incident were stored normally and will appear once processing catches up.
identified
We identified the issue and are working on a fix to release the congestion point.
investigating
Our data processing infrastructure is running behind which is causing delays while ingesting test metrics. No data has been lost.
The backlog recovered for almost all users. We are still monitoring the situation.
monitoring
The GitHub events automatically recovered.
98% of impacted users already fully recovered. The GitHub events backlog continue to decreased for remaining users.
identified
Our GitHub event processing is running behind for some customers which cause unexpected latency latency in our Workflow Automation and Merge Queue pickup.
Legacy Incident Archive
9 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
August 2026
Merge queue delays caused by a GitHub incident
majorSource not attested
Last archived state: resolved
View archived record details
Engine
identified
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...
July 2026
Merge Queue Processing Delays
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We mitigated the issue, the processing is working again.
investigating
Our merge queue processing is very slow for some customers.
engine processing delays
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Some customers are experiencing some engine processing slowdown. We are investigate the issue.
June 2026
Elevated API Errors
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We're experiencing an elevated level of API errors and are currently looking into the issue.
Unexpected merge queue notifications in Slack
minorSource not attested
Last archived state: resolved
View archived record details
identified
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.
May 2026
Merge Queue Disruption
majorSource not attested
Last archived state: resolved
View archived record details
investigating
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.
Merge Queue using mergify cli to send scopes may have encounter issues
Source not attested
Last archived state: resolved
View archived record details
monitoring
We yanked the mergify cli releases having an issue. The merge queue using scopes should work properly now.
identified
Merge Queue using mergify cli to send scopes may have encounter issues
April 2026
Degraded performance in pull request processing
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We mitigated the issue and continue to monitor the pull request processing.
investigating
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.
March 2026
Dashboard login issue
majorSource not attested
Last archived state: resolved
View archived record details
identified
Some users are currently unable to log in to the dashboard. We’re investigating and working on a fix.
