Can't Access Parts of Google Due to Bad Traceroute

[kingkool68]

Android phones connected to my FiOS router can't download updates from the Google Play Store. I can't stream music from https://play.google.com/music/listen Google Drive syncing doesn't work. Looking at traceroutes it looks like their is a problem routing to cache.google.com (50.38.0.144). No issue if I connect via my mobile network or VPN from my laptop. This has been going on for days how can this get fixed?

via FiOS:

Traceroute has started…
traceroute to 50.38.0.144 (50.38.0.144), 64 hops max, 72 byte packets
1 192.168.1.1 (192.168.1.1) 3.050 ms 1.276 ms 1.004 ms
2 lo0-100.bltmmd-vfttp-303.verizon-gni.net (XXX.XXX.XXX.XXX) 2.223 ms 1.503 ms 2.167 ms
3 b3303.bltmmd-lcr-21.verizon-gni.net (130.81.32.20) 5.263 ms 7.739 ms 3.328 ms
4 * * *
5 * * *
6 0.et-5-3-0.br1.iad8.alter.net (140.222.239.79) 640.112 ms 524.673 ms *
7 192.205.36.137 (192.205.36.137) 10.207 ms 9.846 ms 9.790 ms
8 cr81.wshdc.ip.att.net (12.122.134.150) 9.092 ms 6.419 ms 7.966 ms
9 12.122.135.109 (12.122.135.109) 6.791 ms 6.529 ms 6.101 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 * * *
34 * * *
35 * * *
36 * * *
37 * * *
38 * * *
39 * * *
40 * * *
41 * * *
42 * * *
43 * * *
44 * * *
45 * * *
46 * * *
47 * * *
48 * * *
49 * * *
50 * * *
51 * * *
52 * * *
53 * * *
54 * * *
55 * * *
56 * * *
57 * * *
58 * * *
59 * * *
60 * * *
61 * * *

via T-Mobile LTE connection:

Traceroute has started…
traceroute to 50.38.0.144 (50.38.0.144), 64 hops max, 72 byte packets
1 192.168.43.1 (192.168.43.1) 2.903 ms 3.197 ms 2.741 ms
2 255.0.0.0 (255.0.0.0) 33.979 ms 33.411 ms 39.785 ms
3 * * *
4 255.0.0.1 (255.0.0.1) 68.215 ms 42.777 ms 25.186 ms
5 * * *
6 10.168.197.235 (10.168.197.235) 38.439 ms 38.907 ms 43.004 ms
7 10.164.72.172 (10.164.72.172) 27.742 ms 36.277 ms 42.101 ms
8 10.164.165.67 (10.164.165.67) 30.253 ms 34.647 ms 31.187 ms
9 xe-2-1-0.er2.dca2.us.above.net (208.185.145.133) 30.841 ms 47.383 ms 35.051 ms
10 ae6.cr1.dca2.us.zip.zayo.com (64.125.20.117) 32.032 ms 41.495 ms 32.454 ms
11 ae27.cs1.dca2.us.eth.zayo.com (64.125.30.246) 63.311 ms 66.215 ms 52.908 ms
12 * * *
13 ae3.cs1.ord2.us.eth.zayo.com (64.125.29.209) 82.189 ms 56.401 ms 51.577 ms
14 ae27.cr1.ord2.us.zip.zayo.com (64.125.30.243) 56.314 ms 62.550 ms 51.924 ms
15 ae15.er1.ord7.us.zip.zayo.com (64.125.31.85) 50.925 ms 59.846 ms 60.402 ms
16 br01.chcg.il.frontiernet.net (206.223.119.46) 67.551 ms 64.659 ms 56.377 ms
17 ae2---0.cor02.chcg.il.frontiernet.net (74.40.4.141) 107.398 ms 118.679 ms 106.769 ms
18 ae0---0.cor02.enwd.co.frontiernet.net (74.40.5.154) 105.672 ms 111.495 ms 101.360 ms
19 ae6---0.cor01.sttl.wa.frontiernet.net (74.40.2.57) 110.141 ms 109.035 ms 102.086 ms
20 ae1---0.cor02.bvtn.or.frontiernet.net (74.40.1.222) 106.972 ms 105.122 ms 126.581 ms
21 74.40.1.218 (74.40.1.218) 113.326 ms 122.592 ms 107.337 ms
22 cache.google.com (50.38.0.144) 104.486 ms 103.796 ms 97.261 ms

via my VPN connection

Traceroute has started…
traceroute to 50.38.0.144 (50.38.0.144), 64 hops max, 72 byte packets
1 192.168.124.1 (192.168.124.1) 44.816 ms 25.274 ms 28.628 ms
2 10.10.102.1 (10.10.102.1) 27.681 ms 28.171 ms 27.404 ms
3 te0-2-0-10.ccr41.ord01.atlas.cogentco.com (38.88.203.89) 28.885 ms 37.333 ms 29.648 ms
4 be2765.ccr41.ord03.atlas.cogentco.com (154.54.45.18) 33.433 ms 28.245 ms 26.193 ms
5 * * *
6 4.16.38.118 (4.16.38.118) 27.824 ms 27.689 ms 28.671 ms
7 * * *
8 ae14---0.cor02.chcg.il.frontiernet.net (74.40.5.109) 133.539 ms 82.398 ms 90.466 ms
9 ae0---0.cor02.enwd.co.frontiernet.net (74.40.5.154) 82.619 ms 93.833 ms 81.940 ms
10 ae6---0.cor01.sttl.wa.frontiernet.net (74.40.2.57) 82.569 ms 80.799 ms 80.960 ms
11 ae1---0.cor02.bvtn.or.frontiernet.net (74.40.1.222) 83.146 ms 101.481 ms 82.051 ms
12 74.40.1.218 (74.40.1.218) 118.910 ms 111.828 ms 84.100 ms
13 cache.google.com (50.38.0.144) 82.499 ms 83.031 ms 106.903 ms

[CRobGauth]

Seeing as how the issue appears to be past the Verizon network, it may be hard for them to fix it.

I get the same timeouts you are seeing.

I don't have an issue with android phones getting updates.

So not sure where the issue is.