When the route
to the record breaks.

WikiLeaks:
pressure across the stack.

Hosting, domain resolution and payments became separate points at which a publisher could lose support.

In December 2010, WikiLeaks faced service withdrawals across several infrastructure layers. The evidence below shows converging pressure and public political intervention. It does not establish that every provider acted under a single coordinated instruction.

Hosting: the servers.

Amazon stopped hosting WikiLeaks on 1 December. Associated Press reported that the withdrawal followed questions from congressional staff and was praised by Senator Joe Lieberman. The same report said WikiLeaks remained hosted by Sweden’s Bahnhof. Associated Press, via Phys.org · 3 December 2010.

DNS: the way to find the site.

EveryDNS ended service for wikileaks.org late on 2 December. Its stated reason was that DDoS attacks against the domain threatened other customers on its infrastructure. The Register also reported that mirrors and other copies remained available: loss of one domain’s DNS service was not erasure of every copy. The Register · 3 December 2010.

Payments: the ability to receive support.

Visa, MasterCard and PayPal also suspended services to WikiLeaks. WIRED reported that Lieberman publicly defended companies withdrawing support. WIRED · 9 December 2010.

The infrastructure lesson.

These are different dependencies: keeping data online, finding it through a domain, and funding operations. The withdrawals accumulated around the same publisher, but their mechanisms and stated reasons were not identical.

Design relevance: recovery should not depend on the continued cooperation of one host, one domain or the company behind a tool. Independent copies and retrieval routes matter. URMA’s preservation goal does not solve payment exclusion, network shutdowns or every form of censorship.

Marion County Record:
the newsroom’s tools removed.

On 11 August 2023, law enforcement searched the newspaper’s office and seized computers, phones, a file server and journalistic work product. The newspaper said the seizure threatened its ability to publish its weekly edition. U.S. Press Freedom Tracker · newsroom seizure record.

Design relevance: a file that exists only on seized equipment may become unavailable to its newsroom. A recovery path needs material preserved elsewhere and a separately available key before the device is lost. This case does not prove permanent loss of the newspaper’s files, or that encryption would have prevented the raid.

Apple Daily:
when a publication goes offline.

Following raids, arrests and the freezing of company assets, Apple Daily closed in June 2021. Its last printed edition appeared on 24 June; it announced that its digital version would go offline on 23 June. The research’s source for this chronology is a secondary compilation: Wikipedia · Apple Daily raids and arrests, with underlying references.

Design relevance: the closure of a publisher can remove the normal route to its archive. That does not establish that every article or independently saved copy disappeared. Preserving records before closure and keeping them retrievable elsewhere are separate requirements.

Evidence can disappear
with a platform post.

Human Rights Watch reviewed 5,396 pieces of Facebook, Twitter and YouTube content cited in 4,739 of its reports since 2007. It found that 619, or 11%, had been removed. The finding concerns that sample, not all online evidence. Human Rights Watch · 10 September 2020.

HRW called for independent preservation of potential evidence with appropriate access safeguards. The finding does not show that every removal was state censorship or automated moderation, and it is not an endorsement of permanent public blockchain storage.

Design relevance: a link to a social-media post is not an independent archive. Preservation must account for platform removal while protecting sensitive material and the people represented in it.