The surprising thing is if I do this in Bangalore, it terminates in SFO according to geolocation loo
The surprising thing is if I do this in Bangalore, it terminates in SFO according to geolocation look up.

/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.
cache.put doesn't actually return anything, just an empty promise. R2 does return an R2Object, but that doesn't actually include the body. For the two requests to Backblaze, you can call response.body.cancel() to ensure they are closed