Removal of roughly 600 'KAX17' non-exit relays. Run a Tor Bridge campaign, offers rewards for running obfs4 bridges.

There was a temporary cease of blocking for less than a day starting on. īlocking of Tor directory authorities, relays, default obfs4 bridges, meek-azure, and Snowflake in some ISPs in Russia. The web server is added to the registry of blocked domain names in Russia, by IP addresses and by hostname *.recordīlocking of the IP address of the meek-azure front domain in certains ISPs in Russia, part of a wider phenomenon of blocking Tor beginning. The Tor Project web server block is expanded from *.to *. Release of Tor Browser 11.0.2, containing a new default obfs4 bridge 'deusexmachina'. The fraction of networks in Russia blocking Tor, measured by OONI, increases from about 20% to about 50%. Release of Tor Browser 11.5a1, with an altered DTLS fingerprint in Snowflake to counteract blocking in Russia. Rebooted the Snowflake bridge to increase the number of CPUs from 4 to 8. Access was restored for a few hours each day.Īnother round of obfs4 enumeration and blocking occurs in Russia. Was preceded by a shutdown of most mobile networks starting 14:30. Increased capacity of the mapping to client IP addresses on the snowflake bridge.Ĭountry-wide Internet shutdown in Kazakhstan. The Tor Project begins to distribute obfs4 bridges that listen on ports that are reachable in Kazakhstan, despite the ongoing Internet shutdown. Debugged connection problems until 18:47:00. Switched the snowflake bridge to a temporary load-balanced staging server. Switched the snowflake-server (at the time running on a load-balanced staging server) for a version with CPU profiling. Debugged connection problems until 19:52:04. Switched the snowflake bridge from a load-balanced staging server back to the now load-balanced production server. Bridge users increase in Russia relay and bridge users increase in Ukraine.

In the following days, various social media are partially blocked in Russia.

Tor bridge db