Atishay, thanks for your question. We brought it up with Zipkin/Brave to address this specific circumstance. We added alerts to catch similar symptoms in the future. We also issued detailed internal guidance to make sure every Java developer at Netflix is aware of the mechanics of this problem. Note that it's caused not by virtual threads as such, but rather by the interplay between monitors and VTs. Monitor-free code will never experience this condition. As for the affected services - yes, we had to revert virtual threads as a short-term stop-gap measure.