Comcast XFINITY → [Connectivity] Google Issues

Since Tuesday I've been having problems accessing Google services on my computer and ipad. Also having the same issue at work. Home is NE Miami-Dade county and work is SE Broward county. I believe they are on different systems.

Specifically, Google pages take 10-20 seconds to come up half the time and Youtube is experiencing a lot of buffering on videos. All other sites are working normally. Speed test is normal. 125/25

Comcast phone agent scheduled a tech but I don't really see what that would do as it's either a problem further up the network or with Google. Any suggestions?

What's a tracert look like ?

what DNS? any proxy/ VPN involved? powercycled it? direct to modem? is the google link :to Google: ? or a specific IP?

I'm using comcasts dns 75.75.75.75

Power cycled multiple times.

Direct to google.

Do some traces.
I live in central FL and for last 6 months have had issues with google services and comcast.
Sometimes google.com gets 30 ms latency, most times near 200. Same for youtube and others too.
Far as I can tell the issue is actually on Google's side in my trace the latency issue happens after it gets on google network, but when I contacted google fiber (only way to find a way to contact someone lol) they told me to post it in the google forum for the community to assist me... fools..

The real issue is some bad route exist but it's on the google network. They have a butt load of different IP's though so if you can find a DNS provider that happens to not hit the bad ones your issues will improve lol.

Again, provide a tracert.

I was on the ipad. running them now. waiting for them to finish

Also, no extra router. Using the DCT3941 directly.

Tracing route to youtube-ui.l.google.com [2607:f8b0:4008:80a::200e]
over a maximum of 30 hops:

1 4 ms 6 ms 7 ms
2 * * 38 ms
3 19 ms 12 ms 14 ms xe-1-1-1-32767-sur04.northdade.fl.pompano.comcas
t.net [2001:558:72:103::1]
4 15 ms 19 ms 15 ms te-0-3-0-16-ar01.pompanobeach.fl.pompano.comcast
.net [2001:558:70:14d::1]
5 16 ms 19 ms 12 ms be-10-ar01.northdade.fl.pompano.comcast.net [200
1:558:70:d6::1]
6 18 ms * 25 ms be-20214-cr01.miami.fl.ibone.comcast.net [2001:5
58:0:f6b3::1]
7 * * * Request timed out.
8 * * * Request timed out.
9 19 ms 25 ms 15 ms 2001:4860::1:0:245b
10 * * * Request timed out.
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 22 ms 31 ms 16 ms mia07s34-in-x0e.1e100.net [2607:f8b0:4008:80a::2
00e]

Trace complete.

Tracing route to www.google.com [2607:f8b0:4008:80a::2004]
over a maximum of 30 hops:

1 5 ms 3 ms 4 ms
2 14 ms 13 ms *
3 12 ms 16 ms 16 ms xe-1-1-1-32767-sur04.northdade.fl.pompano.comcas
t.net [2001:558:72:103::1]
4 15 ms 19 ms 14 ms te-0-3-0-15-ar01.pompanobeach.fl.pompano.comcast
.net [2001:558:70:125::1]
5 16 ms 25 ms 17 ms be-8-ar01.northdade.fl.pompano.comcast.net [2001
:558:70:cc::1]
6 * * 18 ms be-20214-cr01.miami.fl.ibone.comcast.net [2001:5
58:0:f6b3::1]
7 * * 15 ms 2001:558:0:f612::2
8 * * * Request timed out.
9 27 ms 28 ms 18 ms 2001:4860::1:0:245b
10 * * * Request timed out.
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 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * 15 ms * mia07s34-in-x04.1e100.net [2607:f8b0:4008:80a::2
004]
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 17 ms * * mia07s34-in-x04.1e100.net [2607:f8b0:4008:80a::2
004]
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 18 ms * * mia07s34-in-x04.1e100.net [2607:f8b0:4008:80a::2
004]

Trace complete.

almost looks like some sort of routing loop at Googles address of 2607:f8b0:4008:80a::2
004, packets repeatedly hit that until the TTL expires.

What happend during a v4 trace?

Yeah that looks ugly. A truck roll wouldn't help you at all. Not sure who you would need to contact to help get it resolved. netcool may have a suggestion.

Me neither, but probably no one from comcast. Ive heard that contacting Google for technical issues can be a nightmare....

the direct guys
or
netcool would probably be interested maybe could forward something to somebody.

Yeah!, Yeah! that's the ticket.

I'll cancel the appointment. No need to waste the tech's time.

What's their v4 address so I can run a trace?

Thanks will post over there. I'll let you all know what happens

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

1 3 ms 4 ms 4 ms 192.168.0.1
2 19 ms 14 ms 9 ms 96.120.37.181
3 14 ms 14 ms 14 ms xe-1-1-1-0-sur04.northdade.fl.pompano.comcast.ne
t [68.86.160.141]
4 14 ms 13 ms 19 ms xe-11-0-3-0-sur05.northdade.fl.pompano.comcast.n
et [69.139.182.141]
5 27 ms 11 ms 13 ms te-0-3-0-12-ar01.northdade.fl.pompano.comcast.ne
t [68.85.127.69]
6 18 ms 14 ms 14 ms be-20214-cr01.miami.fl.ibone.comcast.net [68.86.
90.205]
7 14 ms 16 ms 19 ms 68.86.82.18
8 14 ms 12 ms 14 ms as15169-1-c.nota.fl.ibone.comcast.net [23.30.206
.118]
9 12 ms 23 ms 18 ms 209.85.253.118
10 13 ms 16 ms 19 ms 72.14.233.235
11 12 ms 14 ms 12 ms mia07s25-in-f110.1e100.net [216.58.219.110]

Trace complete.

Looks much better. I disabled ipv6 and interestingly it fixed the problem. When I turn ipv6 back on the problem reappears. Was able to repeat this on both of my computers.

Is there a way to disable ipv6 on ios 9?

I don't, but couldn't you just disable IPv6 on your router/gateway?

The gateway let's you disable stateful but not stateless. Apple seems to pull from the stateless setting. I asked Comcast phone support and they have no way to disable the stateless setting

Darn. (Another reason why I prefer standalone routers to ISP-controlled gateways, btw.)

It doesn't look good on turning it off in IOS9. Some quick googling shows lots of articles saying that Apple is really pushing for IPv6 in iOS9, and requiring all apps to support it.... perhaps after a jail break?

Yeah that was my luck searching too. Thought someone here would know definitively. Hopefully Direct will have an ability to fix the networking issue causing the underlying problem or reach the counterpart at Google that can fix it.

The problem appears to have corrected itself late Sunday / early Monday before the Direct team had a chance to get involved. Hopefully it won't return.