Status

Is Hizke working right now?

Live checks against the running API, admin console and website — not a static graphic. This page is generated fresh on every load.

All systems operational.Checked 26/10/2026, 19:31:51 UTC.

API

Operational

Liveness and readiness checks both passed.

Build: bb18ab1338c3b62e2ec745c83dbac393b7e5de60

Last checked 26/10/2026, 19:31:50 UTC.

Admin console

Operational

The admin console responded to a request.

Last checked 26/10/2026, 19:31:50 UTC.

Website

Operational

Inferred: this page was just rendered by this server. This is not an independent probe.

Last checked 26/10/2026, 19:31:51 UTC.

Parts of the service

The three cards above are what this page can check for itself over the internet. These are the parts the platform declares and keeps up to date by hand, including the ones no check from here could see.

Updated 0 seconds ago.

Each declared part of the Hizke service, its current state, why it is in that state, and when it was last checked.
Part of the service	State	Why	Last checked
Operator console	Unknown	never_observed	Never checked
Booking & dispatch API	Unknown	never_observed	Never checked
Rider & driver apps	Unknown	never_observed	Never checked
Notifications (SMS, email, push)	Unknown	never_observed	Never checked
Payments & payouts	Unknown	never_observed	Never checked
Public website & web booking	Unknown	never_observed	Never checked

Incident history

No incidents are being reported.

This feed is held in the API's memory and does not survive a restart, so an empty list here is not proof that nothing has gone wrong.

Twelve-month uptime

The worst-performing component in each month, never an average across components — an average hides an outage in one part of the platform behind healthy figures from the rest.

Monthly uptime for the last twelve months, with the platform's own statement for each month.
Month	Uptime	What we measured
November 2025	Not measured	Not measured for 43200 minutes; no uptime figure can be given.
December 2025	Not measured	Not measured for 44640 minutes; no uptime figure can be given.
January 2026	Not measured	Not measured for 44640 minutes; no uptime figure can be given.
February 2026	Not measured	Not measured for 40320 minutes; no uptime figure can be given.
March 2026	Not measured	Not measured for 44640 minutes; no uptime figure can be given.
April 2026	Not measured	Not measured for 43200 minutes; no uptime figure can be given.
May 2026	Not measured	Not measured for 44640 minutes; no uptime figure can be given.
June 2026	Not measured	Not measured for 43200 minutes; no uptime figure can be given.
July 2026	Not measured	Not measured for 44640 minutes; no uptime figure can be given.
August 2026	Not measured	Not measured for 44640 minutes; no uptime figure can be given.
September 2026	Not measured	Not measured for 43200 minutes; no uptime figure can be given.
October 2026	Not measured	Not measured for 37171.8643 minutes; no uptime figure can be given.

Uptime target

This is a controlled pilot. We publish a non-binding target of 99.5% monthly availability and operate to a stricter 99.9% internal objective. The pilot has no contractual SLA, no automatic service credits and no fixed restoration-time promise. We may offer a goodwill payment case by case, but that creates no entitlement and no precedent. Nothing on this page is a binding commitment. A paying contract gets a service-level schedule only when one is signed, based on measured history, defined exclusions and agreed remedies. This is owner decision D-058, ratified by D-076.