Resolved · 1d ago · Mon, Aug 17, 1:55 PM UTC (1:55 PM 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.
Mergify is currently operational as of . All monitored components are functioning normally.
How do I check if Mergify is down?▼
You can check Mergify status in real time at netbeep.com/status/mergify. This page monitors the official Mergify status page and shows current component health, active incidents, and uptime history.
What should I do during a Mergify outage?▼
During a Mergify outage, check this page for real-time updates. Review the active incidents section for details on affected components and estimated resolution. You can also visit the official status page at https://status.mergify.com for announcements directly from Mergify.
What is Mergify's current status?▼
Mergify is operational. Visit netbeep.com/status/mergify for real-time updates including component health, active incidents, and uptime history.
How many Mergify components does Netbeep monitor?▼
Mergify has 7 monitored components. 7 are operational.
How often does Mergify go down?▼
Mergify outage frequency varies. Netbeep tracks all incidents reported on the official Mergify status page. Visit this page to see current status, uptime percentages, and incident history.
Notion
Figma
Airtable
Asana
Linear
Dropbox