<?xml version="1.0" encoding="UTF-8"?><!-- generator="b2evolution/0.9.0.12" -->
<rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"					xmlns:admin="http://webns.net/mvcb/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel rdf:about="http://news.nestegg.net/index.php">
	<title>Nestegg Announcements</title>
	<link>http://news.nestegg.net/index.php</link>
	<description>Service annoucements from Nestegg, LLC</description>
	<dc:language>en-US</dc:language>
	<admin:generatorAgent rdf:resource="http://b2evolution.net/?v=0.9.0.12"/>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>
	<items>
		<rdf:Seq>
					<rdf:li rdf:resource="http://news.nestegg.net/index.php/2009/02/05/internet_issues"/>
					<rdf:li rdf:resource="http://news.nestegg.net/index.php/2008/12/11/yipes_issues"/>
					<rdf:li rdf:resource="http://news.nestegg.net/index.php/2008/08/03/web_server_outage"/>
					<rdf:li rdf:resource="http://news.nestegg.net/index.php/2008/06/02/yipes_is_back_up"/>
					<rdf:li rdf:resource="http://news.nestegg.net/index.php/2008/06/02/yipes_is_down"/>
				</rdf:Seq>
	</items>
</channel>
<item rdf:about="http://news.nestegg.net/index.php/2009/02/05/internet_issues">
	<title>Internet issues</title>
	<link>http://news.nestegg.net/index.php/2009/02/05/internet_issues</link>
	<dc:date>2009-02-05T17:24:37Z</dc:date>
	<dc:creator>nestegg</dc:creator>
	<dc:subject>Fort Collins</dc:subject>
	<description>There's a peering issue between Yipes and Global Crossing which is causing some sites to be unreachable.  We've temporarily disabled our Yipes connection until the problem is resolved.  This may result in slight slower performance.

The problem has been resolved.  Yipes is back online.</description>
	<content:encoded><![CDATA[	<p>There's a peering issue between Yipes and Global Crossing which is causing some sites to be unreachable.  We've temporarily disabled our Yipes connection until the problem is resolved.  This may result in slight slower performance.</p>
	<p>The problem has been resolved.  Yipes is back online.
</p>
]]></content:encoded>
</item>
<item rdf:about="http://news.nestegg.net/index.php/2008/12/11/yipes_issues">
	<title>Yipes Issues</title>
	<link>http://news.nestegg.net/index.php/2008/12/11/yipes_issues</link>
	<dc:date>2008-12-11T15:28:19Z</dc:date>
	<dc:creator>nestegg</dc:creator>
	<dc:subject>Fort Collins</dc:subject>
	<description>Our Yipes connection is bouncing up and down this morning.  They have dispatched a tech to their Fort Collins node to investigate.  No estimated time to repair.

When they go down traffic is failing over to our backup circuits, but it's causing some choppy performance.  Expect reduced performance until this is resolved.

11:30AM MT --- Yipes reports the problem has been resolved, although we haven't seen any drops since 8:06AM.</description>
	<content:encoded><![CDATA[	<p>Our Yipes connection is bouncing up and down this morning.  They have dispatched a tech to their Fort Collins node to investigate.  No estimated time to repair.</p>
	<p>When they go down traffic is failing over to our backup circuits, but it's causing some choppy performance.  Expect reduced performance until this is resolved.</p>
	<p>11:30AM MT --- Yipes reports the problem has been resolved, although we haven't seen any drops since 8:06AM.
</p>
]]></content:encoded>
</item>
<item rdf:about="http://news.nestegg.net/index.php/2008/08/03/web_server_outage">
	<title>Web server outage</title>
	<link>http://news.nestegg.net/index.php/2008/08/03/web_server_outage</link>
	<dc:date>2008-08-03T16:08:29Z</dc:date>
	<dc:creator>nestegg</dc:creator>
	<dc:subject>San Jose</dc:subject>
	<description>We're having an issue with one of our web servers this morning.  It looks like there may be hardware issues  with the machine, so we are moving the sites hosted on that machine to a different server.

Update: All services have been restored.</description>
	<content:encoded><![CDATA[	<p>We're having an issue with one of our web servers this morning.  It looks like there may be hardware issues  with the machine, so we are moving the sites hosted on that machine to a different server.</p>
	<p>Update: All services have been restored.
</p>
]]></content:encoded>
</item>
<item rdf:about="http://news.nestegg.net/index.php/2008/06/02/yipes_is_back_up">
	<title>Yipes is back up</title>
	<link>http://news.nestegg.net/index.php/2008/06/02/yipes_is_back_up</link>
	<dc:date>2008-06-02T20:23:36Z</dc:date>
	<dc:creator>nestegg</dc:creator>
	<dc:subject>Fort Collins</dc:subject>
	<description>We don't know the full story yet, but apparently there was a major power outage at PRPA (ironically the power company) where all of the fiber is terminated.  If we get more information, like why a UPS didn't handle this problem, we'll post here.</description>
	<content:encoded><![CDATA[	<p>We don't know the full story yet, but apparently there was a major power outage at PRPA (ironically the power company) where all of the fiber is terminated.  If we get more information, like why a UPS didn't handle this problem, we'll post here.
</p>
]]></content:encoded>
</item>
<item rdf:about="http://news.nestegg.net/index.php/2008/06/02/yipes_is_down">
	<title>Yipes is down</title>
	<link>http://news.nestegg.net/index.php/2008/06/02/yipes_is_down</link>
	<dc:date>2008-06-02T19:44:27Z</dc:date>
	<dc:creator>nestegg</dc:creator>
	<dc:subject>Fort Collins</dc:subject>
	<description>A ticket is open and they are investigating.  It appears to be affecting all of Fort Collins.  We are still up but running very slowly over the backup circuit.</description>
	<content:encoded><![CDATA[	<p>A ticket is open and they are investigating.  It appears to be affecting all of Fort Collins.  We are still up but running very slowly over the backup circuit.
</p>
]]></content:encoded>
</item>
</rdf:RDF>
