Cliniko Outage History
14 incidents recorded over the last 365 days, 4 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Cliniko Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 1, 2026 | Australian (AU5) region planned maintenance for Monday, the 2nd of November 2026The scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Nov 1, 2026 | EU & UK (EU1, UK1, UK2, UK3) regions planned maintenance for Sunday the 1st of November 2026The scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Oct 24, 2026 | Canada & US (CA1) region planned maintenance for Saturday the 24th of October 2026The scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Jul 16, 2026 | Cliniko loading issuesAmazon Web Services is reporting initial signs of recovery and continuing to work towards full recovery. Cliniko is now operational again, but please reach out to our support team if you experience ongoing issues. | 3h 0m | Resolved |
| May 18, 2026 | Australian (AU4) region planned maintenance for Tuesday, the 19th of May 2026The scheduled maintenance has been completed. | 4h 0m | Scheduled |
| May 12, 2026 | User sessions ending unexpectedlyThis incident has been resolved. | 6h 24m | Resolved |
| Mar 28, 2026 | Australian (AU1) region planned maintenance for Sunday, the 29th of March 2026The scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Jan 30, 2026 | Loading issues AU1This incident has been resolved. Our team are still investigating the cause and putting in place safe guards to prevent future incidents of the same nature happening again. | 7h 46m | Resolved |
| Jan 24, 2026 | Australian (AU2) region planned maintenance for Sunday, the 25th of January 2026The scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Jan 11, 2026 | UK (UK1, UK2) regions planned maintenance for Sunday, the 11th of January 2026The scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Jan 9, 2026 | Help chat is unavailableThis incident has been resolved. | 1h 42m | Resolved |
| Dec 20, 2025 | Australian (AU3) region planned maintenance for Sunday, the 21st of December 2025The scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Dec 13, 2025 | Australian (AU4) region planned maintenance for Sunday, the 14th of December 2025The scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Dec 7, 2025 | European (EU1) region planned maintenance for Sunday, the 7th of December 2025The scheduled maintenance has been completed. | 2h 0m | Scheduled |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Cliniko incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Cliniko Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Cliniko acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Cliniko outage in this window ran 7h 46m, against a mean recovery of 2h 55m. If you depend on Cliniko in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.