Tango: No, until November 18, 2022 meek was connecting for me. Just, after several attempts (I don’t know exactly the triggers*), which is similar to the DPI work, as I said before. Although, I didn’t check every day before, just occasionally.
After November 18, 2022, ajax.aspnetcdn.com was blocked by sni (not IP).
* This is the subject of discussion. For example, in addition to meek in obfs4proxy, I also had a self-builded meek-client standalone (actual) with modified utls. Let’s say: after several packets, meek-obfs4proxy had connection resets, I repeated several times. Then tried meek-client standalone - ok result. Then, meek-obfs4proxy also started working. Something like that. I never understood the DPI logic. But that’s in the past (for example, on November 13). Now it’s blocked by sni.
And I don’t use the Tor browser. Only console clients.
I have a mobile provider that is famous for DPI. It is strange that he has started sni blocking after November 18. Up to that point, i.e., for the entire year 2022, meek worked as I described above. That is, with difficulties. But the difficulties were only the first few attempts (it looks like DPI work), and then ok.
A couple of years ago, I heard from Turkmenistan users that their DPI also detects meek. It drops connections after a few packets, just like the Russian one.