<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Backbone-News &#187; Nextel</title>
	<atom:link href="http://www.backbone-news.com/tag/nextel/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.backbone-news.com</link>
	<description>Covering Technology, Outages, News and Events</description>
	<lastBuildDate>Fri, 19 Dec 2008 22:25:35 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Sprint-Nextel depeers Cogent (updated)</title>
		<link>http://www.backbone-news.com/2008/10/31/sprint-nextel-depeers-cogent/</link>
		<comments>http://www.backbone-news.com/2008/10/31/sprint-nextel-depeers-cogent/#comments</comments>
		<pubDate>Fri, 31 Oct 2008 14:24:12 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Service Provider]]></category>
		<category><![CDATA[Cogent]]></category>
		<category><![CDATA[Nextel]]></category>
		<category><![CDATA[Peering]]></category>
		<category><![CDATA[Sprint]]></category>

		<guid isPermaLink="false">http://www.backbone-news.com/?p=39</guid>
		<description><![CDATA[ 
What started as with a few messages on several ISP focused mailing-lists has been confirmed by Cogent in a press release today: Sprint-Nextel and Cogent have interrupted their peering connections, and as such customers from both networks can no longer reach the other network.
As a lot of you know, this is not the first [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.backbone-news.com/wp-content/uploads/2008/10/cogent.jpg"><img class="alignnone size-full wp-image-41" title="cogent" src="http://www.backbone-news.com/wp-content/uploads/2008/10/cogent.jpg" alt="" width="200" height="70" /> </a><a href="http://www.backbone-news.com/wp-content/uploads/2008/10/sprint_nextel_logo.jpg"><img class="alignnone size-full wp-image-40" title="sprint_nextel_logo" src="http://www.backbone-news.com/wp-content/uploads/2008/10/sprint_nextel_logo.jpg" alt="" width="166" height="95" /></a></p>
<p>What started as with a few messages on several ISP focused mailing-lists has been confirmed by Cogent in a <a title="Earthtimes.org: Cogent Press release" href="http://www.earthtimes.org/articles/show/sprint-nextel-severs-its-internet-connection-to-cogent-communications,603138.shtml" target="_blank">press release</a> today: Sprint-Nextel and Cogent have interrupted their peering connections, and as such customers from both networks can no longer reach the other network.</p>
<p>As a lot of you know, this is not the first time Cogent has been in the middle of a peering dispute, and so far, with no information from Sprint-Nextel on the matter, it is unclear what the reason behind the issue is, and who actually started the trouble.</p>
<p><strong>Update:</strong> Head over to the <a title="Renesys homepage" href="http://www.renesys.com" target="_blank">Renesys</a> blog to get Todd Underwoods <a title="Renesys Blog: Cogent/Sprint-Nextel" href="http://www.renesys.com/blog/2008/10/wrestling-with-the-zombie-spri.shtml" target="_blank">detailed analysis</a> of the situation. As always, worth reading. Their data gives details about the number of networks which are affected by this dispute:<br />
- 289 autonomous systems are single homed behind Cogent<br />
- 214 autonomous systems are single homed behind Sprint<br />
All of these networks are currently not able to reach each other!</p>
<p>Randy Epstein (President, WV Fiber) informed the readers of the <a title="Nanog Website" href="http://www.nanog.org" target="_blank">NANOG</a> mailing list that the WV Fiber network (AS19151) is currently also affected by this since they only contract with Sprint for Transit, and is settlement free with the rest of its peers, which doesn&#8217;t include Cogent anymore since late last year when Cogent depeered AS19151 for unknown reason.</p>
<p><strong>Update 2</strong>: Further information can be found in an <a title="Arbor: Cogent / Sprint depeering" href="http://asert.arbornetworks.com/2008/10/418/" target="_blank">article</a> at the <a title="Arbor Networks Homepage" href="http://www.arbornetworks.com" target="_blank">Arbor Networks</a> blog, giving also an idea of the amount of traffic exchanged between AS174 and AS1239. But still, no information has surfaced so far about the actual cause of the de-peering.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.backbone-news.com/2008/10/31/sprint-nextel-depeers-cogent/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
