GitHub Events Processing
Last updateresolvedSep 4 · 11:21 UTC
Long-term fix has been deployed and is working as expected. All systems are operational.
Reported by Mergify on their status page.
checked Sep 7, 2026 8:22 AM UTC · Mergify's official status page
Mergify is up and running.
Mergify is currently operational with all systems functioning normally.
All components operational
Email only. No password. No card.
Be the first to know
Statusfield watches Mergify alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
Email only. No password. Free.
Mergify incident history
3 reports published by Mergify in the last 30 days
When Mergify breaks, it is typically resolved in 1h 17m — median across 7 resolved incidents over 90 days.
September 4, 2026
September 2, 2026
GitHub events processing
Last updateresolvedSep 2 · 21:20 UTC
The GitHub events backlog have fully recovered
Reported by Mergify on their status page.
August 18, 2026
Merge queue delays caused by a GitHub incident
Last updateresolvedAug 18 · 06:25 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.
Reported by Mergify on their status page.