Skip to main content

Service status

Is it us, or is it your connection?

Six pieces of Clinizy Care, reported one by one — because when a receipt doesn't reach a patient you need to know which piece failed, not an average across all of them. We publish only what we actually measure, and we say so where we measure nothing.

2 of 6 components have an automated check today. The rest say “not monitored” below rather than show a colour we can't stand behind. Publishing since 14 Aug 2026.

This page is served from the same infrastructure as Clinizy Care.

It is a static file served by our web server, so it stays up — and the API check below stays meaningful — when the backend or the database fails. It does not survive the failures that take out the machine, the web server, or DNS. In those cases this page is unreachable too, and a status page that won't load is itself the signal. Hosting status independently of the product is on our list; until it is done, this is what the page can honestly claim.

Component status

Checked when you loaded this page. Refresh to re-check; the page also re-checks itself about once a minute while it is open.

Clinizy Care components, the current state of each, and uptime over the last 90 days
ComponentRight nowUptime (last 90 days)
AppThe web app your team opens — OPD queue, billing, prescriptions, records.ServingYou are reading this page, so the web server that also serves the app answered your request. It does not prove that logging in, or any screen inside the app, works.Not measured
APIThe backend every screen in the app talks to.Checking…Checked live against our health endpoint. That endpoint reports only that the API process is answering — it does not test the database, the message queue, or any individual feature.Not measured
WhatsApp deliveryReceipts, prescriptions and appointment reminders sent to patients on WhatsApp.Not monitoredDelivery depends on Meta's WhatsApp Business API as well as on us. We record the delivery status of individual messages internally, but nothing aggregates them into a figure we could publish here yet.Not measured
PDF generationPrescriptions, invoices, lab reports and discharge summaries rendered as PDFs.Not monitoredNo automated check yet. A failure here shows up as a document that won't open, and the fastest signal is still you telling us.Not measured
PaymentsSubscription checkout and renewals through Cashfree.Not monitoredCashfree publishes its own status and we do not yet mirror it. A failure on our side of checkout would not appear on this row either.Not measured
BackupsScheduled snapshots of your clinic's database, taken by our managed database host.Not monitoredSnapshots are taken by the managed database host, not by a job we monitor. Nothing on this page confirms that last night's snapshot completed.Not measured

No uptime percentage appears above because none has been measured. We have no external monitor watching Clinizy Care from outside our own servers, so there is no 90-day record to report. We started publishing this page on 14 Aug 2026; nothing before that date was measured. We would rather leave the column empty than put a “99.9%” on it that nobody checked.

Live incident updates

While something is broken, every update is posted here with the time we posted it — from the first sighting, through the cause, to the fix.

No incident is open. We have not opened one — which is not the same as an automated system confirming everything is fine. Four of the six components above have no automated check, so an incident there reaches us when a clinic tells us.

Incident history

Every incident we have opened, with how long it lasted, what it affected, and what we changed afterwards.

No incidents recorded. We began publishing incidents on 14 Aug 2026. Read this list as “no record” rather than “no downtime” — we kept no public incident log before that date, and we are not going to reconstruct one from memory.

Scheduled maintenance

Planned work that could interrupt your clinic is announced here at least 72 hours before it starts, so it never lands in the middle of an OPD you didn't plan for.

No maintenance scheduled. Nothing is planned. When something is, it appears here with the exact window, what will be unavailable, and what your clinic should do about it.

Get told instead of checking

Status updates by email

One email when an incident opens, one when it is resolved, and planned-maintenance notices at least 72 hours ahead. Nothing else on this list — no product marketing, unsubscribe in one click.

Something broken that isn't listed?

Four of the six components have no automated check, so for those the fastest signal is still you telling us. Send a message and we will open an incident above if it is us.

Straight answer on the email list: we are collecting addresses now, and until the automated fan-out ships these notices go out by hand. At our size that works, and we would rather tell you than imply a pipeline that doesn't exist yet.