We're aware of reports that access to Signal has been blocked in some countries. As a reminder, Signal's built-in censorship circumvention feature might be able to help if your connection is affected:

Signal Settings > Privacy > Advanced > Censorship circumvention (on)

We have already started working on more advanced censorship circumvention techniques, but in order for these efforts to be most effective we need the big companies who are dragging their feet on moving away from plaintext SNI headers to start taking this problem more seriously.
Solutions like Encrypted Client Hello (ECH) remove the plaintext server name from the TLS handshake, which makes it far more difficult for hostile ISPs to block access to the sites and services you care about — but this isn’t widely supported yet. We hope that starts to change.
@signalapp Keep in mind that many highly censored countries you talk about just will ban ECH at all. So I don't think that your solution is viable.
@network_is_reliable @signalapp Can an operator ban ECH?
@dinosm @network_is_reliable @signalapp Yes, but that's not practical if all mainstream sites use ECH. Adoption is critical to everybody's safety.
@dalias @dinosm @network_is_reliable @signalapp yeah it's the herd immunity effect for privacy
@ireneista @dalias @dinosm @network_is_reliable @signalapp the hard problem in that game is, unfortunately, the rollout. totalitarian censors will write their DPI rules as the spec is written, turning the new feature into "blocked in X country" from day 1
@valpackett @dalias @dinosm @network_is_reliable @signalapp yes absolutely, that's a real danger
@ireneista @valpackett @dalias @dinosm @network_is_reliable @signalapp in fact that's basically been the case with ECH since the spec was in the early stages, sadly

@erincandescent @ireneista @valpackett tbh I think you’d probably need to force it via making it mandatory in TLS 1.4 or whatever

And even then!