This was definitely the problem. Can you guess where I started tuning server timeouts (the non-502 errors are expected here)?
Thanks for the help figuring this out! Though this was definitely my own fault, it would be nice if Fly could somehow surface these kinds of errors to the applications (either in the logs or in metrics, somehow).
I’m loving the product so far, keep up the good work!