You can "Subscribe to updates" at the top of this page, to be alerted if Cliniko is having technical issues. It will also update you with progress, and when the issues are resolved. We recommend doing so!
Cliniko
Operational
90 days ago
100.0
% uptime
Today
AU1 region
Operational
90 days ago
100.0
% uptime
Today
AU2 region
Operational
90 days ago
100.0
% uptime
Today
AU3 region
Operational
90 days ago
100.0
% uptime
Today
AU4 region
Operational
90 days ago
100.0
% uptime
Today
CA1 region
Operational
90 days ago
100.0
% uptime
Today
EU1 region
Operational
90 days ago
100.0
% uptime
Today
UK1 region
Operational
90 days ago
100.0
% uptime
Today
UK2 region
Operational
90 days ago
100.0
% uptime
Today
www.cliniko.com
Operational
Help chat
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Related
No incidents or maintenance related to this downtime.
Resolved -
For a brief time the Cliniko API was returning timestamps in a different format than usual. Instead of our standard format of "2025-05-27T17:44:48Z" we were instead sending "2025-05-27 17:44:48 UTC". The timestamps are still correct, but not in our standard format.
This problem began at 07:15 UTC on 8 Sep 2025 and the core problem was fixed at 07:30 UTC. But we may have continued to send the incorrect format in some places due to caching until 08:40 UTC. This affected all datetime timestamps given by the API.
If you persist data from our API, you may want to check for timestamps in that format and correct them.
Sep 8, 17:00 AEST