Routing to AWS, google play etc

[JasonD2]

Hello,  I have a XB7 router which I received around Jan 1st.   Ever since I have had nothing but problems with 'certain' connections, and it's always the same ones.  I don't think it's the router itself, but it ALL started happening when I changed over.  The person on the phone had to do something to 'apply' my new router, I wonder if it's something related to that.  Either way, the issue appears to be around the backend services/connection for my account.

Here's some examples that no longer work on my home wifi:

• Amazon Videos embedded in reviews
• Amazon Music/Prime Video
• Google Play Games can no longer log me in

So, what I currently do is disconnect from my wifi and use my cell data to use these services. I shouldn't need to do this. If I'm on my PC, I just can't access them.

I am running in Bridged mode, with the same router that I had before the XB7 'upgrade'.  So I decided to turn on logging, and I can see that the route is choking on the AWS ip lookup.  So in this case I opened Amazon music, the UI is stalled, I pulled the IP it requested from my router logs, and did a tracert on it:

Tracing route to ec2-54-200-116-116.us-west-2.compute.amazonaws.com [54.200.116.116]
over a maximum of 30 hops:

  1    <1 ms     3 ms    <1 ms  <My Machine> [192.168.1.1]
  2     9 ms    10 ms     9 ms  <Removed>
  3     8 ms     8 ms    13 ms  rc1st-be111-1.vc.shawcable.net [64.59.147.181]
  4    10 ms    10 ms     9 ms  24.244.60.1
  5    30 ms    10 ms     *     24.244.59.181
  6     9 ms    10 ms    10 ms  rc1st-be214.vc.shawcable.net [24.244.58.65]
  7    15 ms    14 ms    18 ms  rc2wt-be50-1.wa.shawcable.net [66.163.70.106]
  8    14 ms    18 ms    18 ms  99.82.176.42
  9    14 ms    19 ms    14 ms  52.95.53.209
 10    14 ms    14 ms    14 ms  52.95.53.129
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18    21 ms    23 ms    21 ms  108.166.228.44
 19     *        *        *     Request timed out.
 20    23 ms    22 ms    23 ms  108.166.228.37
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

I haven't bothered tracing down all the owners for those ip addresses, but as you can see, it's not blocked on my end.  Any suggestions on what to do next?  If I call the support they're going to make me reboot etc, which I've done dozens of times etc.  It's just going to be a waste of my time.

[rstra]

@JasonD2  Support will likely be limited because you are in bridge mode. Try taking the XB7 out of bridge mode, bypass your router and see what happens.

[JasonD2]

Oh one more piece of info: I cannot even perform the https://speedtest.shaw.ca/  it fails to make a connection to upload after the download completes.

[JasonD2]

sure I'll do that as soon as I can.

[rstra]

@JasonD2  Speedtest is also hosted by AWS, I wonder if your Shaw ip address is being blocked by AWS?

[JasonD2]

If I turn off the bridge, pop on that wifi and it appears I can access things again.  Set it back to bridged, and cannot access aws again.

Since you mentioned the ip, I'll released/renewed the IP via the router. and it seems to be ok for now.  I'll post back if things go funny again.  I'm not sure why that ip would have had an issue.

[mdk]

@JasonD2 -- there is no "law" on the Internet that routers MUST respond to the special "traceroute" packets.

So, you see: 

17 * * * Request timed out.
18 21 ms 23 ms 21 ms 108.166.228.44
19 * * * Request timed out.
20 23 ms 22 ms 23 ms 108.166.228.37

Your "traceroute" packets DO progress toward the IP-address of the AWS.

P.S. The "Shaw Speed Test" servers are NOT hosted by AWS:

Name: speedtest.glb.shawcable.net
Addresses: 64.59.136.151 , 64.59.134.43
Aliases: speedtest.shaw.ca

Physically, those servers seem to be in Victoria, Vancouver, Kelowna, and other locations.

P.S. Use www.arin.net/whois to quickly find the owner of an IP-address.

[rstra]

@mdk  That Shaw webpage is just a link to the Ookla Speedtest servers.

[JasonD2]

Lasted 6 hours or so, cannot connect to those services again.  Release/Renew brings it all back (does not reboot the router).

I'll have to try using the gateway router for a longer period of time.

[mdk]

@rstra -- That Shaw webpage is just a link to the Ookla Speedtest servers.

Yes, the software at the various physical locations, namely:

1. Victoria
2. Vancouver
3. Kelowna
4. Calgary
5. Edmonton
6. Winnipeg

The Shaw Speedtest allows one to choose from the above physical locations.

Try each of the sites, to observe that the best numbers come from choosing the nearest city to your physical location.