Sustaining Snowflake operations
The team that runs the primary Snowflake bridge is raising funds to pay for server operating expenses such as bandwidth, hardware, and maintenance.. You can help the project by donating to the project on Open Collective:
Snowflake Daily Operations – Open Collective
What follows is an update originally posted on the Open Collective project.
The year 2022 was transformative for the Snowflake censorship circumvention system. The year saw a massive increase in the number of Snowflake users, fueled by some significant censorship events where Snowflake was one of few systems that worked to keep people connected. At the end of 2022, something around 2% of all Tor users used Snowflake to access the Tor network and the uncensored Internet. The Snowflake team has had to invest in powerful server hardware and a fast network connection in order to keep up with demand. Servers and bandwidth don't come for free, which is why we have started an Open Collective project. We aim to collect funds to sustain current operational needs and support future upgrades.
The first major event affecting Snowflake usage actually happened at the end of 2021. Snowflake is deployed as a circumvention system (a pluggable transport) alongside the Tor anonymity system. People use Snowflake and other pluggable transports when direct access to the Tor network is blocked. On December 1, 2021, some Internet service providers in Russia suddenly blocked access to most ways of accessing Tor, including, briefly, Snowflake. With the help of people in Russia, Snowflake developers found and fixed the protocol flaw that was being used to discover and block Snowflake connections, and Snowflake began working again in Russia. But because other ways of accessing Tor remained blocked, more and more people in Russia began using Snowflake.
All the new users started to overwhelm the resources of the server that was then hosting the Snowflake bridge. There were times when the system was barely usable because off all the people trying to use it at once. We had to innovate a new way to deploy a Tor bridge to remove a performance bottleneck; then, when that had taken us as far as it could, we started looking for a more powerful server. We moved to better hardware in March, which enabled the Snowflake bridge to meet demand. The situation remained stable for about the next six months.
On September 21, 2022, Internet service providers in Iran began imposing even more severe censorship than usual, in response to mass protests. Evidently, many people in Iran turned to Snowflake to circumvent the blocks, as the number of users quadrupled in a matter of days. This began a few days of intense performance and optimization work because the greatly increased load was straining even the upgraded server hardware.
The performance work was ultimately successful, and the bridge started handling its new load of users smoothly. Then, about two weeks after the protests began, Snowflake traffic from Iran dropped off precipitously. The cause turned out to be an oversight in the implementation of Snowflake, a TLS fingerprint that has been blocked. When a fix for that problem was deployed, the number of users began to grow again, faster than ever.
Over the course of 2022, Snowflake scaled from 5,000 to 75,000 users. It has been made possible by a dedicated team and investment in hardware infrastructure. As you can see from the user graph, demand for Snowflake continues to grow. It seems likely that there is additional blocking in Russia that has not yet been addressed; and when it is, it is likely to increase usership further.
We encourage respectful, on-topic comments. Comments that violate our Code of Conduct will be deleted. Off-topic comments may be deleted at the discretion of the moderators. Please do not comment as a way to receive support or to report bugs on a post unrelated to a release. If you are looking for support, please see our FAQ, user support forum or ways to get in touch with us.