Is Mergify down?

Last checked 8m ago
Current status
Mergify is up

No incidents right now.

Official status page: https://status.mergify.com · Polled every 5 minutes · 7 components tracked

Mergify is operational right now. Last checked 8m ago; the most recent incident resolved 15d ago.

Real-time Mergify status, recent outages, and incident history — pulled directly from Mergify's official status page at https://status.mergify.com every 5 minutes. Pingoru tracks 7 Mergify services and has captured 6 incidents in the last 90 days (98.97% uptime). Get email, Slack, Discord, or webhook alerts the moment Mergify reports a new incident — free for 5 monitors, no credit card.

Users who monitor Mergify also follow these DevOps services: GitHub Confluence Circle CI OpsGenie JFrog Papertrail Airbrake Splunk OnCall Datadog EU RubyGems View all 6,000+ providers
Mergify uptime 98.97% uptime · past 90 days
Mon Wed Fri
AprMayJunJul
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 47m
    Started Jul 14, 2026, 12:05 PM UTC · Resolved Jul 14, 2026, 12:52 PM UTC
    Engine
    Timeline · 3 updates
    • investigating · Jul 14, 2026, 12:05 PM UTC

      Our merge queue processing is very slow for some customers.

    • monitoring · Jul 14, 2026, 12:40 PM UTC

      We mitigated the issue, the processing is working again.

    • resolved · Jul 14, 2026, 12:52 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 1h 15m
    Started Jul 08, 2026, 04:38 PM UTC · Resolved Jul 08, 2026, 05:54 PM UTC
    Engine
    Timeline · 2 updates
    • investigating · Jul 08, 2026, 04:38 PM UTC

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

    • resolved · Jul 08, 2026, 05:54 PM UTC

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

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

  3. Resolved 58m
    Started Jun 18, 2026, 08:50 AM UTC · Resolved Jun 18, 2026, 09:49 AM UTC
    EngineAPI
    Timeline · 4 updates
    • investigating · Jun 18, 2026, 08:50 AM UTC

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

    • identified · Jun 18, 2026, 09:22 AM UTC

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

    • monitoring · Jun 18, 2026, 09:30 AM UTC

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

    • 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.

    Latest: 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, appl…

  4. Resolved 19m
    Started Jun 11, 2026, 01:46 PM UTC · Resolved Jun 11, 2026, 02:06 PM UTC
    Timeline · 2 updates
    • 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.

    • resolved · Jun 11, 2026, 02:06 PM UTC

      This issue is now resolved.

    Latest: This issue is now resolved.

  5. Resolved 8m
    Started May 28, 2026, 01:36 PM UTC · Resolved May 28, 2026, 01:44 PM UTC
    GitHub API Requests (githubstatus.com)
    Timeline · 2 updates
    • 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.

    • 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.

    Latest: 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 temporar…

See the full Mergify outage history

1 more incident in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Mergify outage history →

Or sign up free to get alerts when Mergify breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 6 incidents View full outage history →