All systems operational

Checked live at 2026-08-14 14:46 UTC

Services

API
operational
Models catalogue
operational
Authentication
operational

These checks run when you load this page, against the public endpoints. Nothing here is cached or simulated.

Incident history

Major outage

New sign-ups suspended during an age-verification change

Resolved

New account registration was unavailable while an age and region verification requirement was introduced. Existing users were unaffected. Because no verification email was sent, we have no record of who was turned away — if you were affected, please get in touch.

Started
2026-07-20 00:00 UTC
Duration
23 days
Affected
Sign-up · Sign-in for accounts without a date of birth on file
  1. 2026-08-11 20:30 UTCFixed and deployed. Sign-in now asks for your date of birth and country of residence the first time you sign in, and tells you plainly when something is missing. We verified the full path end to end: request a code, receive it, verify it, account created.
  2. 2026-08-11 19:30 UTCCause identified. Our identity service checks age and region before sending a verification code. For a first-time user there is no date of birth on file yet, so it declined — correctly. Our sign-in page never asked for one, and it reported the refusal as “could not send email”. So the account could never be created, and the error pointed at the wrong thing.
  3. 2026-08-11 18:40 UTCReported to us by a prospective customer who could not sign up. Investigating.
  4. 2026-07-20 00:00 UTCNew sign-ups suspended. An age and region verification requirement was introduced in our identity service on this date, and account registration was unavailable while the sign-up flow caught up with it. Because the refusal produced no audit record and surfaced as a mail delivery message, we did not notice that registration had stopped.

About historical uptime

We are not publishing a 30-day uptime figure yet. Some of our monitoring is currently unreliable — two checks report failure while the underlying service is demonstrably working, and one still watches a server we retired. Publishing a number derived from that would be misleading. We are rebuilding the monitoring first, and will publish uptime once the numbers mean something.

Something wrong that is not listed here? Tell us.