Amazon Denies Dropping WikiLeaks Because Of ‘Government Inquiry’
Amazon.com (NSDQ: AMZN) says that a “government inquiry” did not drive its controversial decision to stop hosting WikiLeaks' site Monday. In a short blog post, the company says charges that a government inquiry prompted …
Context & Ripple Effects
Amazon's denial lands one day after TPMMuckraker reported how Senator Joe Lieberman's office pressed the company over its hosting of the leaked diplomatic cables, making this blog post the company's first on-the-record pushback against the account of Lieberman getting Amazon to drop WikiLeaks. The dispute matters because Amazon had been the most mainstream home WikiLeaks' trove had found, and its exit within days of publication set off a scramble for infrastructure.
WikiLeaks, meanwhile, has already relocated its archive to a former Cold War bomb shelter with steel doors, confirming that the site is abandoning rented commercial hosting for hardened, self-controlled facilities. Whether readers believe Amazon's denial or the congressional-pressure narrative will shape how other providers respond to similar calls.
First-order effects
- Amazon's hosting relationship with WikiLeaks is terminated regardless of motive, and the company now owns a public controversy that pits its government and enterprise customer base against free-expression critics.
- WikiLeaks is pushed onto self-operated, physically hardened infrastructure, trading the uptime and scale of a commercial cloud for independence from any single provider's political judgment.
Second-order effects
- Other US hosting and cloud providers now face the same playbook — a senatorial phone call plus a public spotlight — and must decide whether accepting WikiLeaks-class customers is worth the exposure.
- If providers conclude politically sensitive archives are bad business, WikiLeaks and similar publishers lose access to mainstream infrastructure tiers, concentrating their operations among niche or offshore hosts.
Third-order effects
- If informal congressional pressure proves sufficient to dehost a publisher, cloud companies will face growing demands for written policies and disclosure of government removal requests rather than ad-hoc exits — a transparency norm that did not exist when Amazon made this call.
- Publishers handling leaked material may begin treating US-hosted infrastructure as a jurisdictional risk by default, accelerating a structural split between mainstream commercial clouds and purpose-built, offshore or self-hosted alternatives.
The trend: Commercial cloud infrastructure is emerging as a lever of state pressure against publishers, pushing the industry toward either formalized government-request procedures or hosting arrangements deliberately outside US jurisdiction.