maybe important log:

from chrome://net-internals/

4278: SSL_CONNECT_JOB
ssl/www.facebook.com:443
Start Time: 2018-06-01 13:29:21.729

t= 2153 [st=    0] +SOCKET_POOL_CONNECT_JOB  [dt=21012]
                    --> group_name = "ssl/www.facebook.com:443"
t= 2153 [st=    0]   +SOCKET_POOL_CONNECT_JOB_CONNECT  [dt=21012]
t= 2153 [st=    0]      TCP_CLIENT_SOCKET_POOL_REQUESTED_SOCKET
                        --> host_and_port = "www.facebook.com:443"
t= 2153 [st=    0]     +SOCKET_POOL  [dt=21012]
t=23165 [st=21012]        SOCKET_POOL_BOUND_TO_CONNECT_JOB
                          --> source_dependency = 4279 (TRANSPORT_CONNECT_JOB)
t=23165 [st=21012]     -SOCKET_POOL
                        --> net_error = -118 (ERR_CONNECTION_TIMED_OUT)
t=23165 [st=21012]   -SOCKET_POOL_CONNECT_JOB_CONNECT
                      --> net_error = -118 (ERR_CONNECTION_TIMED_OUT)
t=23165 [st=21012] -SOCKET_POOL_CONNECT_JOB
4356: HTTP_STREAM_JOB
https://www.facebook.com/
Start Time: 2018-06-01 13:29:41.004

t=21428 [st=   0] +HTTP_STREAM_JOB  [dt=1738]
                   --> expect_spdy = "false"
                   --> original_url = "https://www.facebook.com/"
                   --> priority = "HIGHEST"
                   --> source_dependency = 4355 (HTTP_STREAM_JOB_CONTROLLER)
                   --> url = "https://www.facebook.com/"
                   --> using_quic = "false"
t=21428 [st=   0]    HTTP_STREAM_JOB_WAITING  [dt=0]
                     --> should_wait = false
t=21428 [st=   0]   +HTTP_STREAM_JOB_INIT_CONNECTION  [dt=1737]
t=21428 [st=   0]     +HOST_RESOLVER_IMPL_REQUEST  [dt=0]
                       --> address_family = 0
                       --> allow_cached_response = true
                       --> host = "www.facebook.com:443"
                       --> is_speculative = false
t=21428 [st=   0]        HOST_RESOLVER_IMPL_IPV6_REACHABILITY_CHECK
                         --> cached = true
                         --> ipv6_available = false
t=21428 [st=   0]        HOST_RESOLVER_IMPL_CACHE_HIT
                         --> address_list = ["31.13.72.38:443"]
t=21428 [st=   0]     -HOST_RESOLVER_IMPL_REQUEST
t=21428 [st=   0]     +SOCKET_POOL  [dt=1737]
t=23165 [st=1737]        SOCKET_POOL_BOUND_TO_CONNECT_JOB
                         --> source_dependency = 4278 (SSL_CONNECT_JOB)
t=23165 [st=1737]     -SOCKET_POOL
                       --> net_error = -118 (ERR_CONNECTION_TIMED_OUT)
t=23165 [st=1737]   -HTTP_STREAM_JOB_INIT_CONNECTION
t=23165 [st=1737]    HTTP_STREAM_JOB_BOUND_TO_REQUEST
                     --> source_dependency = 4353 (URL_REQUEST)
t=23166 [st=1738] -HTTP_STREAM_JOB

This is indeed unexpected, and I cannot tell based on the log what is causing the issue.  In each TRANSPORT_CONNECT_JOB, host resolver succesfully returns with a cache hit, and then the job times out twenty something seconds later.

Can you try using Incognito mode?  Do you have any proxies set up?  What happens if you temporarily disable your anti-virus software?

Might be worth noting that facebook.com, instagram.com, and whatsapp.com are all owned and operated by Facebook.  Do you experience this issue on any other websites?

Reporter, any chance you could answer the question in comment #3?

yes, sorry.

Incognito mode, reinstalling chrome, reseting to factory, disabling proxies and anti-virus software doesn't help. 
Doesn't find any other sites with the same problem.

It seems that the Windows update broke something, because the problem occurred simultaneously on two PCs that had access to IPV6. But I do not understand why other browsers work fine.
I tried to find any older version of chrome that would work, but none of them worked with this sites. Reinstalling windows on a notebook helped to solve this problem. 

sorry for my bad english

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

wonskcalb@ Thanks for the update.

As per comment #5, can you please confirm if this issue can be closed, as Reinstalling windows on notebook solved this problem. 

Thanks..

wonskcalb: friendly ping, can you response to comment #7?

WontFixing, per comment #5.