Just had a phone call from a member of the Google tech te...

[Bergerac82]

Just had a phone call from a member of the Google tech team.
My case was allocated to him. According to said tech, the Stadia team are working with Shaw to understand/resolve the problem. No timeline given, but he promised frequent updates.

It's great to hear from them, and to be kept in the loop, but at 10 days and counting of being unable to use the service I'm losing confidence in purely cloud based gaming, at least with Shaw as the only viable provider in my area.

As others have said, it's not the end of the world (I've read 5 books since Stadia died), but it's a service paid for and unusable.

[shaw-tony]

@talios @CapnCrunch @Alexey @Flourens @JonahL @mattywaggleburn @Jbegould @Exception @Bergerac82 
Thank you so much for your patience. We are indeed working with Google to resolve this matter as it related to the recent service interruption in BC. 

Our engineers are looking for the destination IP. Please post your traceroutes to the Stadia/Geforce Now/xcloud servers. Feel free to also direct message me those details if you aren't comfortable in sharing it publicly.

[mattywaggleburn]

Thanks @shaw-tony, I'm just at work currently but i'll provide the trace routes tonight. would a tracert to stadia.google.com and google dns (8.8.8.8) be enough?

[shaw-tony]

@mattywaggleburn yes that should be fine as I am unable to locate their specific server address.

[Bergerac82]

From the traceroute tool on the Shaw router 

Status: Complete !
1: 7,8,6 24.67.192.1 24.67.192.1
2: 21,21,20 rd3cs-be118-1.ok.shawcable.net 64.59.170.41
3: 38,37,39 rc1st-be5.vc.shawcable.net 66.163.67.217
4: 37,38,40 rc2wt-be50-1.wa.shawcable.net 66.163.70.106
5: *
6: *
7: 39,39,40 209.85.242.36 209.85.242.36
8: 41,39,40 74.125.243.179 74.125.243.179
9: 46,46,46 209.85.249.94 209.85.249.94
10: 71,70,62 72.14.239.196 72.14.239.196
11: 67,68,71 209.85.247.4 209.85.247.4
12: 69,86,69 209.85.254.242 209.85.254.242
13: 91,88,87 142.250.57.139 142.250.57.139
14: 94,99,92 209.85.254.128 209.85.254.128
15: 85,90,94 108.170.237.213 108.170.237.213
16: 87,85,90 108.170.237.213 108.170.237.213

[Exception]

Launched Stadia game on Chrome in windows 10.  Used Netlimiter to identify IP which was getting the bulk of the Stadia traffic.  Opened up command prompt and did a traceroute to that IP.

C:\tracert 136.116.3.86

Tracing route to 136.116.3.86 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms router.asus.com [192.168.2.1]
2 16 ms 7 ms 11 ms 68.147.160.1
3 9 ms 8 ms 9 ms rc3no-be104-1.cg.shawcable.net [64.59.131.189]
4 25 ms 25 ms 24 ms rc2wt-be100.wa.shawcable.net [66.163.75.233]
5 26 ms 28 ms 31 ms 72.14.242.90
6 * * * Request timed out.
7 29 ms 30 ms 29 ms 209.85.254.246
8 29 ms 28 ms 29 ms 172.253.140.11
9 31 ms 28 ms 29 ms 172.253.140.120
10 28 ms 27 ms 26 ms 136.116.3.86

Trace complete.

[Exception]

Just an FYI for anyone reading this above, my connection goes to my router --> shaw modem --> Calgary --> Winnipeg --> Nebraska --> and then I presume to Mountain View in California.  Seems like our traffic is taking the scenic route.

[Exception]

Just to note, the Stadia website IP isn't going to give you any useful info for route tracing.  I suggest Shaw ask Google for the list of IP addresses instead of relying on customers.

[Bergerac82]

Thanks @Exception .

My traceroute was to the Stadia.google.com IP, so likely not useful.

Happy to run another, but will need appropriate destination IP from Google/Shaw.

@shaw-tony, can your team provide?

[Exception]

@Bergerac82 

136.116.3.86