<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>High Latency and online Chat&#x27;s refusal to acknowledge a prob in Comcast HSI</title>
<link>http://www.dslreports.com/forum/r22593677</link>
<description></description>
<language>en</language>
<pubDate>Sat, 05 Dec 2009 08:50:10 EDT</pubDate>
<lastBuildDate>Sat, 05 Dec 2009 08:50:10 EDT</lastBuildDate>

<item>
<title>Re: High Latency and online Chat&#x27;s refusal to acknowledge a prob</title>
<link>http://www.dslreports.com/forum/remark,22599800</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : <div class="bquote"><small>said by  EG <A HREF="/useremail/u/1414214"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A> :</small><br><br><div class="bquote"><small>said by Captain456  :</small><br><br>Yep, the latency starts after Comcast handed the traffic to ATT.  </div>W.I.W., it appears that CC handed the traffic to Tata/Teleglobe, which then handed the traffic to AT&T.<br> </div>Funny you call me on that, it was even said before I made that post. So yea....]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22599800</guid>
<pubDate>Tue, 23 Jun 2009 20:52:31 EDT</pubDate>
</item>

<item>
<title>Re: High Latency and online Chat&#x27;s refusal to acknowledge a prob</title>
<link>http://www.dslreports.com/forum/remark,22599176</link>
<description><![CDATA[<A HREF="/useremail/u/1414214"><b>EG</b></A> : <div class="bquote"><small>said by Captain456 :</small><br><br>Yep, the latency starts after Comcast handed the traffic to ATT.  </div>W.I.W., it appears that CC handed the traffic to Tata/Teleglobe, which then handed the traffic to AT&T.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22599176</guid>
<pubDate>Tue, 23 Jun 2009 18:52:11 EDT</pubDate>
</item>

<item>
<title>Re: High Latency and online Chat&#x27;s refusal to acknowledge a prob</title>
<link>http://www.dslreports.com/forum/remark,22598554</link>
<description><![CDATA[<A HREF="/useremail/u/314530"><b>NormanS</b></A> : <div class="bquote"><small>said by  koshoka <A HREF="/useremail/u/1418272"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A> :</small><br><br>No matter the problem, it's Comcast's fault.<br> </div>It's their use of Sandvine!  :D<br><br>(For those who take things too literally, that is supposed to be hyperbolic humor, not truth. Based on the controversy over Comcast's former use of Sandvine to throttle BT.)<br><small>--<br>Norman<br>~Oh Lord, why have you come<br>~To Konnyu, with the Lion and the Drum</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22598554</guid>
<pubDate>Tue, 23 Jun 2009 17:02:15 EDT</pubDate>
</item>

<item>
<title>Re: High Latency and online Chat&#x27;s refusal to acknowledge a prob</title>
<link>http://www.dslreports.com/forum/remark,22596349</link>
<description><![CDATA[<A HREF="/useremail/u/1418272"><b>koshoka</b></A> : No matter the problem, it's Comcast's fault.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22596349</guid>
<pubDate>Tue, 23 Jun 2009 11:32:34 EDT</pubDate>
</item>

<item>
<title>Re: High Latency and online Chat&#x27;s refusal to acknowledge a prob</title>
<link>http://www.dslreports.com/forum/remark,22595939</link>
<description><![CDATA[<A HREF="/useremail/u/1171845"><b>JSRoman</b></A> : So I guess the Comcast rep. didn't acknowledge a problem for a reason. Imagine that. <br><small>--<br>&raquo;<A HREF="http://www.seabee.navy.mil" >www.seabee.navy.mil</A></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22595939</guid>
<pubDate>Tue, 23 Jun 2009 10:17:57 EDT</pubDate>
</item>

<item>
<title>Re: High Latency and online Chat&#x27;s refusal to acknowledge a prob</title>
<link>http://www.dslreports.com/forum/remark,22595795</link>
<description><![CDATA[<A HREF="/useremail/u/1364611"><b>Xyc</b></A> : It seems like AT&T is still having issues with traffic engineering since Comcast stopped using AT&T for transit about a year ago. AT&T went from having Comcast's not-insubstantial traffic entering their network from a couple of routers per Comcast market (several hundred routers in total?) to receiving it from a limited number of peering points where they already had a lot of traffic coming in from peers like L3 and Tata. Sort of like switching a showerhead from normal to massage mode. :)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22595795</guid>
<pubDate>Tue, 23 Jun 2009 09:49:32 EDT</pubDate>
</item>

<item>
<title>Re: High Latency and online Chat&#x27;s refusal to acknowledge a prob</title>
<link>http://www.dslreports.com/forum/remark,22595509</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Yep, the latency starts after Comcast handed the traffic to ATT. Comcast is not an ATT customer per se here, whoever is hosting the server is an ATT customer. The fault lies with ATT and their customer. It's up to their customer to get it resolved. Nothing Comcast can do.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22595509</guid>
<pubDate>Tue, 23 Jun 2009 08:57:52 EDT</pubDate>
</item>

<item>
<title>Re: High Latency and online Chat&#x27;s refusal to acknowledge a prob</title>
<link>http://www.dslreports.com/forum/remark,22594076</link>
<description><![CDATA[<A HREF="/useremail/u/1414214"><b>EG</b></A> : <div class="bquote"><small>said by  yt <A HREF="/useremail/u/1556203"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A> :</small><br><br>I seem to remember there were problems between AT&T and several other ISPs including Sprint and Verizon.  Blizzard pays AT&T to be their ISP and they need to fix it with them or diversify their connectivity.<br> </div>Agreed ! Single homing for them = ridiculous !!<br><br>Just pointing out that the issue is between those two interconnect points in that particular trace.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22594076</guid>
<pubDate>Mon, 22 Jun 2009 22:13:15 EDT</pubDate>
</item>

<item>
<title>Re: High Latency and online Chat&#x27;s refusal to acknowledge a prob</title>
<link>http://www.dslreports.com/forum/remark,22593954</link>
<description><![CDATA[<A HREF="/useremail/u/1556203"><b>yt</b></A> : <div class="bquote"><small>said by  EG <A HREF="/useremail/u/1414214"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A> :</small><br><br>Actually, this appears to be an issue between Tata and AT&T..<br> </div>I seem to remember there were problems between AT&T and several other ISPs including Sprint and Verizon.  Blizzard pays AT&T to be their ISP and they need to fix it with them or diversify their connectivity.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22593954</guid>
<pubDate>Mon, 22 Jun 2009 21:45:54 EDT</pubDate>
</item>

<item>
<title>Re: High Latency and online Chat&#x27;s refusal to acknowledge a prob</title>
<link>http://www.dslreports.com/forum/remark,22593892</link>
<description><![CDATA[<A HREF="/useremail/u/1414214"><b>EG</b></A> : Actually, this appears to be an issue between Tata and AT&T..]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22593892</guid>
<pubDate>Mon, 22 Jun 2009 21:36:52 EDT</pubDate>
</item>

<item>
<title>Re: High Latency and online Chat&#x27;s refusal to acknowledge a prob</title>
<link>http://www.dslreports.com/forum/remark,22593854</link>
<description><![CDATA[<A HREF="/useremail/u/1031014"><b>JeffinSmyrna</b></A> : Thanks for the input all.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22593854</guid>
<pubDate>Mon, 22 Jun 2009 21:32:05 EDT</pubDate>
</item>

<item>
<title>Re: High Latency and online Chat&#x27;s refusal to acknowledge a prob</title>
<link>http://www.dslreports.com/forum/remark,22593823</link>
<description><![CDATA[<A HREF="/useremail/u/1556203"><b>yt</b></A> : <div class="bquote"><small>said by  JeffinSmyrna <A HREF="/useremail/u/1031014"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>  :</small><br><br>Actually Comcast aknowledged a routing issue on their end a couple of days ago (on their forums).  They did some re-routing to the WoW servers. Im thinking this is the same issue.<br> </div>I doubt it.  Given Blizzard only has 1 ISP and the WoW forums are showing problems with many different ISPs (not just Comcast), I think the fix is really Blizzard's to address.  The first thing a network engineer does is multi-home vs. putting all your gaming eggs in one (not so great) basket.  I would think a gaming company that has millions of online customers would use more than 1 ISP.  How do you route around issues if you only have AT&T?<br><br>That said, you should try a realm closer to you... say Dallas.<br><br>&raquo;<A HREF="http://www.wowwiki.com/US_realm_list_by_datacenter" >www.wowwiki.com/US_realm_list_by_datacenter</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22593823</guid>
<pubDate>Mon, 22 Jun 2009 21:26:32 EDT</pubDate>
</item>

<item>
<title>Re: High Latency and online Chat&#x27;s refusal to acknowledge a prob</title>
<link>http://www.dslreports.com/forum/remark,22593800</link>
<description><![CDATA[<A HREF="/useremail/u/1517701"><b>beachintech</b></A> : It's not. Everything on comcasts network and their initial link to ATT is fine. This is an ATT issue inside their own network.<br><br>Time to contact blizzard and have them work on it.<br><small>--<br>Tech at the Beach.</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22593800</guid>
<pubDate>Mon, 22 Jun 2009 21:21:45 EDT</pubDate>
</item>

<item>
<title>Re: High Latency and online Chat&#x27;s refusal to acknowledge a prob</title>
<link>http://www.dslreports.com/forum/remark,22593797</link>
<description><![CDATA[<A HREF="/useremail/u/1031014"><b>JeffinSmyrna</b></A> : Actually Comcast aknowledged a routing issue on their end a couple of days ago (on their forums).  They did some re-routing to the WoW servers. Im thinking this is the same issue.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22593797</guid>
<pubDate>Mon, 22 Jun 2009 21:21:00 EDT</pubDate>
</item>

<item>
<title>Re: High Latency and online Chat&#x27;s refusal to acknowledge a prob</title>
<link>http://www.dslreports.com/forum/remark,22593791</link>
<description><![CDATA[<A HREF="/useremail/u/1556203"><b>yt</b></A> : <div class="bquote"><small>said by  beachintech <A HREF="/useremail/u/1517701"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A> :</small><br><br>The problem looks to be with ATT. Not something comcast can really fix. Everything on Comcasts ibone and such are fine. <br> </div>QFT - This looks like an issue that your Game provider should address with their ISP.  Hopefully they have more than 1 ISP and can route around AT&T isssues (which appear to be growing)<br><br>You may also try and use a Game server closer to you.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22593791</guid>
<pubDate>Mon, 22 Jun 2009 21:18:59 EDT</pubDate>
</item>

<item>
<title>Re: High Latency and online Chat&#x27;s refusal to acknowledge a prob</title>
<link>http://www.dslreports.com/forum/remark,22593769</link>
<description><![CDATA[<A HREF="/useremail/u/1517701"><b>beachintech</b></A> : The problem looks to be with ATT. Not something comcast can really fix. Everything on Comcasts ibone and such are fine. <br><br>Your hop 9, 192.205.35.57, is an ATT edge router, which has a good link with comcast.<br><small>--<br>Tech at the Beach.</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22593769</guid>
<pubDate>Mon, 22 Jun 2009 21:15:47 EDT</pubDate>
</item>

<item>
<title>High Latency and online Chat&#x27;s refusal to acknowledge a prob</title>
<link>http://www.dslreports.com/forum/remark,22593677</link>
<description><![CDATA[<A HREF="/useremail/u/1031014"><b>JeffinSmyrna</b></A> : I play Wow and for the last week, latency has been HORRIBLE. I tried to talk to online chat support but it went no where fast. Can you assist? Here is a copy of the transcript:<br><br>chat id : 9bc5dd41-1f63-4e64-b255-4956b0f82f8f<br>Problem : High latency<br>Jeff > High latency<br>Shera.26087 > Hi, Jeff!<br>Shera.26087 > I am happy to have a chance to assist you with your concern. How are you doing today?<br>Jeff_ > Im an online gamer and the past week I have noticed that my latency to the game servers have made it so my gaming is unplayable.<br>Shera.26087 > I am really sorry to know that.<br>Shera.26087 > Jeff, have you tried to update your system when you experienced high latencies?<br>Jeff_ > update my system?<br>Jeff_ > Tracing route to 206.16.147.36 over a maximum of 30 hops<br><br>  1     *        *        *     Request timed out.<br>  2     9 ms     9 ms     9 ms  68.85.135.25<br>  3    11 ms    11 ms    12 ms  te-8-2-ar01.nashville.tn.nash.comcast.net [68.85<br>.174.17]<br>  4    10 ms    11 ms    14 ms  te-9-2-ur01.goodslettvll.tn.nash.comcast.net [68<br>.86.148.61]<br>  5    14 ms    14 ms    14 ms  te-0-3-0-1-cr01.nashville.tn.ibone.comcast.net [<br>68.86.90.133]<br>  6    30 ms    31 ms    31 ms  pos-1-8-0-0-cr01.dallas.tx.ibone.comcast.net [68<br>.86.85.17]<br>  7    34 ms    35 ms    35 ms  vlan549.icore2.dtx-dallas.as6453.net [206.82.142<br>.5]<br>  8    40 ms    35 ms    35 ms  vlan6.icore1.dtx-dallas.as6453.net [209.58.47.13<br>]<br>  9    28 ms    28 ms    29 ms  192.205.35.57<br> 10   178 ms   174 ms   180 ms  cr2.dlstx.ip.att.net [12.122.138.110]<br> 11   174 ms   181 ms   173 ms  cr1.attga.ip.att.net [12.122.28.173]<br> 12   182 ms   173 ms   175 ms  cr2.wswdc.ip.att.net [12.122.1.174]<br> 13   178 ms   172 ms   172 ms  cr2<br>Jeff_ > .n54ny.ip.att.net [12.122.3.37]<br> 14   181 ms   172 ms   176 ms  cr1.cb1ma.ip.att.net [12.122.31.126]<br> 15   173 ms   173 ms   174 ms  gar5.cb1ma.ip.att.net [12.122.145.33]<br> 16   180 ms   203 ms   199 ms  12-122-254-14.attens.net [12.122.254.14]<br> 17   174 ms   175 ms   174 ms  mdf001c7613r0003-gig-10-1.bos1.attens.net [12.13<br>0.0.170]<br> 18     *        *        *     Request timed out.<br> 19     *        *        *     Request timed out.<br> 20     *        *        *     Request timed out.<br> 21     *        *        *     Request timed out.<br> 22     *        *        *     Request timed out.<br> 23     *        *        *     Request timed out.<br> 24     *        *        *     Request timed out.<br> 25     *        *        *     Request timed out.<br> 26     *        *        *     Request timed out.<br> 27     *        *        *     Request timed out.<br> 28     *        *        *     Request timed out.<br> 29     *        *        *     Request timed out.<br> 30     *        *        *     Requ<br>Jeff_ > est timed out.<br><br>Trace complete.<br>Jeff_ > there seems to be a problem with the peering arrangement from the Dallas, TX  hop to ATT<br>Shera.26087 > May I please know how you got those ping results.<br>Shera.26087 > To better assist you, may I please have your account number?<br>Jeff_ > I got my results from doing a tracert.<br>Shera.26087 > Thank you.<br>Jeff_ > my account number is xxxxxxxxxxxx<br>Shera.26087 > I will also run a health check on your system, Jeff.<br>Shera.26087 > Thank you so much.<br>Shera.26087 > Please give me a minute or two, as I pull up your account information.<br>Jeff_ > ok.. as you can cleary see, its not my system<br>Shera.26087 > Thank you for waiting. I really appreciate your patience.<br>Shera.26087 > Jeff, please also try to run a speed test on your internet connection.<br>Shera.26087 > Thank you.<br>Shera.26087 > To run a speed test, please click this link: &raquo;<A HREF="http://www.2wire.com" >www.2wire.com</A> then choose "speed meter" link located on top.<br>Jeff_ > Shera, while I appreciate your help, this isnt a speed issue.. its a latency issue<br>Jeff_ > Speed Meter<br><br>Your current bandwidth reading is<br>5.55 Mbps <br>Shera.26087 > I understand, Jeff.<br>Shera.26087 > Thank you.<br>Shera.26087 > The result of the PING test on your system.<br>Shera.26087 > Pinging 00:22:2d:14:87:2e<br>--- 96.70.158.5 ping statistics ---<br>32 bytes from 96.70.158.5 (96.70.158.5): icmp_seq=1 time=42.74 ms<br>32 bytes from 96.70.158.5 (96.70.158.5): icmp_seq=2 time=47.39 ms<br>32 bytes from 96.70.158.5 (96.70.158.5): icmp_seq=3 time=47.73 ms<br>32 bytes from 96.70.158.5 (96.70.158.5): icmp_seq=4 time=42.86 ms<br>32 bytes from 96.70.158.5 (96.70.158.5): icmp_seq=5 time=49.38 ms<br>32 bytes from 96.70.158.5 (96.70.158.5): icmp_seq=6 time=46.02 ms<br>32 bytes from 96.70.158.5 (96.70.158.5): icmp_seq=7 time=42.90 ms<br>32 bytes from 96.70.158.5 (96.70.158.5): icmp_seq=8 time=42.91 ms<br>32 bytes from 96.70.158.5 (96.70.158.5): icmp_seq=9 time=40.62 ms<br>32 bytes from 96.70.158.5 (96.70.158.5): icmp_seq=10 time=47.46 ms<br>10 packets transmitted, 10 packets received, 0% packet loss, time 450.01 ms<br>rtt min/avg/max = 40.62/45.00/49.38 ms<br>Shera.26087 > I can not see an issue here.<br>Jeff_ > your kidding, right?<br>Shera.26087 > I think you are just having an issue if you are playing online.<br>Jeff_ > wow.. you have no clue<br>Shera.26087 > It seems that you have left the chat room. Unfortunately, I am unable to reopen this chat window. Please feel free to chat back and one of my colleagues will be happy to assist you.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22593677</guid>
<pubDate>Mon, 22 Jun 2009 20:59:51 EDT</pubDate>
</item>

</channel>
</rss>
