Live  /  Mergify  /  Incident

Mergify: Delayed processing of GitHub events for some organizations

Mergify · mergify.comMinor incidentResolved2026-11-12 17:57 UTC
Public — what happened

Summary

Mergify said that a small number of organizations were seeing delays in how their GitHub events were handled, which it listed as a minor issue. The company reported that the lateness had been going on since 14:00 UTC, and it posted its first update at 16:34 UTC on 12 November 2026 saying it was investigating. Its status page shows the incident as resolved at 17:57 UTC, though the text provided does not state a cause.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Mergify against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Mergify: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Mergify report →

More from Mergify

Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.

The full archive is on the Mergify status & history page.

Related: Mergify status & history. SquidGrid is not affiliated with Mergify.