Davzz

Little_Naz: we are very confident this is not DDOS blocking. Most of the HAR files we have show requests in a 'blocked' state which is the local browser blocking and we have logs on the cloudflare side that clearly show that once the requests folk are complaining about make it there they are very fast.

Its possible that we have changed something that is tripping the browser limits more than in the past - that bit isnt really super obvious to me. Its also possible its something out of our control (e.g. torntools type extensions are used by many users and count towards the browser limits).

If it makes you feel better, here is a bug report with Google engineers complaining about this limit in Chrome: https://issues.chromium.org/issues/40180988. Chrome have made their limit a bit larger since then, but with many tabs (each doing multiple websocket connections and many HTTP requests) its not hard to imagine that we are hitting into this.

Hello all,

Its pretty clear there is no single cause of this from the HAR files I have, but we have made some further changes that we think reduce the number of connections each browser makes (by fixing/improving cache headers for files that dont change). We also turned off HTTP/3 for TORN. The header change took some time to fully apply, but should be applied everywhere now - I am curious how folks find things from about now-ish.

One thing that we have noticed is that some (but certainly not all) of this is caused by many tabs running. Each tab has 2 connections to the main TORN domain, and browsers have limits on the number of connections they make. If you are seeing this, please check that you do not have lots of tabs open and try to reproduce the problem in a different browser if possible.

Clearly, for those users who do have a ISP that has a rubbish connection to cloudflare we are not going to be able to totally fix this, but hopefully we can help make it better! We thank you all for your patience.

-Alex

Hi All,

We have looked at a fair few HAR files from this. We have significantly increased the amount of logging we have in our control from requests before they hit our infrastructure, which helps dig into this stuff. So far, the HAR files i've reviewed all show connection problems between a user and Cloudflare's closest datacenter. Cloudflare is one of, if not the, best connected CDN providers we could have chosen but from time to time folks may have problems between their ISP and cloudflare that are solved by VPNs (which hit another cloudflare POP). Additionally, we are using Cloudflare's 'managed challenge' feature to protect TORN against DDOS attacks that are a sad reality for us - these will sometimes create problems though we have a bit more ability to make changes here if we have clear evidence of specific problems.

If somebody can reproduce this please can you email a sanitised HAR file to alex@torn.com? Please also run the https://speed.cloudflare.com/ at the same time and export the results as a PDF to send. Finally, please try to see if running the free cloudflare VPN (https://one.one.one.one/) on your device makes the problem better or worse.

Thanks!

-Alex

Its possible I have pushed a change that fixed this.

^^ Thanks, i've got a handful of users - no need for more HAR files from new users (i'm emailing some of those users directly to ask for more tho!)