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

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

<channel>
<title>Latency again at 12.244.72.197/198 hops in AT&#x26;T Broadband</title>
<link>http://www.dslreports.com/forum/r3967987</link>
<description></description>
<language>en</language>
<pubDate>Thu, 03 Dec 2009 07:41:05 EDT</pubDate>
<lastBuildDate>Thu, 03 Dec 2009 07:41:05 EDT</lastBuildDate>

<item>
<title>Re: Latency again at 12.244.72.197/198 hops</title>
<link>http://www.dslreports.com/forum/remark,3978340</link>
<description><![CDATA[<A HREF="/useremail/u/274842"><b>DSLTech</b></A> : Doesnt look like a peering problem. We have peering problems here where I work and they don't just happen in the evening during prime time.<br><br>The 12/8 network belongs to AT&T, no? And it would be their responsibility to resolve issues on it.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,3978340</guid>
<pubDate>Mon, 29 Jul 2002 22:19:42 EDT</pubDate>
</item>

<item>
<title>Re: Latency again at 12.244.72.197/198 hops</title>
<link>http://www.dslreports.com/forum/remark,3969604</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Well, I called tonight talked to a 2 tier guy. Im getting horrid pings from my computer to the gateway. They have already sent out a guy to check my lines which he said was ok and was a network problem. Well the ATTBI guy tonight said that this is a cable problem and the technician will have to resolve it somehow.<br><br>They have already swapped out my modem and still the same issue is present. I dont know maybe something is wired right but getting 300 ms 1 hop to my gateway is wrong. At least ATTBI agrees here. Now to see if they fix it.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,3969604</guid>
<pubDate>Mon, 29 Jul 2002 01:44:05 EDT</pubDate>
</item>

<item>
<title>Re: Latency again at 12.244.72.197/198 hops</title>
<link>http://www.dslreports.com/forum/remark,3968437</link>
<description><![CDATA[<A HREF="/useremail/u/465839"><b>deblin</b></A> : Actually, that's a peer/backbone router problem and any ISP would suffer from the same problems, it has nothing to do with cable.<br><br>Glad it's fixed though! :)<br><small>--<br>"I drank what?" -Socrates</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,3968437</guid>
<pubDate>Sun, 28 Jul 2002 23:08:35 EDT</pubDate>
</item>

<item>
<title>Re: Latency again at 12.244.72.197/198 hops</title>
<link>http://www.dslreports.com/forum/remark,3968315</link>
<description><![CDATA[<A HREF="/useremail/u/274842"><b>DSLTech</b></A> : OK its good now. Moody little b*tch.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,3968315</guid>
<pubDate>Sun, 28 Jul 2002 22:54:26 EDT</pubDate>
</item>

<item>
<title>Latency again at 12.244.72.197/198 hops</title>
<link>http://www.dslreports.com/forum/remark,3967987</link>
<description><![CDATA[<A HREF="/useremail/u/274842"><b>DSLTech</b></A> : Here we go again.. seeing prime-time latency on these particular routers: 12.244.72.197 and/or 12.244.72.198 (depending on where you're testing from):<br><br>From work:<br><br>  8   10 ms   10 ms   10 ms  so-6-1-0.gar2.SanJose1.Level3.net [209.247.14.13<br>]<br>  9   10 ms   10 ms   10 ms  pos8-0.core1.SanFrancisco1.Level3.net [209.247.1<br>0.226]<br> 10   10 ms   10 ms   10 ms  ggr1.sffca.ip.att.net [166.90.50.158]<br> 11   10 ms   10 ms   10 ms  gbr4-p50.sffca.ip.att.net [12.123.13.70]<br> 12   10 ms   10 ms   10 ms  gbr2-p100.sffca.ip.att.net [12.122.1.190]<br> 13   10 ms   10 ms   10 ms  gar1-p370.sffca.ip.att.net [12.123.13.61]<br> 14   141 ms   141 ms   140 ms  12.244.72.197<br> 15   141 ms   156 ms   156 ms  12.244.67.6<br> 16   157 ms   140 ms   156 ms  12-233-238-1.client.attbi.com [12.233.238.1]<br><br>Trace complete.<br><br>I guess thats just cable for you. Ugh.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,3967987</guid>
<pubDate>Sun, 28 Jul 2002 22:18:40 EDT</pubDate>
</item>

</channel>
</rss>
