API
Amazon Web Services
Amazon will permanently close Amazon Mechanical Turk (MTurk) — the crowdsourcing marketplace and MTurk API for Human Intelligence Tasks — on 30 September 2026, and the same closure ends SageMaker Ground Truth and Amazon Augmented AI (A2I) human-review workflows
departs 30 Sept 2026
Quick answers
- Is it true that Amazon Mechanical Turk (MTurk) is shutting down?
- Yes. Amazon Web Services has officially announced it, effective 30 Sept 2026. Amazon Mechanical Turk (MTurk) is the on-demand human workforce behind a huge amount of data labeling, survey collection, content moderation, and evaluation work: requesters post Human Intelligence Tasks (HITs) and workers complete them, driven programmatically through the MTurk API (the `mturk` boto3 client and the `mturk-requester` endpoint).
- When does it take effect?
- 30 Sept 2026. Verified against the vendor's own announcement.
- What should I use instead?
- There is no in-place successor from AWS — MTurk, SageMaker Ground Truth, and Amazon Augmented AI (A2I) are all closing together, so this is a move off the platform, not an upgrade.
What this means for you
Amazon Mechanical Turk (MTurk) is the on-demand human workforce behind a huge amount of data labeling, survey collection, content moderation, and evaluation work: requesters post Human Intelligence Tasks (HITs) and workers complete them, driven programmatically through the MTurk API (the `mturk` boto3 client and the `mturk-requester` endpoint). Following an assessment, AWS has decided to close it permanently on 30 September 2026. New customer registration already stopped on 30 July 2026. On the closure date HIT submission ends and all remaining unsubmitted HITs automatically expire, so any pipeline — nightly data-labeling jobs, RLHF/eval loops, academic studies, moderation queues — that calls the MTurk API for human work stops returning results that day. The blast radius is wider than the marketplace: the closure also ends the Amazon Mechanical Turk Worker type in SageMaker Ground Truth labeling jobs and Amazon Augmented AI (A2I) human-review workflows as of 30 September 2026, so ML teams who never touched the MTurk console directly are affected too. Money and records wind down on their own clock: requesters can award bonuses and approve or reject completed HITs until 30 October 2026 (unactioned HITs auto-approve), pre-paid balances are refunded within 30 days, and transaction history stays available only until 28 January 2027 — pull anything you need for the record before then.
Where to go
There is no in-place successor from AWS — MTurk, SageMaker Ground Truth, and Amazon Augmented AI (A2I) are all closing together, so this is a move off the platform, not an upgrade. First, protect what is owed: workers should verify a payment method and transfer schedule in the MTurk Worker Portal, and requesters should verify payment info in the Requester Portal so refunds process cleanly. Export any HIT data, results, and transaction history you need before 28 January 2027, after which the history is gone. Then re-home the human-in-the-loop work: move data labeling and annotation to another managed crowdsourcing/labeling provider (see alternatives), and if you drive MTurk through the API, plan to rewrite the `mturk` boto3 / MTurk API calls against the new vendor's API — there is no drop-in endpoint. Validate the replacement pipeline on real tasks well before 30 September 2026 rather than treating the cutoff as a switch you flip at the last minute.
- Managed data-labeling / annotation platforms (e.g. Scale AI, Labelbox, Appen, Toloka, Prolific for research studies) — evaluate against your task types, quality controls, and API
- Other human-in-the-loop / crowdsourcing marketplaces (e.g. Clickworker, Remotasks) for HIT-style microtasks
- Self-hosted labeling tooling (e.g. Label Studio, CVAT) paired with your own contractor or internal workforce for full control
If any part of your stack quietly relies on humans to label data, run surveys, moderate content, or grade model outputs, there is a good chance it routes through Amazon Mechanical Turk (MTurk) — the marketplace where requesters post Human Intelligence Tasks (HITs) and a global crowd completes them, usually driven through the MTurk API (the mturk boto3 client against the mturk-requester endpoint). After 21 years, Amazon is closing it.
Per Amazon’s official Closure FAQs, following an internal assessment AWS has decided to permanently close Amazon Mechanical Turk on 30 September 2026. New customer registration already stopped on 30 July 2026. On the closure date, HIT submission ends and all remaining unsubmitted HITs automatically expire — so any pipeline that calls the MTurk API for human work stops returning results that day.
The reach is wider than the MTurk console. The same closure ends the Amazon Mechanical Turk Worker type in SageMaker Ground Truth labeling jobs and in Amazon Augmented AI (A2I) human-review workflows as of 30 September 2026. Plenty of ML teams who never opened the MTurk dashboard directly still depend on it through those services, and they are in scope too.
The financial and record-keeping wind-down runs on its own schedule. Requesters can award bonuses and approve or reject completed HITs until 30 October 2026 (anything left unactioned auto-approves), pre-paid balances are refunded within 30 days, and — the part worth a calendar reminder — transaction history stays available only until 28 January 2027. Whatever you need for accounting, research reproducibility, or the record, export it before that date.
There is no in-place AWS successor: MTurk, SageMaker Ground Truth, and Amazon Augmented AI are closing together, so this is a migration off the platform rather than an upgrade path. The immediate tasks are mechanical — workers should confirm a payment method and transfer schedule in the Worker Portal; requesters should verify payment info in the Requester Portal so refunds land cleanly. After that, the real work is re-homing the human-in-the-loop step: pick a managed labeling or crowdsourcing provider, and if you drive MTurk over the API, budget for rewriting the mturk calls against a different vendor’s API — there is no drop-in endpoint. As with every dated shutdown, the trap is a pipeline that works fine for months and then goes silent on one morning in late September. Move the work, and test it on real tasks, before the 30th.
Entry changelog
- — last reviewed.
- — Entry created from Amazon Mechanical Turk's official Closure FAQs (mturk.com/help) and the site-wide closure banner. Surfaced via Layer-2 discovery (HN). Primary source states permanent closure 30 September 2026, HIT submission ending that day, bonuses/approvals through 30 October 2026, refunds within 30 days, transaction history available until 28 January 2027, and that the closure also ends the MTurk Worker type in SageMaker Ground Truth and Amazon Augmented AI (A2I). New-customer registration had already stopped 30 July 2026.
Put this countdown in your README
Building on Amazon Web Services? Drop this badge into a project’s README or docs — it shows the days left and
refreshes on its own every night from this page.
[](https://lastcall.dev/entries/amazon-mechanical-turk-shutdown) Spot an error or a changed date? Tell us and it’s corrected the same night.