In a recent development, Tor, the formidable open-source software for enabling anonymous communication, announced the discontinuation of its Cloud service. The company broke the news in a detailed blog post, revealing the underlying reasons behind this pivotal decision.
Tor’s Cloud service operated on the Amazon EC2 platform, serving as an important asset within the company’s technological structure. However, maintaining the software had become increasingly difficult due to the presence of certain persistent bugs, impacting the functionality and user experience.
The predominant cause for the termination of Tor’s Cloud was a major bug within the software that rendered it completely dysfunctional. This glitch hampered the very purpose of the service, preventing users from accessing the Internet. In addition to this, there were over a dozen minor bugs detected that further complicated the situation. One of these was singled out as the ‘highest priority’ issue.
Consequently, the number of Tor Cloud bridges, which form the connection points within the Tor network, steadily declined since the beginning of 2014. This is believed to be a direct result of the highlighted bugs and other technical issues plaguing the software.
On a positive note, Tor informed its users that the discontinuation of its Cloud project would not affect already configured Tor Cloud instances. This assurance holds significance as each instance, when initiated, copies a template of the operating system and settings. Thus, the removal of the original template does not impact any existing copies, allowing current users to continue running their bridges without any interruption.
Initiated as an experimental endeavor, Tor Cloud was envisioned to offer a practical way for volunteers to contribute to the Tor network. By running bridge relays using Amazon’s EC2 infrastructure, users could easily set up and maintain Tor bridge relays in the cloud.
Despite the potential disappointment that this announcement may trigger among its community members, Tor emphasized that there are alternative methodologies to run Tor bridges. This termination does not affect the broader Tor network or the users’ capabilities to contribute towards network privacy and freedom.
Reflecting on this decision, it’s clear that managing complex cloud infrastructure projects, especially for non-profit organizations, is an arduous task. Limited resources add an extra layer of complexity to such projects. Adapting to these challenges, Tor is realigning its focus on enhancing its core privacy tools while encouraging community members to explore alternative ways to support the network.
Tor remains committed to its mission of protecting online privacy and circumventing censorship, despite facing tough decisions regarding project prioritization.
This article was updated in 2025 to reflect modern realities.
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.
