Appearance
Service Level Agreement & Incident Handling
Effective 4 October 2026.
No beta SLA
The public beta has no committed uptime, response time, resolution time or service credit.
No quantified beta SLA
EasyMerge will open as a free public beta in 2026. For the beta, we do not commit to an uptime percentage, response or resolution time, service credit, or fixed support window. A review status, pricing page or guide does not create an implied commitment.
If a paid plan later includes an SLA, it must be published or agreed in writing before it applies. This page does not replace an individual customer agreement.
Review and service status
The dashboard can show a review as Queued, Preparing…, Reviewing…, Completed, Failed or Cancelled. A failed review does not necessarily mean that your repository has a problem; it can result from a limit or temporary dependency failure. See Review lifecycle and Troubleshooting for each state and the available next steps.
The public status page at status.easymerge.dev shows whether EasyMerge is working before you open a ticket. It covers three parts of the service: GitHub connection, PR review processing and the EasyMerge dashboard. Each shows its current status (Operational, Degraded performance, Partial outage or Major outage) and a 30-day availability bar.
Active incidents appear below, with their updates, followed by past incidents from the last 30 days; View history goes back one year. The page is a snapshot taken when you open it, so reload it for the latest status.
It reports the platform as a whole, not one pull request. For your own review, the dashboard and the pull request's check run remain the most accurate source.
Reporting an incident
Check the status page first. Then create a Technical ticket in Help & Support, or choose Report a problem on a review or repository to prefill its context. Include the pull-request or review URL, when it occurred, the displayed status and the impact. The support guide explains attachment limits and content you should not send.
Do not include passwords, access tokens, secrets or exploit payloads in a ticket. Security incidents must follow the vulnerability disclosure process.
How we handle incidents
When enough information is available to investigate, we assess impact, prioritise safe restoration of service and update the ticket when we can. Investigation can include review state, operational logs and relevant dependencies; we do not need your entire repository or secrets to begin.
During an interruption, an in-progress review can fail or be cancelled. Use retry or Scan again where the interface offers it, and do not assume that partial results have been posted inline on GitHub. For updates about a particular installation, follow its support ticket.