Status
Whether the site is answering as it should, asked from outside every thirty minutes. These are measurements, not a promise: there is no service level agreement, and the figures below are only ever what the checks saw.
How this is checked
A scheduled job on GitHub's servers asks the live site three questions every thirty minutes. Each has to be answered in twenty seconds, and each has one right answer:
- The front door.
GET /has to answer 200 with the front door's page. This is the pages themselves, and the tools in them. - Keys and sign-in.
GET /api/licencehas to answer 200 with{ "ok": true }. This is the server route that makes and renews Pro keys. - The Pro lock. A real file under
/pro-code/, asked for with no key, has to be refused with 402 and the lock's own header. A 200 here would mean the paid applications' code was being handed to anyone who asked, which is the one failure worse than being down; a 404 or a 500 would mean the lock itself is broken.
The answers are kept for seven days and the note of any failure says what came back. GitHub starts scheduled jobs late when it is busy, sometimes by many minutes, and can skip one, so the times above are when each check actually ran, and a gap is a check that did not run rather than one that passed.
What this does not check: every tool, and your browser. The tools run on your device, so a tool that has already loaded, or that you have installed, keeps working through an outage of the server; what stops is anything that needs it, such as buying Pro, renewing a key, or opening a Pro application whose code is not yet on this device.
The record is kept outside this site's code, so that writing it every half hour does not make a new deployment every half hour, and this page reads it through /api/status on this site, so that opening it tells nobody else you did. What that route reads is on /trust.
If something is wrong
If this page does not load at all, the site is not answering you, and the site's X account and Discord are the places to ask. If the checks pass and something still does not work for you, the support page writes an email with what we need to know, and you read it before it goes.