Is Mergify down?
Last checked 1m agoNo incidents right now.
Mergify is operational right now. Last checked 1m ago; the most recent incident resolved 13h 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 10 Mergify services and has captured 7 incidents in the last 90 days (99.05% uptime). Get email, Slack, Discord, or webhook alerts the moment Mergify reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- GitHub Events ProcessingMerge Queue
Timeline · 2 updates
- 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.
- resolved · Sep 16, 2026, 05:42 PM UTC
Issue is mitigated. If a pull request still looks stuck, comment "@mergifyio refresh" on it.
Latest: Issue is mitigated. If a pull request still looks stuck, comment "@mergifyio refresh" on it.
-
- GitHub Events Processing
Timeline · 4 updates
- 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.
- identified · Sep 15, 2026, 01:59 PM UTC
We identified the issue and are working on a fix to release the congestion point.
- 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.
- resolved · Sep 15, 2026, 05:07 PM UTC
The issue has been fixed.
Latest: The issue has been fixed.
-
- GitHub Events Processing
Timeline · 4 updates
- 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.
- monitoring · Sep 04, 2026, 09:30 AM UTC
The backlog recovered for almost all users. We are still monitoring the situation.
- monitoring · Sep 04, 2026, 10:03 AM UTC
The backlog recovered for all users. We are still monitoring the situation.
- resolved · Sep 04, 2026, 11:21 AM UTC
Long-term fix has been deployed and is working as expected. All systems are operational.
Latest: Long-term fix has been deployed and is working as expected. All systems are operational.
-
- GitHub Events Processing
Timeline · 4 updates
- 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.
- 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.
- monitoring · Sep 02, 2026, 08:34 PM UTC
The backlog recovered for almost all users. We are still monitoring the situation.
- resolved · Sep 02, 2026, 09:20 PM UTC
The GitHub events backlog have fully recovered
Latest: The GitHub events backlog have fully recovered
-
- GitHub Events Processing
Timeline · 2 updates
- 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.
- 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.
Latest: 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 re…
-
See the full Mergify outage history
2 more incidents 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
- Delayed pull request processing ResolvedStarted Sep 16, 2026, 04:31 PM UTC · Resolved Sep 16, 2026, 05:42 PM UTC · 1h 10m
- Test Metrics Ingestion ResolvedStarted Sep 15, 2026, 01:33 PM UTC · Resolved Sep 15, 2026, 05:07 PM UTC · 3h 33m
- GitHub Events Processing ResolvedStarted Sep 04, 2026, 09:10 AM UTC · Resolved Sep 04, 2026, 11:21 AM UTC · 2h 10m
- GitHub events processing ResolvedStarted Sep 02, 2026, 06:12 PM UTC · Resolved Sep 02, 2026, 09:20 PM UTC · 3h 7m
- Started Aug 17, 2026, 01:55 PM UTC · Resolved Aug 18, 2026, 06:25 AM UTC · 16h 30m
- Merge Queue Processing Delays ResolvedStarted Jul 14, 2026, 12:05 PM UTC · Resolved Jul 14, 2026, 12:52 PM UTC · 47m
- engine processing delays ResolvedStarted Jul 08, 2026, 04:38 PM UTC · Resolved Jul 08, 2026, 05:54 PM UTC · 1h 15m