So for a while now I've been throwing this link at people! https://forms.gle/4cb5j1JWrUh1JfdYA
It's a quick troubleshooting guide I designed a while back to help people identify possible issues with Stadia centered around bad connectivity and latency/stuttering problems. It's nothing fancy, but has helped enough people resolve some of their issues (about 25%).
As of today, I've had almost 100 people go through the form and give me feedback, so I decided it would be cool to throw out a few statistics and possible insights that might be interesting for people out there!
First, most of the answers I got are from the US (50%), Germany (10%), Canada (10%) and the UK (10%). This probably corresponds to the population on the official Reddit, so I wouldn't read too much into it.
Next it seems that many issues are directly linked to using Stadia over WiFi (39% had issues when over WiFi, 39% over both WiFi and Ethernet, and only 22% when plugged in). This isn't too surprising either, but it does really show how much of a difference a direct connection can make.
Now within these categories (WiFi/Ethernet/Both) the percentage of people having issues in Chrome vs Chromecast/Phone/All is staggering at 63%–72%! And this bit is really telling, when coupled with all the discussions I've seen on Reddit, it really seems like one of the main problems people have when running Stadia is that there are way too many factors that can affect the quality of you connection when using Chrome (browser extensions, antivirus, VPN, firewall issues, low-quality network card, bad handling of video decoding, ...). In fact, if Google were to build some form of tool to try and identify some of these issues, I think it might help a pretty decent portion of users!
I'm not sure if this is meaningful, but I asked people what ISP they were using and AT&T and Spectrum were the only ones to come up quite a few times (but the sample size is much too small to be worth much I think).
As form modems, there are a whole bunch, but quite a lot of Google WiFi. Once again, not enough data to make this really meaningful, but still worth pointing out that it's not a catch-all solution.
And there it is. I could probably have built the form to gather a bit more data, but that wasn't really my goal at that point in time.