https://www.bamsoftware.com/talks/crysp-2025-iran/
140.82.121.6 | api.github.com |
216.239.38.120 | google.com |
https://github.com/net4people/bbs
GitHub and Microsoft are willing collaborators in dictatorship.
Look for alternatives to GitHub.
During the shutdown, people in Iran unexpectedly found themselves able to comment on the discussion thread using the GitHub app.
The reason was that the GitHub app uses the GitHub REST API (api.github.com at 140.82.121.6).
Partway into the shutdown, Google search (google.com at 216.239.38.120) suddenly became accessible. (See IODA graph.)
No other Google services: no maps, drive, youtube, etc.
Let's try domain fronting:
But actually, domain fronting was not required.
(Only an IP filter, no SNI filter.)
Pointing Google domains to 216.239.38.120 in /etc/hosts would make them accessible.
Downloading files from Google Drive through the single accessible IP address:
curl --connect-to ::216.239.38.120 --ssl-revoke-best-effort \ -L -o champa-client-darwin-amd64 \ "https://drive.usercontent.google.com/download? id=1ROCBSIsnat8uDQSlOFajuW2XAbeqNNZh&export=download&confirm=t"
There was limited success with an AMP cache tunnel (repo.or.cz/champa.git).
Possible future work: tunnel/rendezvous through GitHub actions? (#issuecomment-2993311379)
The shutdown's effect on Snowflake users:
After the shutdown (ntc.party/t/17068/2):
The June 2025 shutdown was qualitatively different than past shutdowns in Iran. More information: Project Ainita presentation at IETF 123:
The big difference in June 2025: less reliance on BGP-based blocking (routing); instead using selective middleboxes.
Some channels of network access remained open, even during a "shutdown".
Different events called "shutdowns" work differently, even in the same country at different times.
Some forms of fairly traditional censorship circumvention worked in this case, though it is not known whether they would have continued to. (The situation did not persist long enough to reach an equilibrium.)