Mergify Outage History

Mergify is up right now

There were 6 Mergify outages since February 26, 2026 totaling 10h 40m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.mergify.com

Minor April 15, 2026

Degraded performance in pull request processing

Detected by Pingoru
Apr 15, 2026, 06:29 PM UTC
Resolved
Apr 15, 2026, 07:37 PM UTC
Duration
1h 8m
Affected: Engine
Timeline · 3 updates
  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

Detected by Pingoru
Mar 30, 2026, 09:33 AM UTC
Resolved
Mar 30, 2026, 10:55 AM UTC
Duration
1h 22m
Affected: Dashboard
Timeline · 2 updates
  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

Detected by Pingoru
Mar 20, 2026, 04:38 PM UTC
Resolved
Mar 20, 2026, 05:44 PM UTC
Duration
1h 5m
Affected: Engine
Timeline · 2 updates
  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

Detected by Pingoru
Mar 06, 2026, 11:02 AM UTC
Resolved
Mar 06, 2026, 12:56 PM UTC
Duration
1h 53m
Affected: Engine
Timeline · 3 updates
  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

Detected by Pingoru
Mar 05, 2026, 11:36 AM UTC
Resolved
Mar 05, 2026, 02:17 PM UTC
Duration
2h 41m
Affected: Engine
Timeline · 3 updates
  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

Detected by Pingoru
Feb 26, 2026, 04:29 PM UTC
Resolved
Feb 26, 2026, 06:58 PM UTC
Duration
2h 29m
Affected: Engine
Timeline · 5 updates
  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 →

Looking to track Mergify downtime and outages?

Pingoru polls Mergify's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Mergify reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Mergify alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Mergify for free

5 free monitors · No credit card required