Skip to content
MGT Alcor
Status

We do not publish an automated status feed yet.

This page exists at the address it will always be at, and it is honest about what sits behind it: there is no external monitoring, no incident history and no automated component check on this platform today. Rather than show green ticks that nothing verifies, it tells you that.

During an incident

What to do if something is not working

  1. If an examination is in progress, tell your invigilator first. They can see the sitting and can act on it in a way a support inbox cannot. Answers are saved as they are given, so a disconnection does not lose work already entered.
  2. Check whether it is only you. A candidate's own connection, a campus network or a browser extension accounts for most of what reaches us as an outage. Trying a different network is thirty seconds and resolves it often.
  3. Tell us. Write to grievances@macliysglobal.tech with the time, the institution and what you were doing. We acknowledge within 24 hours — the published route and its timelines are on the grievance page.
What we do commit to

Three things that are true without a status feed

Nothing ends a live exam

Not maintenance mode, not a restore, not a tenant suspension, not a deploy. Each of those checks for attempts in progress and exempts or refuses. Only a proctor can end one sitting, deliberately.

Backups run nightly

The database is dumped on a schedule and verified by checksum before any restore. Files on disk are not covered — see security and compliance, where that gap is stated in full.

An availability target, not a record

We aim for 99.9% over a calendar month, excluding announced maintenance. It is a target. We do not publish a measured figure because we do not measure one, and quoting a number we cannot evidence is the thing this page exists to avoid.

What has to exist first

Before this page can report anything

An honest status page needs three things this platform does not have: an external prober that checks availability from outside our own infrastructure, a record of incidents with their start and end, and a component breakdown that distinguishes "the exam runner is down" from "certificate verification is slow".

When those exist this page becomes the feed. The address will not change, so a link saved today keeps working.