Why webkit-based browsers sometimes make TLSv1 hello and ERR_TIMED_OUT happens?

I usually use Debian + Chromium.
Sometimes some sites give me this error:

It even may become ok later after some time but often Wireshark gives me this:

I noticed that on failure Chromium made TLSv1 Hello and on success it was TLSv1.2.
I tried another webkit-based browser – same error.
I tried Firefox – everything is ok.
Where these settings are that control TLS?
Why this happens?