Is Kadroflow working

Checking …

The check above runs when you load this page. It asks the database to answer a trivial query and asks object storage whether a file exists, and reports whether each answered and how long it took. That is a live reading, not a summary of the past.

There is no uptime percentage on this page, deliberately. Nothing in this system has been measuring availability over time, so any figure printed here would be invented. A number nobody computes is exactly the kind of claim the trust page exists to avoid making. When continuous measurement is in place, a figure will appear here and it will say what measured it.

Incidents are written by a person and published without a deploy. An empty history means none was published; it does not mean none happened.

This page is served by the same Cloudflare Worker as the product. If that Worker is down, this page is down with it and will not tell you anything at all — including that something is wrong.

That is true of every status page hosted on the system it reports on. Saying so is more useful than letting a page that fails to load imply everything is fine. If this page is unreachable and you need to know whether it is us, write to support@kadroflow.com; mail is delivered by a different provider and does not depend on the application being up.

GET /api/status returns the same reading as JSON, unauthenticated, with cross-origin requests allowed, so your own monitoring can poll it. It carries overall, a component list with response times, and any published incidents. It is cached for 30 seconds.

Poll it no more than once a minute. Every request runs live checks against the systems it is reporting on, and a status page should never become the reason for the outage.