Status
Where things stand, what we will tell you when they stop standing, and how quickly.
Current state
This page is updated by hand, not by a monitor. We are wiring automated checks and will say so here when they are live. Until then, treat the line above as our last review rather than a live probe, and the commitments below as the thing worth holding us to.
What we commit to
A customer-affecting incident is posted on this page, with what is affected and what we know at the time. Updated as it develops rather than once at the end.
That first post goes up within an hour of us confirming an incident is customer-affecting, whether or not we understand the cause yet.
Anything that materially affected requests gets a written account of what happened and what changed as a result. Published here, not sent only to whoever complained.
A breach involving personal data follows the notification terms in the Data Processing Agreement, which are contractual and have their own clock.
Incident history
No customer-affecting incidents have been recorded. That is a short history rather than a track record: ModelBeat is in public beta and this page starts here so there is somewhere for the first one to go.
Being told
There is no subscribe button here yet, because a button that collected addresses we had no way to send to would be worse than none. Write to hello@neuralarc.ai and we will add you to the incident notice list by hand, which is how it works today.