Jwumasay joo-maJwumasay joo-maLive operational status for every part of the platform, with the full incident history and what each one affected. Updated as things change rather than after the fact.
Nothing is currently affecting the platform that we are aware of.
Sign in, task queue, submissions
Work requests, deliveries, dataset export
QA, reviews, payouts
Weekly batch and payout rails
Uploads, recordings, exports
Programmatic access for clients
Loading timeline…
This figure is derived from incidents we have declared on this page, not from an external uptime monitor. Any period with no declared incident is counted as healthy. We would rather show you a number you can check the basis of than one you cannot.
A status page that only reports colour is not much use. These are the guarantees that hold regardless of what the board above says.
This page is updated before support replies individually. If something is wrong and you cannot see it here, it usually means we do not know yet, so tell us.
Reserved tasks hold their reservation through an incident, and the timer is extended rather than expiring while you cannot reach the platform.
Accepted work is credited to your ledger the moment QA accepts it, independently of whether the site is reachable. A missed weekly batch runs as soon as the incident clears.
If the client portal is unavailable, the review clock on any delivery pauses for the duration, so no batch is deemed accepted because someone could not sign in.
Tell us. A report from someone actually using the platform is usually how we find out first.
Report a problem