@Leo I guess I could get multiple threads by having my worker make multiple calls back to itself?
@Leo I guess I could get multiple threads by having my worker make multiple calls back to itself?


/cdn-cgi/trace path of your website, ex: https://d1-a-ut.makemyparty.live/cdn-cgi/trace, and look at colo={airportcode}, and that airport code is the identifider of the location you hit
38.10.0.47, you get a peering db result, it's CF's IP for them on Extreme IX in Bangalore, so it's most likely going to Cf's Banglore colo

If the system detects that a Worker is deadlocked on open connections — for example, if the Worker has pending connection attempts but has no in-progress reads or writes on the connections that it already has open — then the least-recently-used open connection will be canceled to unblock the Worker.Otherwise, not sure what it could be
If the Worker later attempts to use a canceled connection, an exception will be thrown. These exceptions should rarely occur in practice, though, since it is uncommon for a Worker to open a connection that it does not have an immediate use for.
/cdn-cgi/tracehttps://d1-a-ut.makemyparty.live/cdn-cgi/tracecolo={airportcode}38.10.0.47