Status

Last reviewed: 26 August 2026

All services operating normally as of the review date above. This is a hand-written statement, not a live feed — read the honesty note below before relying on it.

What "the service" comprises

All of it runs on AWS in the Mumbai region behind CloudFront, as described on the security page.

The honest part

This page is not backed by automated monitoring. There is no probe checking the service every minute and flipping this banner on its own — the status above is updated by a person, which means an outage could begin before this page says so. We tell you this because a static "all systems operational" page dressed up as a live one is a small lie, and this site doesn't do those. A real monitoring feed is on the list; when it exists, this page will be driven by it and will say so.

Incidents

If there is an incident that affects customers, it will be posted here with dates and a plain description of what happened, and recorded in the legal changelog. Security incidents additionally follow the notification commitment on the security page: acknowledgement within 48 hours, affected customers notified by email without undue delay.

No incidents recorded to date. (The service launched on 26 August 2026 — an empty incident history one day in is a fact of the calendar, not a track record.)

What we aim for

We build for the cancel flow to be up whenever your customer reaches for it, and we treat any downtime of that flow as the most serious kind. We do not publish an uptime percentage or offer a formal SLA — we have no measured history yet, and quoting a number without one would be invention. Two honest mitigations exist in the product itself: the flow runs on AWS-managed serverless infrastructure with no server of ours to fall over, and if you set a completion URL, your own cancellation page remains the fallback — our Terms explicitly tell you not to make Cancel Desk the only way a customer can cancel.