We can’t say for sure it’s the exact same underlying issue, but 2.5 definitely had enough reliability problems for us that we spent a lot of time trying to stabilize it.
On our side, the main documented 2.5 problems were mid-session 1011 / 1008 disconnects, transcription reliability issues during longer speech, and general turn-management / instruction-following instability. We tried multiple times to make 2.5 robust enough for production, and before migrating we even spent about 3 weeks exploring a WebRTC architecture via LiveKit because we suspected part of the problem might be in the audio pipeline or transport layer.
What ultimately changed the outcome for us was moving off 2.5. We migrated to 3.1 Flash Live and also tightened our client-side turn handling, and that was the first setup that felt materially more stable and production-ready for us.
If migration is possible in your environment, I’d strongly recommend testing 3.1 as well.