If the AI gateway fails
The gateway walks the fallback chain across providers. If every provider fails, the app serves your cached plan. You still get missions; the explanations are shorter.
JESS MOVEPlatform status
Checked just now
Checked when you loaded this page, not cached. Only three things below are actually measured — the rest are listed as unknown, because nothing is yet watching them, and a green tick nobody is checking is worse than no tick at all.
Checked live
Read from the API’s own health endpoint at Sun, 13 Sep 2026 00:36:06 GMT. State is carried by the badge text as well as the colour.
Not yet monitored
These are live in the product. There is no independent check on them yet, so this page will not claim one. When uptime monitoring is in place they move up.
In build
Incident history
Nothing has been recording availability, so there is no history to publish. This page previously showed thirty days of green bars and three written-up incidents with dates and resolution times. None of it had happened. It has been removed rather than left to be believed, and when a real incident occurs it will be written here with the same detail those inventions had.
Degradation policy
This part is not a status report — it is how the system is built to fail, which is true whether or not anything is failing today.
The gateway walks the fallback chain across providers. If every provider fails, the app serves your cached plan. You still get missions; the explanations are shorter.
Readiness falls back to calendar structure, device inactivity and your own check-in. The engine widens its uncertainty rather than pretending to know.
A mission whose window has closed is suppressed, not sent late. Arriving after the gap has gone is the exact defect the product exists to avoid.
Safety screening, the five-variant requirement, the under-18 body-metric prohibition and the k-anonymity floor. These fail closed: if they cannot be evaluated, nothing is served.
Report a problem we have not listed: contact us.