For more than three months,
@Amazon has systematically removed, blocked, or failed to moderate legitimate reviews across my growing library — a library I spent four years building during the war in Ukraine.
@Amazon officially recognized this as part of a “large-scale global technical issue.”
During this entire period, I continued investing into
@AmazonAds and independently driving thousands of targeted readers into the
@Amazon ecosystem through X and other platforms.
22 published books. A combat zone. Daily financial, reputational, and strategic losses. Three months without resolution.
Yesterday, during another night missile attack, I publicly described this endless conflict with
@AmazonKDP on X and LinkedIn.
Within hours, the situation triggered resonance among authors, founders, IT specialists, operators, business leaders, and other professionals.
Only after that did
@AmazonKDP send a new response openly admitting two things:
complete disconnection between Amazon’s internal departments, and complete inability inside KDP itself to resolve the situation.
At the same time,
@Amazon directly stated that even after violating the fundamental mechanics required for an author’s growth and sales, their internal policies provide no compensation mechanisms inside the
@Amazon ecosystem itself — including through
@AmazonAds.
This is broken logic.
According to this position,
@Amazon may continue monetizing traffic and advertising around books whose trust architecture and sales mechanics were damaged by the platform itself, while internal procedures remain more important than solving the actual damage created by the system.
This is no longer a technical issue. It is a systemic failure of operational responsibility.
Any support matters now: reposts, comments, visibility.
The goal is simple: force this situation out of automated stagnation and into a real operational dialogue.
@Amazon, I am waiting for a constructive response. Already.