/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

AWS says Mechanical Turk will no longer accept new customers and that it is placing the crowdsourcing service in maintenance, signaling its future retirement

Workers who use OG crowdsourcing platform say AWS is closing accounts  —  Amazon Web Services will stop accepting new customers …

The Register Simon Sharwood

Context & Ripple Effects

Mechanical Turk’s wind-down fits a broader Amazon pattern in the related coverage: products and initiatives including Product Ads, Amazon Care, and Scout were discontinued when they no longer fit the company’s long-term priorities.

For AWS, the timing contrasts with investment in Bedrock AgentCore and a $1B AI-focused forward-deployed-engineer organization, indicating a portfolio increasingly organized around enterprise AI platforms and services rather than a legacy standalone marketplace.

First-order effects

  • Mechanical Turk can no longer add customers, forcing prospective users to select another way to source human tasks rather than build new workflows on the service.
  • Existing users face a maintenance-only service and must plan for migration; workers are exposed to declining task availability and, as reported, account closures.

Second-order effects

  • Organizations that used Mechanical Turk for human-in-the-loop work, including data collection or evaluation tasks, will need to move work to alternative providers or bring more of that process in-house.
  • The closure can redirect demand toward competing crowdsourcing and data-operations services, while making continuity and migration support more important to buyers.

Third-order effects

  • If AWS continues to retire peripheral legacy offerings while funding AI infrastructure and customer-facing AI deployment teams, its portfolio becomes more concentrated on higher-level cloud and enterprise AI services.
  • The exit also underscores that human-task marketplaces are not necessarily durable strategic assets for hyperscalers; their role may increasingly be supplied by specialists or embedded within broader AI-data operations.

The trend: This is one data point in AWS’s reallocation from older standalone services toward enterprise AI platforms, tooling, and deployment capacity.

Discussion

  • @phelimb Phelim Bradley on x
    When we started @Prolific, we were motivated by the question “what if MTurk was actually good”? It's sad to see Mturk closing it's doors, but it's not a surprise. It's the result of years of degrading data quality and an unhealthy marketplace. The future of AI and science [image]
  • George Bliatsios George Bliatsios on linkedin
    Leaving aside the ethics of it for a moment (which doesn't mean at all the considerations are minor) and the quality and operational problems Amazon presumably …
  • @carnage4life Dare Obasanjo on bluesky
    It's the end of an era.  Amazon's Mechanical Turk is a classic instance of “fake it until you make it.”  —  Instead of faking artificial intelligence by hiring people in low income countries to perform basic data entry or data processing tasks, it's now cheaper to perform those t…
  • @jmsdnns @jmsdnns on bluesky
    this is wild.  the first time I worked with CCB (Prof friend at Penn) we built tools to use mechanical turk for generating datasets for translation algos  —  the boto library had an incomplete implementation so I finished it and then we used it for his research at Johns Hopkins  …
  • @ealeyner Eli Aleyner on x
    End of an Era. Artificial artificial intelligence no longer needed when real AI is decent? Can this mean that my code would finally be retired?
  • @jamesekaplan James Kaplan on x
    Amazon really blew an 18 yr lead on Mercor