<?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/"
		>
<channel>
	<title>Comments on: BroadLink wireless outage</title>
	<atom:link href="http://corp.sonic.net/status/2008/08/27/broadlink-wireless-outage/feed/" rel="self" type="application/rss+xml" />
	<link>http://corp.sonic.net/status/2008/08/27/broadlink-wireless-outage/</link>
	<description>Messages on the current status of Sonic.net's systems and equipment.</description>
	<lastBuildDate>Thu, 19 Nov 2009 22:00:28 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: dane</title>
		<link>http://corp.sonic.net/status/2008/08/27/broadlink-wireless-outage/comment-page-1/#comment-610</link>
		<dc:creator>dane</dc:creator>
		<pubDate>Wed, 03 Sep 2008 16:57:36 +0000</pubDate>
		<guid isPermaLink="false">http://corp.sonic.net/status/?p=1000000084#comment-610</guid>
		<description>Mike,

It&#039;s not our network to fix, it&#039;s owned by Broadlink.  I don&#039;t yet know what their plans are at this point.

Which other wireless provider are you referring to?  I&#039;m not aware of anyone of that scale in the area.

-Dane</description>
		<content:encoded><![CDATA[<p>Mike,</p>
<p>It&#8217;s not our network to fix, it&#8217;s owned by Broadlink.  I don&#8217;t yet know what their plans are at this point.</p>
<p>Which other wireless provider are you referring to?  I&#8217;m not aware of anyone of that scale in the area.</p>
<p>-Dane</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike</title>
		<link>http://corp.sonic.net/status/2008/08/27/broadlink-wireless-outage/comment-page-1/#comment-609</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Wed, 03 Sep 2008 16:03:07 +0000</pubDate>
		<guid isPermaLink="false">http://corp.sonic.net/status/?p=1000000084#comment-609</guid>
		<description>Are you saying here that the bl wireless network will just be allowed to continue to deteriorate and put the existing subscribers at risk for future extended unplanned outages because it doesn&#039;t have the structure or tools to manage it properly like a real service provider network should? Have you considered selling it? Or have you considered maybe talking to other wireless broadband providers and soliciting proposals to get the core issues fixed so it&#039;s no longer a support burden? 

You know there is a successful wireless broadband provider just north of you that has a substantially large network with perhaps 1000 subs and that does have solutions to the problems you mentioned such as centralized provisioning, support, suspension and disconnection, and just might know some magic that could help you and your customers achieve a higher level of service and stability than what you are currently. And epically, if you&#039;re left with pulling together former employees of a defunct company to fix core equipment failures when they occur, I would say that the time to think about it is now rather than later.</description>
		<content:encoded><![CDATA[<p>Are you saying here that the bl wireless network will just be allowed to continue to deteriorate and put the existing subscribers at risk for future extended unplanned outages because it doesn&#8217;t have the structure or tools to manage it properly like a real service provider network should? Have you considered selling it? Or have you considered maybe talking to other wireless broadband providers and soliciting proposals to get the core issues fixed so it&#8217;s no longer a support burden? </p>
<p>You know there is a successful wireless broadband provider just north of you that has a substantially large network with perhaps 1000 subs and that does have solutions to the problems you mentioned such as centralized provisioning, support, suspension and disconnection, and just might know some magic that could help you and your customers achieve a higher level of service and stability than what you are currently. And epically, if you&#8217;re left with pulling together former employees of a defunct company to fix core equipment failures when they occur, I would say that the time to think about it is now rather than later.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dane</title>
		<link>http://corp.sonic.net/status/2008/08/27/broadlink-wireless-outage/comment-page-1/#comment-599</link>
		<dc:creator>dane</dc:creator>
		<pubDate>Thu, 28 Aug 2008 15:54:03 +0000</pubDate>
		<guid isPermaLink="false">http://corp.sonic.net/status/?p=1000000084#comment-599</guid>
		<description>It was great that some of the old BL folks were able to get together and help us resolve it!  See some narrative and pic here: http://corp.sonic.net/ceo/2008/08/27/punt/</description>
		<content:encoded><![CDATA[<p>It was great that some of the old BL folks were able to get together and help us resolve it!  See some narrative and pic here: <a href="http://corp.sonic.net/ceo/2008/08/27/punt/" rel="nofollow">http://corp.sonic.net/ceo/2008/08/27/punt/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bill Paris</title>
		<link>http://corp.sonic.net/status/2008/08/27/broadlink-wireless-outage/comment-page-1/#comment-598</link>
		<dc:creator>bill Paris</dc:creator>
		<pubDate>Thu, 28 Aug 2008 15:35:03 +0000</pubDate>
		<guid isPermaLink="false">http://corp.sonic.net/status/?p=1000000084#comment-598</guid>
		<description>So sorry that Sonic is stuck in the middle of this but thanks for getting us back online. It was the catalyst for getting us to switch to Sonic DSL next week.</description>
		<content:encoded><![CDATA[<p>So sorry that Sonic is stuck in the middle of this but thanks for getting us back online. It was the catalyst for getting us to switch to Sonic DSL next week.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Punt! &#124; Sonic.net CEO Blog</title>
		<link>http://corp.sonic.net/status/2008/08/27/broadlink-wireless-outage/comment-page-1/#comment-597</link>
		<dc:creator>Punt! &#124; Sonic.net CEO Blog</dc:creator>
		<pubDate>Thu, 28 Aug 2008 06:15:27 +0000</pubDate>
		<guid isPermaLink="false">http://corp.sonic.net/status/?p=1000000084#comment-597</guid>
		<description>[...] mentioned in the status blog (formerly system MOTD), BroadLink Communications had a system failure in a critical component of [...]</description>
		<content:encoded><![CDATA[<p>[...] mentioned in the status blog (formerly system MOTD), BroadLink Communications had a system failure in a critical component of [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
