Lnproxy wouldn’t have initiated the payment to you if Strike didn’t pay the wrapped invoice, so assuming you saw evidence of a payment in Phoenix, we can rule out strike. It’s unclear from your post how long the payment was stuck, but lnproxy (if it didn’t experience an unexpected problem which given the code I read 6 months ago would cause it to exit and required manual recovery) would’ve released the held payment once it knew the payment failed. It’s possible that ACINQ was holding the payment from lnproxy, trying to splice in liquidity to your channel and that took awhile to fail.