Mergify Outage History

Mergify is up right now

Pingoru has recorded 51 incidents for Mergify: 19 in the last 12 months and 6 in the last 90 days.

Source: status.mergify.com

51incidents recorded
19last 12 months
6last 90 days
2 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Mergify in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202611 of 720 (0%)
May 202622 of 744 (0%)
June 202621 of 720 (0%)
July 202622 of 744 (0%)
August 2026117 of 744 (2%)
September 2026410 of 720 (1%)
October 202611 of 525 (0%)

Incidents, newest first

Notice October 19, 2026 Merge Queue Processing Delays 1h 6m Merge Queue

Started Oct 19, 2026, 01:15 PM UTC· resolved Oct 19, 2026, 02:21 PM UTC

  1. monitoring Oct 19, 2026, 01:15 PM UTC

    Between 12:40 and 12:59 UTC, merge queues stopped starting new batches, so pull requests waiting in the queue did not progress. Processing resumed at 12:59 UTC, and the pull requests that were waiting have since been processed. No action is needed on your side: pull requests queued during that window continued on their own. We have identified the cause and are monitoring to confirm everything stays stable.

  2. resolved Oct 19, 2026, 02:21 PM UTC

    This incident is resolved. We have since deployed a fix so the queue recovers from this kind of interruption on its own.

Read the full incident report →

Minor September 16, 2026 Delayed pull request processing 1h 10m GitHub Events Processing, Merge Queue

Started Sep 16, 2026, 04:31 PM UTC· resolved Sep 16, 2026, 05:42 PM UTC

  1. investigating Sep 16, 2026, 04:31 PM UTC

    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.

  2. resolved Sep 16, 2026, 05:42 PM UTC

    Issue is mitigated. If a pull request still looks stuck, comment "@mergifyio refresh" on it.

Read the full incident report →

Minor September 15, 2026 Test Metrics Ingestion 3h 33m GitHub Events Processing

Started Sep 15, 2026, 01:33 PM UTC· resolved Sep 15, 2026, 05:07 PM UTC

  1. investigating Sep 15, 2026, 01:33 PM UTC

    Our data processing infrastructure is running behind which is causing delays while ingesting test metrics. No data has been lost.

  2. identified Sep 15, 2026, 01:59 PM UTC

    We identified the issue and are working on a fix to release the congestion point.

  3. monitoring Sep 15, 2026, 04:06 PM UTC

    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.

  4. resolved Sep 15, 2026, 05:07 PM UTC

    The issue has been fixed.

Read the full incident report →

Notice September 4, 2026 GitHub Events Processing 2h 10m GitHub Events Processing

Started Sep 04, 2026, 09:10 AM UTC· resolved Sep 04, 2026, 11:21 AM UTC

  1. identified Sep 04, 2026, 09:10 AM UTC

    Our GitHub event processing is running behind for some customers which cause unexpected latency latency in our Workflow Automation and Merge Queue pickup.

  2. monitoring Sep 04, 2026, 09:30 AM UTC

    The backlog recovered for almost all users. We are still monitoring the situation.

  3. monitoring Sep 04, 2026, 10:03 AM UTC

    The backlog recovered for all users. We are still monitoring the situation.

  4. resolved Sep 04, 2026, 11:21 AM UTC

    Long-term fix has been deployed and is working as expected. All systems are operational.

Read the full incident report →

Major September 2, 2026 GitHub events processing 3h 7m GitHub Events Processing

Started Sep 02, 2026, 06:12 PM UTC· resolved Sep 02, 2026, 09:20 PM UTC

  1. identified Sep 02, 2026, 06:12 PM UTC

    Our GitHub event processing is running behind for some customers which cause unexpected latency latency in our Workflow Automation and Merge Queue pickup.

  2. monitoring Sep 02, 2026, 07:21 PM UTC

    The GitHub events automatically recovered. 98% of impacted users already fully recovered. The GitHub events backlog continue to decreased for remaining users.

  3. monitoring Sep 02, 2026, 08:34 PM UTC

    The backlog recovered for almost all users. We are still monitoring the situation.

  4. resolved Sep 02, 2026, 09:20 PM UTC

    The GitHub events backlog have fully recovered

Read the full incident report →

Major August 17, 2026 Merge queue delays caused by a GitHub incident 16h 30m GitHub Events Processing

Started Aug 17, 2026, 01:55 PM UTC· resolved Aug 18, 2026, 06:25 AM UTC

  1. identified Aug 17, 2026, 01:55 PM UTC

    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 as GitHub recovers. We are monitoring and will update this page when the situation changes.

  2. resolved Aug 18, 2026, 06:25 AM UTC

    GitHub's incident is resolved and Mergify is back to normal. Merge queue processing returned to its usual rate. Pull requests queued during the incident were processed as GitHub recovered, and no action is needed on your side.

Read the full incident report →

Notice July 8, 2026 engine processing delays 1h 15m GitHub Events Processing

Started Jul 08, 2026, 04:38 PM UTC· resolved Jul 08, 2026, 05:54 PM UTC

  1. investigating Jul 08, 2026, 04:38 PM UTC

    Some customers are experiencing some engine processing slowdown. We are investigate the issue.

  2. resolved Jul 08, 2026, 05:54 PM UTC

    The issue was impacted only a couple of customers and has been mitigated.

Read the full incident report →

Major June 18, 2026 Elevated API Errors 58m GitHub Events Processing, API

Started Jun 18, 2026, 08:50 AM UTC· resolved Jun 18, 2026, 09:49 AM UTC

  1. investigating Jun 18, 2026, 08:50 AM UTC

    We're experiencing an elevated level of API errors and are currently looking into the issue.

  2. identified Jun 18, 2026, 09:22 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jun 18, 2026, 09:30 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jun 18, 2026, 09:49 AM UTC

    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.

Read the full incident report →

Minor June 11, 2026 Unexpected merge queue notifications in Slack 19m

Started Jun 11, 2026, 01:46 PM UTC· resolved Jun 11, 2026, 02:06 PM UTC

  1. identified Jun 11, 2026, 01:46 PM UTC

    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.

  2. resolved Jun 11, 2026, 02:06 PM UTC

    This issue is now resolved.

Read the full incident report →

Major May 28, 2026 Merge Queue Disruption 8m GitHub API Requests (githubstatus.com)

Started May 28, 2026, 01:36 PM UTC· resolved May 28, 2026, 01:44 PM UTC

  1. investigating May 28, 2026, 01:36 PM UTC

    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.

  2. resolved May 28, 2026, 01:44 PM UTC

    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.

Read the full incident report →

Notice May 5, 2026 Merge Queue using mergify cli to send scopes may have encounter issues 1h 56m

Started May 05, 2026, 11:11 AM UTC· resolved May 05, 2026, 01:07 PM UTC

  1. identified May 05, 2026, 11:11 AM UTC

    Merge Queue using mergify cli to send scopes may have encounter issues

  2. monitoring May 05, 2026, 11:45 AM UTC

    We yanked the mergify cli releases having an issue. The merge queue using scopes should work properly now.

  3. resolved May 05, 2026, 01:07 PM UTC

    New mergify-cli release fixed the issue.

Read the full incident report →

Minor April 15, 2026 Degraded performance in pull request processing 1h 8m GitHub Events Processing

Started Apr 15, 2026, 06:29 PM UTC· resolved Apr 15, 2026, 07:37 PM UTC

  1. investigating Apr 15, 2026, 06:29 PM UTC

    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.

  2. monitoring Apr 15, 2026, 06:53 PM UTC

    We mitigated the issue and continue to monitor the pull request processing.

  3. resolved Apr 15, 2026, 07:37 PM UTC

    The issue has been resolved.

Read the full incident report →

Minor March 30, 2026 Dashboard login issue 1h 22m Dashboard

Started Mar 30, 2026, 09:33 AM UTC· resolved Mar 30, 2026, 10:55 AM UTC

  1. identified Mar 30, 2026, 09:33 AM UTC

    Some users are currently unable to log in to the dashboard. We’re investigating and working on a fix.

  2. resolved Mar 30, 2026, 10:55 AM UTC

    The login issue has been resolved.

Read the full incident report →

Minor March 20, 2026 Processing of GitHub events is delayed 1h 5m GitHub Events Processing

Started Mar 20, 2026, 04:38 PM UTC· resolved Mar 20, 2026, 05:44 PM UTC

  1. investigating Mar 20, 2026, 04:38 PM UTC

    Some GitHub webhook events are experiencing delayed processing, which may cause delays in pull request evaluations. We are actively investigating the issue.

  2. resolved Mar 20, 2026, 05:44 PM UTC

    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.

Read the full incident report →

Major March 6, 2026 Data Processing Delays 1h 53m GitHub Events Processing

Started Mar 06, 2026, 11:02 AM UTC· resolved Mar 06, 2026, 12:56 PM UTC

  1. investigating Mar 06, 2026, 11:02 AM UTC

    Our data processing infrastructure is running behind which is causing inaccuracies in the reporting.

  2. monitoring Mar 06, 2026, 12:30 PM UTC

    We've deployed a change to reduce the deliverability issues from GitHub webhooks events. We're monitoring this.

  3. resolved Mar 06, 2026, 12:56 PM UTC

    Github event processing is back on track

Read the full incident report →

Minor March 5, 2026 Duplicate queue status report comments on pull requests 2h 41m GitHub Events Processing

Started Mar 05, 2026, 11:36 AM UTC· resolved Mar 05, 2026, 02:17 PM UTC

  1. identified Mar 05, 2026, 11:36 AM UTC

    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.

  2. monitoring Mar 05, 2026, 12:42 PM UTC

    Comment duplication has been mitigating, we're still investigating the issue.

  3. resolved Mar 05, 2026, 02:17 PM UTC

    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.

Read the full incident report →

Major February 26, 2026 Engine outage 2h 29m GitHub Events Processing

Started Feb 26, 2026, 04:29 PM UTC· resolved Feb 26, 2026, 06:58 PM UTC

  1. investigating Feb 26, 2026, 04:29 PM UTC

    We're experiencing an elevated level of errors in the Mergify engine and are currently looking into the issue.

  2. identified Feb 26, 2026, 05:32 PM UTC

    We identified the issue, put in place first mitigation and releasing a fix

  3. monitoring Feb 26, 2026, 05:57 PM UTC

    We released a fix that solved the issue and we are recovering lost github event

  4. monitoring Feb 26, 2026, 06:47 PM UTC

    We are continuing to recover the lost GitHub events

  5. resolved Feb 26, 2026, 06:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 18, 2025 Cloudflare Upstream Outage Impacting Dashboard, Documentation and API 2h 43m Dashboard, API, Documentation

Started Nov 18, 2025, 12:09 PM UTC· resolved Nov 18, 2025, 02:53 PM UTC

  1. investigating Nov 18, 2025, 12:09 PM UTC

    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

  2. investigating Nov 18, 2025, 12:47 PM UTC

    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

  3. resolved Nov 18, 2025, 02:53 PM UTC

    The incident is now resolved

Read the full incident report →

Major October 20, 2025 Missing pull requests approvals 8h 50m GitHub Events Processing

Started Oct 20, 2025, 08:31 AM UTC· resolved Oct 20, 2025, 05:22 PM UTC

  1. investigating Oct 20, 2025, 08:31 AM UTC

    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.

  2. monitoring Oct 20, 2025, 02:44 PM UTC

    GitHub acknowledges the issue and has reverted the change that introduced the regression. We are monitoring the situation.

  3. resolved Oct 20, 2025, 05:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 16, 2025 Incident on Dashboard and Engine 7h 51m Dashboard, GitHub Events Processing

Started May 16, 2025, 06:43 AM UTC· resolved May 16, 2025, 02:34 PM UTC

  1. investigating May 16, 2025, 06:43 AM UTC

    We've spotted an issue with our dashboard and our events processing. We're currently investigating the issue, and will provide an update soon.

  2. investigating May 16, 2025, 07:08 AM UTC

    We are continuing to investigate this issue.

  3. investigating May 16, 2025, 07:36 AM UTC

    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.

  4. monitoring May 16, 2025, 09:38 AM UTC

    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.

  5. monitoring May 16, 2025, 12:06 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved May 16, 2025, 02:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 10, 2025 Event processing delay 1h 35m GitHub Events Processing

Started Jan 10, 2025, 12:05 PM UTC· resolved Jan 10, 2025, 01:40 PM UTC

  1. identified Jan 10, 2025, 12:05 PM UTC

    We identified an issue in event processing, adding delay and latency to Mergify operations.

  2. monitoring Jan 10, 2025, 12:26 PM UTC

    We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

  3. resolved Jan 10, 2025, 01:40 PM UTC

    We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

Read the full incident report →

Major December 19, 2024 Pull request Processing Delays 1h 7m GitHub Events Processing

Started Dec 19, 2024, 03:46 PM UTC· resolved Dec 19, 2024, 04:53 PM UTC

  1. identified Dec 19, 2024, 03:46 PM UTC

    Our pull requests processing is slower than usual. We are working on solving the issue.

  2. monitoring Dec 19, 2024, 04:00 PM UTC

    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.

  3. resolved Dec 19, 2024, 04:53 PM UTC

    This incident has been resolved.

Read the full incident report →