<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: This latency is caused by ____ ?</title>
	<atom:link href="http://blogs.law.harvard.edu/doc/2009/06/21/this-latency-is-caused-by-____/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.law.harvard.edu/doc/2009/06/21/this-latency-is-caused-by-____/</link>
	<description>Same old blog, brand new place</description>
	<lastBuildDate>Sat, 28 Nov 2009 21:14:31 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Doc Searls</title>
		<link>http://blogs.law.harvard.edu/doc/2009/06/21/this-latency-is-caused-by-____/comment-page-1/#comment-207827</link>
		<dc:creator>Doc Searls</dc:creator>
		<pubDate>Sun, 06 Sep 2009 17:11:31 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=1729#comment-207827</guid>
		<description>We worked it out by talking with higher-level techs than you&#039;ll reach just by making calls. When you do make the call, navigate past the robots to a human, and then demand speaking to an expert who can run down the problem.

In our case the problem as both a crimped line above our house and something with a gateway farther back within Cox. We found the problem mostly by running traceroutes. 

If you need more help, contact me directly at my firstname AT lastname dot com.</description>
		<content:encoded><![CDATA[<p>We worked it out by talking with higher-level techs than you&#8217;ll reach just by making calls. When you do make the call, navigate past the robots to a human, and then demand speaking to an expert who can run down the problem.</p>
<p>In our case the problem as both a crimped line above our house and something with a gateway farther back within Cox. We found the problem mostly by running traceroutes. </p>
<p>If you need more help, contact me directly at my firstname AT lastname dot com.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mac Bakewell</title>
		<link>http://blogs.law.harvard.edu/doc/2009/06/21/this-latency-is-caused-by-____/comment-page-1/#comment-207769</link>
		<dc:creator>Mac Bakewell</dc:creator>
		<pubDate>Sun, 06 Sep 2009 07:51:36 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=1729#comment-207769</guid>
		<description>Hi Doc,

Any resolution to this yet? I&#039;m on the Mesa in Santa Barbara where there are a lot of City College rentals (i.e. lots of online gamers and video streamers). 

Because of the overload, in June of 08 Cox added a new node to this neighborhood and, for a while, things were very much better. The problem now is not speed but latency. Once locked into a site download speeds exceed 20 Mbps, but every so often, like at least twice an hour, both computers here go into a trance when trying to initiate contact with a new URL. 

My initial thought was DNS, so I flushed the DNS caches and switched DNS servers (from from 4.2.2.3 and 4.2.2.2 to Open DNS 208.67.220.220 and 208.67.222.222). That didn&#039;t help so yesterday I bought a new modem from Cox (a Motorola SB5101 to replace the suspect SB5120). 

My hopes were up for the first hour, which went by without a hiccup, but then, and again all day today, we&#039;re back to the same old tedious business. Sigh. I guess I&#039;ll be calling Cox on Tuesday but meanwhile I&#039;d be grateful to hear how this last thread worked out.</description>
		<content:encoded><![CDATA[<p>Hi Doc,</p>
<p>Any resolution to this yet? I&#8217;m on the Mesa in Santa Barbara where there are a lot of City College rentals (i.e. lots of online gamers and video streamers). </p>
<p>Because of the overload, in June of 08 Cox added a new node to this neighborhood and, for a while, things were very much better. The problem now is not speed but latency. Once locked into a site download speeds exceed 20 Mbps, but every so often, like at least twice an hour, both computers here go into a trance when trying to initiate contact with a new URL. </p>
<p>My initial thought was DNS, so I flushed the DNS caches and switched DNS servers (from from 4.2.2.3 and 4.2.2.2 to Open DNS 208.67.220.220 and 208.67.222.222). That didn&#8217;t help so yesterday I bought a new modem from Cox (a Motorola SB5101 to replace the suspect SB5120). </p>
<p>My hopes were up for the first hour, which went by without a hiccup, but then, and again all day today, we&#8217;re back to the same old tedious business. Sigh. I guess I&#8217;ll be calling Cox on Tuesday but meanwhile I&#8217;d be grateful to hear how this last thread worked out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doc Searls Weblog &#183; What&#8217;s 10,241,704.22kb between ex-friends?</title>
		<link>http://blogs.law.harvard.edu/doc/2009/06/21/this-latency-is-caused-by-____/comment-page-1/#comment-207511</link>
		<dc:creator>Doc Searls Weblog &#183; What&#8217;s 10,241,704.22kb between ex-friends?</dc:creator>
		<pubDate>Sat, 05 Sep 2009 04:52:06 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=1729#comment-207511</guid>
		<description>[...] at my house in Santa Barbara for weeks after I got back there in June. I wrote about that here, here, here, here and here. So I used my Sprint datacard a lot. Far as I knew, it had an unlimited data [...]</description>
		<content:encoded><![CDATA[<p>[...] at my house in Santa Barbara for weeks after I got back there in June. I wrote about that here, here, here, here and here. So I used my Sprint datacard a lot. Far as I knew, it had an unlimited data [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doc Searls</title>
		<link>http://blogs.law.harvard.edu/doc/2009/06/21/this-latency-is-caused-by-____/comment-page-1/#comment-184084</link>
		<dc:creator>Doc Searls</dc:creator>
		<pubDate>Wed, 08 Jul 2009 16:04:02 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=1729#comment-184084</guid>
		<description>Hi Rick.

I&#039;m familiar with Wake Forest. My uncle, a big Wake fan, went to Wake when it was still in Wake. 

Has there been a speed increase lately from your service? I think these problems show up when the carrier upgrades something and it hoses downstream devices -- including their own gateways and such. I think that&#039;s the case here. Certainly my own old gear in the house didn&#039;t help.</description>
		<content:encoded><![CDATA[<p>Hi Rick.</p>
<p>I&#8217;m familiar with Wake Forest. My uncle, a big Wake fan, went to Wake when it was still in Wake. </p>
<p>Has there been a speed increase lately from your service? I think these problems show up when the carrier upgrades something and it hoses downstream devices &#8212; including their own gateways and such. I think that&#8217;s the case here. Certainly my own old gear in the house didn&#8217;t help.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick DeNatale</title>
		<link>http://blogs.law.harvard.edu/doc/2009/06/21/this-latency-is-caused-by-____/comment-page-1/#comment-183989</link>
		<dc:creator>Rick DeNatale</dc:creator>
		<pubDate>Wed, 08 Jul 2009 04:39:12 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=1729#comment-183989</guid>
		<description>I&#039;m interested in this thread myself.

For the past week or so, I&#039;ve been seeing VERY intermittent problems similar to yours Doc.

Several times a day, ping times to say google.com go up to 4000ms or higher, traceroutes never complete.  Then things go back to normal.  It&#039;s so intermittent that I haven&#039;t been able to rule out my router, but it does SOMETIMES happen with a direct laptop to model connection.

In my case this is a DSL connection. I&#039;m in Wake Forest, NC (Raleigh neighbor, not Winston-Salem which is where Wake Forest University moved in the 1950s), and my isp/telco is WindStream.</description>
		<content:encoded><![CDATA[<p>I&#8217;m interested in this thread myself.</p>
<p>For the past week or so, I&#8217;ve been seeing VERY intermittent problems similar to yours Doc.</p>
<p>Several times a day, ping times to say&nbsp;<a href="http://google.com" title="http://google. " target="_blank">google.com</a> go up to 4000ms or higher, traceroutes never complete.  Then things go back to normal.  It&#8217;s so intermittent that I haven&#8217;t been able to rule out my router, but it does SOMETIMES happen with a direct laptop to model connection.</p>
<p>In my case this is a DSL connection. I&#8217;m in Wake Forest, NC (Raleigh neighbor, not Winston-Salem which is where Wake Forest University moved in the 1950s), and my isp/telco is WindStream.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Life in Cox tech support hell &#124; dv8-designs</title>
		<link>http://blogs.law.harvard.edu/doc/2009/06/21/this-latency-is-caused-by-____/comment-page-1/#comment-182527</link>
		<dc:creator>Life in Cox tech support hell &#124; dv8-designs</dc:creator>
		<pubDate>Sat, 27 Jun 2009 05:42:29 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=1729#comment-182527</guid>
		<description>[...] symptoms are what they were when I first blogged the problem on June 21, and again when I posted a follow-up on June 24. That was when the Cox service guy [...]</description>
		<content:encoded><![CDATA[<p>[...] symptoms are what they were when I first blogged the problem on June 21, and again when I posted a follow-up on June 24. That was when the Cox service guy [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doc Searls Weblog &#183; Life in Cox tech support hell</title>
		<link>http://blogs.law.harvard.edu/doc/2009/06/21/this-latency-is-caused-by-____/comment-page-1/#comment-182521</link>
		<dc:creator>Doc Searls Weblog &#183; Life in Cox tech support hell</dc:creator>
		<pubDate>Sat, 27 Jun 2009 05:15:57 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=1729#comment-182521</guid>
		<description>[...] symptoms are what they were when I first blogged the problem on June 21, and again when I posted a follow-up on June 24. That was when the Cox service guy [...]</description>
		<content:encoded><![CDATA[<p>[...] symptoms are what they were when I first blogged the problem on June 21, and again when I posted a follow-up on June 24. That was when the Cox service guy [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doc Searls</title>
		<link>http://blogs.law.harvard.edu/doc/2009/06/21/this-latency-is-caused-by-____/comment-page-1/#comment-182259</link>
		<dc:creator>Doc Searls</dc:creator>
		<pubDate>Thu, 25 Jun 2009 16:57:34 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=1729#comment-182259</guid>
		<description>I&#039;d like to hear more, Chip. The key will be keeping service competitors in business and free to innovate, while also preventing monopolies and duopolies from coasting on their captives. I worry that ther Obama administration, to prevent the latter, may foreclose on the former.

I also think the Net needs to be built out increasingly from the edges in, rather than the centers out. And that we stay open to the inevitable improvements in the Net itself.

Absent a generally agreed-upon understanding of what the Net is, all the above will be hard to pull off.</description>
		<content:encoded><![CDATA[<p>I&#8217;d like to hear more, Chip. The key will be keeping service competitors in business and free to innovate, while also preventing monopolies and duopolies from coasting on their captives. I worry that ther Obama administration, to prevent the latter, may foreclose on the former.</p>
<p>I also think the Net needs to be built out increasingly from the edges in, rather than the centers out. And that we stay open to the inevitable improvements in the Net itself.</p>
<p>Absent a generally agreed-upon understanding of what the Net is, all the above will be hard to pull off.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chip</title>
		<link>http://blogs.law.harvard.edu/doc/2009/06/21/this-latency-is-caused-by-____/comment-page-1/#comment-182234</link>
		<dc:creator>Chip</dc:creator>
		<pubDate>Thu, 25 Jun 2009 13:48:49 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=1729#comment-182234</guid>
		<description>Spent yesterday morning in meeting on broadband and Federal Funding for rural access

Very interesting stuff pending - mix of fiber and wifi with totally open (IP structure) system, nice mesh and redundancy options.</description>
		<content:encoded><![CDATA[<p>Spent yesterday morning in meeting on broadband and Federal Funding for rural access</p>
<p>Very interesting stuff pending &#8211; mix of fiber and wifi with totally open (IP structure) system, nice mesh and redundancy options.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Warot</title>
		<link>http://blogs.law.harvard.edu/doc/2009/06/21/this-latency-is-caused-by-____/comment-page-1/#comment-182119</link>
		<dc:creator>Mike Warot</dc:creator>
		<pubDate>Wed, 24 Jun 2009 11:16:20 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=1729#comment-182119</guid>
		<description>Your latency is caused by one of &lt;a href=&quot;http://mikewarot.blogspot.com/2009/06/3-tipping-points.html&quot; rel=&quot;nofollow&quot;&gt;the three unsolved tipping points&lt;/a&gt; of the internet.... the lack of mesh networking. One node should not kill the internet, ever.</description>
		<content:encoded><![CDATA[<p>Your latency is caused by one of <a href="http://mikewarot.blogspot.com/2009/06/3-tipping-points.html" rel="nofollow">the three unsolved tipping points</a> of the internet&#8230;. the lack of mesh networking. One node should not kill the internet, ever.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
