3 ms·
Honestly, I don't find it bad at all. It hardly ever crashes or drops connections and we use it a lot. My only beef is voice communication latency. It is defin
by osigurdson 4y ago
Honestly, I don't find it bad at all. It hardly ever crashes or drops connections and we use it a lot.
My only beef is voice communication latency. It is definitely several hundred milliseconds - far worse than using a phone. This leads to very unnatural CB-radio type conversations (you almost need to say "over" when you are finished talking).
- 4whaitsworth99 4y agoFor what it's worth... I use teams all day for communication across all of the teams I work with in 3 different countries and have no latency issues. I agree with your assessment that it isn't bad though. I don't have any of the issues that everyone here is reporting. Everything just works, I can call any of the 1000s of people at our org and they can join effortlessly. I'd happily switch to whatever else to be less reliant on MS, but teams being bad isn't a valid argument in my mind.
- osigurdson 4y agoI might be exaggerating a little. However, that is one thing that we noticed when back in the office post covid. Small group (5-8 people) conversations flowed better. In small groups, low latency is very important. It matters less with one on one conversations and is unimportant for large meetings. I want sub 50ms.