Google Stadia Latency in Alberta

Schwaby
Grasshopper


Anyone else in the Calgary region experiencing high latency to Google Stadia servers?  The servers noted below have a latency of 75-80ms, however the same IP's from other ISP's in the same geographic area are about 30-40ms.

This high latency stops the games from playing in 1080P/4K resolution and Stadia displays an error about "Unstable Internet connection".  I see old threads on here about the exact same issue and someone from Shaw was able to investigate.   I have the technical ability and resources to provide any traceroutes, ping tests, etc etc so hopefully someone can help to investigate this with me!

Stadia Server IPs tested:

136.112.70.40
136.112.68.229
136.112.68.230
136.112.73.96
136.112.65.241

Labels (1)
15 Replies

--  have you noticed the "Atmospheric Rivers" that have c...

mdk
Legendary Grand Master

@Schwaby --  have you noticed the "Atmospheric Rivers" that have caused (and will be causing, next Tuesday/Wednesday) multiple wash-outs on BC Highway 5 ("Coquihalla") and the scheduled [preventative] closing of the Hope-Princeton highway, the scheduled [cautionary] closing of BC Highway 3 (Crowsnest) and the massive flooding in Merritt and in Abbotsford?

I wonder how many of Shaw's fiber-optic cables in BC have been damaged by the floods and the land-slides?

I am thinking of Shaw's routes from Edmonton to Vancouver to Seattle and Calgary to Vancouver to Seattle, with a destination on Google's network, in California.

For me, the Shaw fiber-optic cables from Vancouver Island -> Vancouver -> Seattle seem to be functioning normally.

What do you expect Shaw to do? It's been reported that infrastructure recovery in BC may take "months".

P.S. Please don't post the same question in more than one thread.

 

0 Kudos
Reply
Loading...

"What do you expect Shaw to do?"      Provide me the type...

Schwaby
Grasshopper

"What do you expect Shaw to do?"

     Provide me the type of information you noted above.  If washed out fiber is undeniably the issue with increased latency to Stadia's servers I can understand and accept there is a time to repair.   Seems suspicious a ping test from Okotoks vs Medicine Hat has a difference of ~40ms and the service works fine.

0 Kudos
Reply
Loading...

Unfortunately, nobody here and the front line support peo...

rstra
Grand Master

@Schwaby Unfortunately, nobody here and the front line support people are able to help with routing issues. The Shaw outages are local to places like Abbotsford, Merrit, Hope etc. so those issues wouldn’t be causing the problem. You might get lucky if you DM the Shaw people on Twitter, I was able to get help for an issie that nobody else seemed to know how to fix. 

0 Kudos
Reply
Loading...

--   Seems suspicious a ping test from Okotoks vs Medicin...

mdk
Legendary Grand Master

@Schwaby --   Seems suspicious a ping test from Okotoks vs Medicine Hat has a difference of ~40ms and the service works fine.

Shaw has major network points in both Calgary & Edmonton.

Capture.JPG

 

Presumably, Shaw has fiber-optic cables from Calgary to nearby Okotoks.

But, from Medicine Hat, where do Shaw's cables go? West, to Calgary? North and then west to Edmonton?

Could one of the "hops" be "saturated" with traffic, and thus become "slow" ?

The output from a "trace-route" utility from Medicine Hat to Vancouver (and then Seattle) could be helpful. Try a trace to:  [66.163.68.18] (Shaw's gateway to Washington State, USA), and post the results.

 

 

 

 

 

 

 

 

 

 

0 Kudos
Reply
Loading...

-- from Shaw's "Outages" pages -- a 30-day credit to affe...

mdk
Legendary Grand Master

@rstra -- from Shaw's "Outages" pages -- a 30-day credit to affected customers.

Nov 27 - British Columbia (Fraser Valley) | All Services - Outage (Fix in Progress)

Due to extreme weather and driving conditions in British Columbia, some customers are temporarily without service.
Once weather conditions in the affected areas subside, our local technicians will work to restore services as quickly as possible.
Please note there will be delays in technician visits and equipment shipping.
Our thoughts go out to all those impacted by the extreme weather
and we greatly appreciate your patience during this time.

Live Updates:
11/26/2021 17:46 PT Shaw Internet and Video services in Hope have successfully been restored.
To ensure your connection is working as expected, please power down your modem or TV players for 30 seconds and then plug back in.
Please be aware that customers impacted by this event will receive a 30 day credit on their next invoice.
additional technicians will be on the ground in Hope over the next week to support any individual service issues.

0 Kudos
Reply
Loading...

Thanks   Was able to gather what, to me looks pretty conc...

Schwaby
Grasshopper

Thanks @mdk 

Was able to gather what, to me looks pretty conclusive Shaw has either a misconfiguration or major issues in their infrastructure from the Okotoks area.  Tested to a Stadia server presumably in California somewhere.

Output below is from Okotoks:

tracert 136.112.68.229

Tracing route to 229.68.112.136.bc.googleusercontent.com [136.112.68.229]
over a maximum of 30 hops:

1 3 ms * 7 ms 10.0.10.1
2 5 ms 3 ms 4 ms 10.0.60.4
3 15 ms 11 ms 13 ms 70.75.96.1
4 18 ms 12 ms 16 ms rc3no-be134-1.cg.shawcable.net [64.59.133.53]
5 14 ms 15 ms 14 ms 24.244.57.193
6 18 ms 14 ms 15 ms 24.244.60.105
7 17 ms 12 ms 11 ms rc3no-be214.cg.shawcable.net [24.244.57.1]
8 34 ms 36 ms 33 ms rc2nr-be110-1.wp.shawcable.net [66.163.76.58]
9 58 ms 55 ms 54 ms rc3fs-be25.mt.shawcable.net [66.163.76.22]
10 56 ms 52 ms 54 ms 142.250.168.184
11 * * * Request timed out.
12 59 ms 58 ms 55 ms 74.125.244.145
13 57 ms 60 ms 54 ms 74.125.244.146
14 59 ms * * 142.251.61.188
15 75 ms * * 142.251.226.162
16 76 ms 76 ms 77 ms 142.251.64.19
17 76 ms 73 ms 73 ms 108.170.245.113
18 75 ms 82 ms 89 ms 172.217.78.7
19 81 ms 75 ms 82 ms 172.217.78.64
20 80 ms 76 ms 84 ms 229.68.112.136.bc.googleusercontent.com [136.112.68.229]

Trace complete.

ping 136.112.68.229 -n 10

Pinging 136.112.68.229 with 32 bytes of data:
Reply from 136.112.68.229: bytes=32 time=79ms TTL=59
Reply from 136.112.68.229: bytes=32 time=78ms TTL=59
Reply from 136.112.68.229: bytes=32 time=76ms TTL=59
Reply from 136.112.68.229: bytes=32 time=78ms TTL=59
Reply from 136.112.68.229: bytes=32 time=72ms TTL=59
Reply from 136.112.68.229: bytes=32 time=75ms TTL=59
Reply from 136.112.68.229: bytes=32 time=79ms TTL=59
Reply from 136.112.68.229: bytes=32 time=75ms TTL=59
Reply from 136.112.68.229: bytes=32 time=75ms TTL=59
Reply from 136.112.68.229: bytes=32 time=78ms TTL=59

Ping statistics for 136.112.68.229:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 72ms, Maximum = 79ms, Average = 76ms

**********************************************************************************************************

Below Pictures are from Medicine Hat

ping.jpgtracert.jpg

0 Kudos
Reply
Loading...

I'm having the same issue. The routing is completely scre...

Oiltown34
Grasshopper

Screenshot_20211127-225700.png

I'm having the same issue. The routing is completely screwed right now.

0 Kudos
Reply
Loading...

&   --  Shaw has either a misconfiguration or major issue...

mdk
Legendary Grand Master

@Oiltown34  & @Schwaby  --  Shaw has either a misconfiguration or major issues in their infrastructure from the Okotoks area. 

I would bet on "major issue".

Output below is from Okotoks:

tracert 136.112.68.229

Tracing route to 229.68.112.136.bc.googleusercontent.com [136.112.68.229]
over a maximum of 30 hops:

1 3 ms * 7 ms 10.0.10.1
2 5 ms 3 ms 4 ms 10.0.60.4
3 15 ms 11 ms 13 ms 70.75.96.1
4 18 ms 12 ms 16 ms rc3no-be134-1.cg.shawcable.net [64.59.133.53]  --------- Calgary
5 14 ms 15 ms 14 ms 24.244.57.193 
6 18 ms 14 ms 15 ms 24.244.60.105
7 17 ms 12 ms 11 ms rc3no-be214.cg.shawcable.net [24.244.57.1]   -------------- Calgary
8 34 ms 36 ms 33 ms rc2nr-be110-1.wp.shawcable.net [66.163.76.58] ------------- Winnipeg
9 58 ms 55 ms 54 ms rc3fs-be25.mt.shawcable.net [66.163.76.22] ----------------- Montreal
10 56 ms 52 ms 54 ms 142.250.168.184  ----------------  Google

For some reason, the Shaw router in Calgary is preferring to route your packets to Winnipeg, rather than through water-immersed British Columbia to Vancouver to Seattle to California.

My guess is a broken fiber-optic cable somewhere between Banff and Vancouver, due to the many land-slides that have closed all the highways between Greater Vancouver and Hope/Kamloops/Kelowna.

Thus, there could be a "doubling" of traffic on the Calgary <--> Winnipeg hop, and on the Winnipeg <--> Montreal hop.

The vice-premier of BC indicates that it could be "months" for the infrastructure to be repaired -- more than 20 "breaks" just on BC 5 (Coquihalla).

 

 

0 Kudos
Reply
Loading...

Did you ever get your issue sorted out. I've talked to bo...

Oiltown34
Grasshopper

Did you ever get your issue sorted out. I've talked to both both Shaw and stadia and am getting the circle jerk as to where problem is? Thanks

0 Kudos
Reply
Loading...
TALK TO US
We're here to help