Mergify incident
Duplicate queue status report comments on pull requests
Affected components
Update timeline
- 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.
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
5 free monitors · No credit card required