Ever since the ‘Akamai’ Incident, Yahoo Mail hasn’t been the same.
I can ping to it just fine, I just can’t login and read my yahoo mail. When I can it’s really slow. Ever since the Upgrades and the Akamai incident, Yahoo has been really out of whack when accessing from Comcast.
I’m also having issues with Gmail. But atleast gmail Isn’t as bad, just really slow.
ping mail.yahoo.com
PING login.yahoo.akadns.net (216.109.127.60): 56 data bytes
64 bytes from 216.109.127.60: icmp_seq=0 ttl=241 time=18.868 ms
64 bytes from 216.109.127.60: icmp_seq=1 ttl=241 time=20.032 ms
64 bytes from 216.109.127.60: icmp_seq=2 ttl=241 time=18.874 ms
64 bytes from 216.109.127.60: icmp_seq=3 ttl=241 time=20.956 ms
64 bytes from 216.109.127.60: icmp_seq=4 ttl=241 time=19.990 ms
^C
— login.yahoo.akadns.net ping statistics —
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 18.868/19.744/20.956/0.792 ms
4 srp-8-1-ar01.verona.nj.nj01.comcast.net (68.87.47.193) 12.870 ms 9.725 ms
5 pos-7-0-cr01.plainfield.nj.core.comcast.net (68.87.19.253) 9.891 ms 8.937 ms
6 12.118.149.5 (12.118.149.5) 10.761 ms 10.216 ms
7 tbr2-p014001.n54ny.ip.att.net (12.123.3.14) 11.121 ms 19.033 ms
8 ggr2-p390.n54ny.ip.att.net (12.123.3.62) 10.752 ms 11.037 ms
9 so-1-0-0.edge1.NewYork1.Level3.net (4.68.127.5) 10.067 ms 21.489 ms
10 ge-2-1-0.bbr2.NewYork1.Level3.net (64.159.4.149) 9.882 ms 10.297 ms
11 as-1-0.bbr2.Washington1.Level3.net (64.159.1.86) 17.708 ms 18.743 ms
12 ge-7-2.ipcolo2.Washington1.Level3.net (64.159.18.132) 18.758 ms 18.791 ms
13 unknown.Level3.net (166.90.148.10) 18.932 ms 17.489 ms
14 vl49.bas1-m.dcn.yahoo.com (216.109.120.222) 18.643 ms vl33.bas2-m.dcn.yahoo.com (216.109.120.154) 23.350 ms
15 alteon2.124.dcn.yahoo.com (216.109.124.11) 21.772 ms 20.097 ms
Thanks
Matt,
GMail seems OK to me - i'm on a nac.net line.
-- Jonathan
Thanks for reading my message. I clearly stated I was having issues
accessing the site, and not ping or traceroute related. I provided them just
incase you needed them.
And BTW, I'm not the only Comcast user having trouble. It's been about 20
posts from others on DSLREPORTS with the same issue, so its clear there is a
problem and it needs to be resolved.
do you have another channel to email the support aliases for the sites
noted? Perhaps they are unaware of their 'issue' at this time? If you have
then excellent, if you have not remember it's sometimes difficult to see a
user's problem from the server side of the fence 
Just a suggestion, since it appears to be working for me at this time (I
had to create an account, but it all worked well enough from the fUUNET
network atleast, where I see if via level3)
-Chris
Comcast offers toll-free customer assistance for all of its paying
customers. Have you tried contacting them? The number is on your
bill every month.
<rant>
Yes, try calling them. You *might* get through. These days they
seem to hang up on about 1 of 3 customers who call in.
I've been back on their "High Speed Internet" for about 3 months
now and it seems to be getting worse every day. They are either
overselling, or this new wholly-owned network of theirs is built
very wrong.
</rant>
Honestly though.. if you use your home 'Net connection for anything
important, I'd look for an alternative. I routinely have 19ms to my
next hop.. about 4 miles away. I happen to have Verona and
Plainfield directly in front of me as well.. I think it's our area.
cheers,
[...]
do you have another channel to email the support aliases for the
sites noted? Perhaps they are unaware of their 'issue' at this time?
If you have then excellent, if you have not remember it's sometimes
difficult to see a user's problem from the server side of the fence
I'd normally agree that NANOG isn't the best place for airing dirty
laundry concerning one's residential broadband connection, but this is
far more widespread than one might first think, maybe even bordering
on operationally relevant. And of course, the standard support
channels you speak of are less than closed in.
I've spoken to some large-ish content hosts who've been receiving a
slew of support tickets from Comcast customers in the Northern New
Jersey and Philadelphia metro areas, unable to access their sites,
beginning at or around last Friday.
I've done a little digging of my own, and it appears as though there's
some MTU/MSS-related weirdness going on. If anybody from Comcast is
listening, feel free to ping me offline for more details...
-a
I'm pretty sure all I asked was: "did you try emailing yahoo to report a
problem, most likely via some other email provider since you are having
issues with yahoo"
Oh well, perhaps it's just mtu issues 