#latency

[mattywaggleburn]

#latency

[Alexey]

right now Stadia shows connection is Good

31ms latency

Tracing route to 136.116.3.86 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 10.0.0.1
2 8 ms 8 ms 9 ms 174.4.96.1
3 10 ms 11 ms 10 ms rd3ht-be101-1.ok.shawcable.net [64.59.170.109]
4 16 ms 15 ms 15 ms rc3no-be12.cg.shawcable.net [66.163.67.149]
5 24 ms 24 ms 25 ms rc2wt-be100.wa.shawcable.net [66.163.75.233]
6 31 ms 31 ms 30 ms 72.14.242.90
7 * * * Request timed out.
8 24 ms 25 ms 24 ms 209.85.254.236
9 27 ms 26 ms 25 ms 172.253.140.9
10 32 ms 31 ms 31 ms 172.253.140.20
11 34 ms 29 ms 30 ms 136.116.3.86

Tracing route to stadia.google.com [172.217.165.14]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.1
2 21 ms 8 ms 8 ms 174.4.96.1
3 11 ms 11 ms 11 ms rd3ht-be101-1.ok.shawcable.net [64.59.170.109]
4 16 ms 15 ms 15 ms rc3no-be12.cg.shawcable.net [66.163.67.149]
5 25 ms 24 ms 24 ms rc2wt-be100.wa.shawcable.net [66.163.75.233]
6 34 ms 30 ms 31 ms 72.14.242.90
7 33 ms 32 ms 30 ms 216.239.49.117
8 32 ms 31 ms 33 ms 74.125.243.195
9 32 ms 31 ms 31 ms 172.253.71.130
10 65 ms 65 ms 66 ms 72.14.239.196
11 65 ms 64 ms 64 ms 209.85.247.4
12 77 ms 82 ms 77 ms 172.253.76.221
13 81 ms 80 ms 78 ms 74.125.244.145
14 80 ms 77 ms 78 ms 216.239.40.255
15 77 ms 76 ms 77 ms yyz12s06-in-f14.1e100.net [172.217.165.14]

[CapnCrunch]

So i can confirm the issue is still present. It did flash "good" then straight back to unstable and likely to disconnect.

Tracing route to stadia.google.com [172.217.0.14]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.1
2 8 ms 6 ms 7 ms 70.72.160.1
3 8 ms 8 ms 8 ms rc3so-be150-1.cg.shawcable.net [64.59.132.145]
4 30 ms 30 ms 30 ms rc1wt-be82.wa.shawcable.net [66.163.76.9]
5 28 ms 28 ms 29 ms 72.14.221.102
6 30 ms 29 ms 29 ms 108.170.245.123
7 * 67 ms * 209.85.249.94
8 57 ms 57 ms 60 ms 108.170.233.244
9 61 ms 58 ms 57 ms 209.85.143.102
10 58 ms 58 ms 57 ms 209.85.250.34
11 56 ms 56 ms 56 ms 108.170.243.193
12 57 ms 56 ms 57 ms 216.239.42.35
13 57 ms 57 ms 56 ms ord38s04-in-f14.1e100.net [172.217.0.14]

[mattywaggleburn]

Did this twice with NetLimiter, 2 ip's that had the majority of the traffice to google, both appear to be located in Kansas

Servers:

136.112.133.141

136.115.231.242

Tracing route to 136.115.231.242 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.24.72.1
2 13 ms 11 ms 13 ms 70.75.96.1
3 14 ms 15 ms 13 ms rc3no-be134-1.cg.shawcable.net [64.59.133.53]
4 28 ms 27 ms 30 ms rc2wt-be100.wa.shawcable.net [66.163.75.233]
5 32 ms 32 ms 33 ms 72.14.242.90
6 * * * Request timed out.
7 29 ms 32 ms 35 ms 74.125.243.177
8 30 ms 29 ms 31 ms 74.125.243.178
9 62 ms 52 ms 47 ms 172.253.71.120
10 63 ms 58 ms 62 ms 209.85.241.246
11 174 ms 59 ms 59 ms 72.14.234.8
12 205 ms 60 ms 58 ms 209.85.250.147
13 225 ms 61 ms 64 ms 108.170.244.1
14 * 71 ms 63 ms 172.217.116.7
15 59 ms 58 ms 59 ms 172.217.116.178
16 61 ms 58 ms 62 ms 136.115.231.242

[shaw-tony]

@talios @CapnCrunch @Alexey @Flourens @JonahL @mattywaggleburn @Jbegould @Exception @Bergerac82 

Thank you for all the details! Last night, our engineering team normalized the IP routing preferences from before the service interruption. Cloud services for Stadia, xCloud, and Geforce Now should be working as expected. Let me know if it still isn't.

[JonahL]

Looks promising so far. Shows my connection is excellent, and no messages about having an unstable connection. I'll report back if anything changes. 

Thanks so much for looking into this! 

[mattywaggleburn]

@shaw-tony Thanks a million!

[CapnCrunch]

I was hoping for a valentines day miracle... 

@shaw-tony it still doesn't work. 

[Bergerac82]

@shaw-tony I'm back up and running in Rossland, BC.
Been working since yesterday evening, and pretty stable.

[talios]

Seems very close, I use all 3 services and geforce now and xcloud are now working great; Stadia's still the same/having issues though.