- Detected by Pingoru
- Sep 16, 2026, 04:31 PM UTC
- Resolved
- Sep 16, 2026, 05:42 PM UTC
- Duration
- 1h 10m
Affected: 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.
Read the full incident report →
- Detected by Pingoru
- Sep 15, 2026, 01:33 PM UTC
- Resolved
- Sep 15, 2026, 05:07 PM UTC
- Duration
- 3h 33m
Affected: 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.
Read the full incident report →
- Detected by Pingoru
- Sep 04, 2026, 09:10 AM UTC
- Resolved
- Sep 04, 2026, 11:21 AM UTC
- Duration
- 2h 10m
Affected: 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.
Read the full incident report →
- Detected by Pingoru
- Sep 02, 2026, 06:12 PM UTC
- Resolved
- Sep 02, 2026, 09:20 PM UTC
- Duration
- 3h 7m
Affected: 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
Read the full incident report →
- Detected by Pingoru
- Aug 17, 2026, 01:55 PM UTC
- Resolved
- Aug 18, 2026, 06:25 AM UTC
- Duration
- 16h 30m
Affected: 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.
Read the full incident report →
- Detected by Pingoru
- Jul 14, 2026, 12:05 PM UTC
- Resolved
- Jul 14, 2026, 12:52 PM UTC
- Duration
- 47m
Affected: GitHub Events Processing
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.
Read the full incident report →
- Detected by Pingoru
- Jul 08, 2026, 04:38 PM UTC
- Resolved
- Jul 08, 2026, 05:54 PM UTC
- Duration
- 1h 15m
Affected: GitHub Events Processing
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.
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2026, 08:50 AM UTC
- Resolved
- Jun 18, 2026, 09:49 AM UTC
- Duration
- 58m
Affected: GitHub Events ProcessingAPI
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.
Read the full incident report →
- Detected by Pingoru
- Jun 11, 2026, 01:46 PM UTC
- Resolved
- Jun 11, 2026, 02:06 PM UTC
- Duration
- 19m
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.
Read the full incident report →
- Detected by Pingoru
- May 28, 2026, 01:36 PM UTC
- Resolved
- May 28, 2026, 01:44 PM UTC
- Duration
- 8m
Affected: 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.
Read the full incident report →
- Detected by Pingoru
- May 05, 2026, 11:11 AM UTC
- Resolved
- May 05, 2026, 01:07 PM UTC
- Duration
- 1h 56m
Timeline · 3 updates
-
identified May 05, 2026, 11:11 AM UTC
Merge Queue using mergify cli to send scopes may have encounter issues
-
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.
-
resolved May 05, 2026, 01:07 PM UTC
New mergify-cli release fixed the issue.
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2026, 06:29 PM UTC
- Resolved
- Apr 15, 2026, 07:37 PM UTC
- Duration
- 1h 8m
Affected: GitHub Events Processing
Timeline · 3 updates
-
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.
-
monitoring Apr 15, 2026, 06:53 PM UTC
We mitigated the issue and continue to monitor the pull request processing.
-
resolved Apr 15, 2026, 07:37 PM UTC
The issue has been resolved.
Read the full incident report →
- 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
-
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.
-
resolved Mar 30, 2026, 10:55 AM UTC
The login issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 20, 2026, 04:38 PM UTC
- Resolved
- Mar 20, 2026, 05:44 PM UTC
- Duration
- 1h 5m
Affected: GitHub Events Processing
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Mar 06, 2026, 11:02 AM UTC
- Resolved
- Mar 06, 2026, 12:56 PM UTC
- Duration
- 1h 53m
Affected: GitHub Events Processing
Timeline · 3 updates
-
investigating Mar 06, 2026, 11:02 AM UTC
Our data processing infrastructure is running behind which is causing inaccuracies in the reporting.
-
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.
-
resolved Mar 06, 2026, 12:56 PM UTC
Github event processing is back on track
Read the full incident report →
- Detected by Pingoru
- Mar 05, 2026, 11:36 AM UTC
- Resolved
- Mar 05, 2026, 02:17 PM UTC
- Duration
- 2h 41m
Affected: GitHub Events Processing
Timeline · 3 updates
-
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.
-
monitoring Mar 05, 2026, 12:42 PM UTC
Comment duplication has been mitigating, we're still investigating the issue.
-
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 →
- Detected by Pingoru
- Feb 26, 2026, 04:29 PM UTC
- Resolved
- Feb 26, 2026, 06:58 PM UTC
- Duration
- 2h 29m
Affected: GitHub Events Processing
Timeline · 5 updates
-
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.
-
identified Feb 26, 2026, 05:32 PM UTC
We identified the issue, put in place first mitigation and releasing a fix
-
monitoring Feb 26, 2026, 05:57 PM UTC
We released a fix that solved the issue and we are recovering lost github event
-
monitoring Feb 26, 2026, 06:47 PM UTC
We are continuing to recover the lost GitHub events
-
resolved Feb 26, 2026, 06:58 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 12:09 PM UTC
- Resolved
- Nov 18, 2025, 02:53 PM UTC
- Duration
- 2h 43m
Affected: DashboardAPIDocumentation
Timeline · 3 updates
-
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
-
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
-
resolved Nov 18, 2025, 02:53 PM UTC
The incident is now resolved
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 08:31 AM UTC
- Resolved
- Oct 20, 2025, 05:22 PM UTC
- Duration
- 8h 50m
Affected: GitHub Events Processing
Timeline · 3 updates
-
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.
-
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.
-
resolved Oct 20, 2025, 05:22 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 16, 2025, 06:43 AM UTC
- Resolved
- May 16, 2025, 02:34 PM UTC
- Duration
- 7h 51m
Affected: DashboardGitHub Events Processing
Timeline · 6 updates
-
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.
-
investigating May 16, 2025, 07:08 AM UTC
We are continuing to investigate this issue.
-
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.
-
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.
-
monitoring May 16, 2025, 12:06 PM UTC
We are continuing to monitor for any further issues.
-
resolved May 16, 2025, 02:34 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 10, 2025, 12:05 PM UTC
- Resolved
- Jan 10, 2025, 01:40 PM UTC
- Duration
- 1h 35m
Affected: GitHub Events Processing
Timeline · 3 updates
-
identified Jan 10, 2025, 12:05 PM UTC
We identified an issue in event processing, adding delay and latency to Mergify operations.
-
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.
-
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 →
- Detected by Pingoru
- Dec 19, 2024, 03:46 PM UTC
- Resolved
- Dec 19, 2024, 04:53 PM UTC
- Duration
- 1h 7m
Affected: GitHub Events Processing
Timeline · 3 updates
-
identified Dec 19, 2024, 03:46 PM UTC
Our pull requests processing is slower than usual. We are working on solving the issue.
-
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.
-
resolved Dec 19, 2024, 04:53 PM UTC
This incident has been resolved.
Read the full incident report →
