<?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>Sonic.net Status &#187; Network</title>
	<atom:link href="http://corp.sonic.net/status/category/network/feed/" rel="self" type="application/rss+xml" />
	<link>http://corp.sonic.net/status</link>
	<description>Messages on the current status of Sonic.net&#039;s systems and equipment.</description>
	<lastBuildDate>Tue, 09 Mar 2010 19:11:36 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>San Francisco ATM switch failure.</title>
		<link>http://corp.sonic.net/status/2010/03/09/san-francisco-atm-switch-failure/</link>
		<comments>http://corp.sonic.net/status/2010/03/09/san-francisco-atm-switch-failure/#comments</comments>
		<pubDate>Tue, 09 Mar 2010 18:58:23 +0000</pubDate>
		<dc:creator>mmerner</dc:creator>
				<category><![CDATA[Network]]></category>
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://corp.sonic.net/status/?p=1000000805</guid>
		<description><![CDATA[At approximately 10:40 we had a hardware failure on an ATM switch in San Francisco. We are presently rebooting it. Approximate downtime should be 5-7 minutes. -Sonic NOC
Update 11:10AM: The ATM switch reload is complete and traffic appears to be returning to normal. If you continue to have DSL sync-no-surf connectivity issues, please contact our [...]]]></description>
			<content:encoded><![CDATA[<p>At approximately 10:40 we had a hardware failure on an ATM switch in San Francisco. We are presently rebooting it. Approximate downtime should be 5-7 minutes. -Sonic NOC</p>
<p>Update 11:10AM: The ATM switch reload is complete and traffic appears to be returning to normal. If you continue to have DSL sync-no-surf connectivity issues, please contact our tech support.</p>]]></content:encoded>
			<wfw:commentRss>http://corp.sonic.net/status/2010/03/09/san-francisco-atm-switch-failure/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Large Outage in San Francisco</title>
		<link>http://corp.sonic.net/status/2010/02/20/large-outage-in-san-francisco/</link>
		<comments>http://corp.sonic.net/status/2010/02/20/large-outage-in-san-francisco/#comments</comments>
		<pubDate>Sat, 20 Feb 2010 16:15:10 +0000</pubDate>
		<dc:creator>npatrick</dc:creator>
				<category><![CDATA[Network]]></category>

		<guid isPermaLink="false">http://corp.sonic.net/status/2010/02/20/large-outage-in-san-francisco/</guid>
		<description><![CDATA[We&#8217;re currently experiencing a rather large outage in San Francisco, presumably caused by a power failure to some of our colocation space there. All available resources are being brought to bear, and we&#8217;ll have more shortly. This outage is likely impacting a large portion of our DSL customers as well as some Dial, Biz-T, FRATM, [...]]]></description>
			<content:encoded><![CDATA[<p>We&#8217;re currently experiencing a rather large outage in San Francisco, presumably caused by a power failure to some of our colocation space there. All available resources are being brought to bear, and we&#8217;ll have more shortly. This outage is likely impacting a large portion of our DSL customers as well as some Dial, Biz-T, FRATM, and other services. -Nathan, Jared, and the rest of the NOC</p>
<p>Update 8:25AM: We have confirmed that the issue is caused by a power failure. Apparently the facility at 200 Paul Avenue is currently without utility power. The vast majority of the site&#8217;s generators, ATSes, and UPS systems worked properly, but the UPSes feeding suite 502 (the location of some of our equipment at that facility) did not transfer correctly. More to follow.</p>
<p>Update 9:19AM: Power has been restored to our equipment, and we&#8217;re ensuring that everything returns to service cleanly.</p>
<p>Update 9:32AM: Service to the vast majority of our customers has been restored. There appears to be one DSL aggregation device that is still having trouble &#8212; we&#8217;re taking a look at that now.</p>
<p>Update 10:22AM: All services have been restored. Please let us know if you still have any outstanding issues. We&#8217;ll be having a serious chat with our colocation provider about this event, as this outage occurred despite a massive investment in fully redundant A+B power &#8212; both of which died simultaneously.</p>]]></content:encoded>
			<wfw:commentRss>http://corp.sonic.net/status/2010/02/20/large-outage-in-san-francisco/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
		<item>
		<title>Unexpected DSL Aggregation Router Reboot</title>
		<link>http://corp.sonic.net/status/2010/02/10/unexpected-dsl-aggregation-router-reboot/</link>
		<comments>http://corp.sonic.net/status/2010/02/10/unexpected-dsl-aggregation-router-reboot/#comments</comments>
		<pubDate>Wed, 10 Feb 2010 11:28:49 +0000</pubDate>
		<dc:creator>jared</dc:creator>
				<category><![CDATA[Network]]></category>

		<guid isPermaLink="false">http://corp.sonic.net/status/?p=1000000777</guid>
		<description><![CDATA[At approximately 3:00 AM today, one of our DSL aggregation routers serving customers in the Bay Area suffered what appears to be a software crash. This software crash kept the router out of service until 3:14 AM, at which time it was booted up and handling customer traffic normally.
The exact cause of the software crash [...]]]></description>
			<content:encoded><![CDATA[<p>At approximately 3:00 AM today, one of our DSL aggregation routers serving customers in the Bay Area suffered what appears to be a software crash. This software crash kept the router out of service until 3:14 AM, at which time it was booted up and handling customer traffic normally.</p>
<p>The exact cause of the software crash is being investigated with the vendor at this time. We are monitoring the router, and all affected customers appear to be back online at this time.</p>
<p>-Jared</p>
<p>Update: The router has unexpectedly crashed again. We are in the process of moving all customers served by this router to a hot spare. Connectivity should be restored shortly.</p>
<p>Update: All affected customers have been moved to the hot spare successfully. All affected customers should be online again at this time.</p>]]></content:encoded>
			<wfw:commentRss>http://corp.sonic.net/status/2010/02/10/unexpected-dsl-aggregation-router-reboot/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ATM Customer Aggregation Router Reload</title>
		<link>http://corp.sonic.net/status/2009/12/28/atm-customer-aggregation-router-reload-3/</link>
		<comments>http://corp.sonic.net/status/2009/12/28/atm-customer-aggregation-router-reload-3/#comments</comments>
		<pubDate>Mon, 28 Dec 2009 21:51:24 +0000</pubDate>
		<dc:creator>jared</dc:creator>
				<category><![CDATA[Network]]></category>

		<guid isPermaLink="false">http://corp.sonic.net/status/?p=1000000716</guid>
		<description><![CDATA[This evening, Tuesday, Dec 29 at 12:01 AM, we will be performing a maintenance reload on our ATM customer aggregation routers. This will result in 5-10 minutes of downtime for Business-T and FRATM customers.
-Jared
Update: The scheduled router reloads have been completed and all affected customers should be back online. Downtime for affected customers was &#60; [...]]]></description>
			<content:encoded><![CDATA[<p>This evening, Tuesday, Dec 29 at 12:01 AM, we will be performing a maintenance reload on our ATM customer aggregation routers. This will result in 5-10 minutes of downtime for Business-T and FRATM customers.</p>
<p>-Jared</p>
<p>Update: The scheduled router reloads have been completed and all affected customers should be back online. Downtime for affected customers was &lt; 10 minutes.</p>]]></content:encoded>
			<wfw:commentRss>http://corp.sonic.net/status/2009/12/28/atm-customer-aggregation-router-reload-3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>DSL Aggregation Equipment Failure</title>
		<link>http://corp.sonic.net/status/2009/11/22/dsl-aggregation-equipment-failure/</link>
		<comments>http://corp.sonic.net/status/2009/11/22/dsl-aggregation-equipment-failure/#comments</comments>
		<pubDate>Mon, 23 Nov 2009 06:56:20 +0000</pubDate>
		<dc:creator>npatrick</dc:creator>
				<category><![CDATA[Network]]></category>
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://corp.sonic.net/status/2009/11/22/dsl-aggregation-equipment-failure/</guid>
		<description><![CDATA[One of our DSL aggregation routers handling customers in California&#8217;s LATA 1 (largely the San Francisco area) started having problems at approximately 10:41pm tonight. Customers experienced a complete service outage until 10:47pm, at which point we were able to restore partial service. We&#8217;re presently working to move the affected customer&#8217;s service to alternate equipment, which [...]]]></description>
			<content:encoded><![CDATA[<p>One of our DSL aggregation routers handling customers in California&#8217;s LATA 1 (largely the San Francisco area) started having problems at approximately 10:41pm tonight. Customers experienced a complete service outage until 10:47pm, at which point we were able to restore partial service. We&#8217;re presently working to move the affected customer&#8217;s service to alternate equipment, which will involve 10-15 minutes worth of additional downtime in the near future. At present, customers on this particular piece of aggregation gear are experiencing ~7% packet loss. We&#8217;ll update this entry as our work progresses.</p>
<p>-Nathan, Matt and Jared</p>
<p>Update 11:14pm:</p>
<p>The problem turned out to be a failing ATM port inside of our network. We&#8217;ve migrated all traffic to a hot-spare port and service has returned to normal.</p>]]></content:encoded>
			<wfw:commentRss>http://corp.sonic.net/status/2009/11/22/dsl-aggregation-equipment-failure/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Pogowave finishes network address translation migration</title>
		<link>http://corp.sonic.net/status/2009/10/13/pogowave-finishes-network-address-translation-migration/</link>
		<comments>http://corp.sonic.net/status/2009/10/13/pogowave-finishes-network-address-translation-migration/#comments</comments>
		<pubDate>Tue, 13 Oct 2009 16:46:17 +0000</pubDate>
		<dc:creator>kavan</dc:creator>
				<category><![CDATA[Maintenance]]></category>
		<category><![CDATA[Network]]></category>

		<guid isPermaLink="false">http://corp.sonic.net/status/?p=1000000612</guid>
		<description><![CDATA[Today is the day that the wireless department will turn off network address translation on our last Pogowave station; The Golden Apple Ranch on Fitzpatrick Lane.
This is our largest and most diverse station, featuring three low band access points.
We think that this can be performed in less than 30 minutes of down time.  Thank you [...]]]></description>
			<content:encoded><![CDATA[<p>Today is the day that the wireless department will turn off network address translation on our last Pogowave station; The Golden Apple Ranch on Fitzpatrick Lane.</p>
<p>This is our largest and most diverse station, featuring three low band access points.</p>
<p>We think that this can be performed in less than 30 minutes of down time.  Thank you for your patience during this transition that will allow for improved customer support for all Sonic.net Pogowave customers.</p>]]></content:encoded>
			<wfw:commentRss>http://corp.sonic.net/status/2009/10/13/pogowave-finishes-network-address-translation-migration/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>DHCP Server Failure</title>
		<link>http://corp.sonic.net/status/2009/08/30/dhcp-server-failure-2/</link>
		<comments>http://corp.sonic.net/status/2009/08/30/dhcp-server-failure-2/#comments</comments>
		<pubDate>Sun, 30 Aug 2009 15:44:12 +0000</pubDate>
		<dc:creator>jared</dc:creator>
				<category><![CDATA[Network]]></category>

		<guid isPermaLink="false">http://corp.sonic.net/status/?p=1000000569</guid>
		<description><![CDATA[This morning at approximately 8 AM our Support staff became aware that one of our DHCP servers was not serving DHCP leases properly, in such a way that our monitoring systems were not able to detect the problem. Our Support team escalated the problem to the Operations staff and we were able to remedy the [...]]]></description>
			<content:encoded><![CDATA[<p>This morning at approximately 8 AM our Support staff became aware that one of our DHCP servers was not serving DHCP leases properly, in such a way that our monitoring systems were not able to detect the problem. Our Support team escalated the problem to the Operations staff and we were able to remedy the problem by rebooting the partially-locked server. Service was restored by approximately 8:28 AM. We apologize for this outage and will be looking into ways of extending our monitoring so this unusual type of failure will not be missed again.</p>
<p>-Jared and the Support team</p>
<p>Update: The DHCP server has begun to fail again, so we have removed it from service. DHCP should be functioning normally again. If you are having problems obtaining a DHCP lease, please try rebooting your modem and any computers or routers that are having problems.</p>]]></content:encoded>
			<wfw:commentRss>http://corp.sonic.net/status/2009/08/30/dhcp-server-failure-2/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>ADSL2+ Speed Reprofiling</title>
		<link>http://corp.sonic.net/status/2009/08/03/adsl2-speed-reprofiling/</link>
		<comments>http://corp.sonic.net/status/2009/08/03/adsl2-speed-reprofiling/#comments</comments>
		<pubDate>Tue, 04 Aug 2009 00:20:32 +0000</pubDate>
		<dc:creator>jared</dc:creator>
				<category><![CDATA[Network]]></category>

		<guid isPermaLink="false">http://corp.sonic.net/status/?p=1000000534</guid>
		<description><![CDATA[This Wednesday, August 5 at 12:01 AM, we will be re-profiling all of our ADSL2+ lines. This will cause all ADSL2+ lines to have to re-sync, causing a minute or two of downtime for any Fusion or Flexlink ADSL2+ customer. If you have problems with your ADSL2+ line after this operation, please reboot your modem.
-Jared
Update: [...]]]></description>
			<content:encoded><![CDATA[<p>This Wednesday, August 5 at 12:01 AM, we will be re-profiling all of our ADSL2+ lines. This will cause all ADSL2+ lines to have to re-sync, causing a minute or two of downtime for any Fusion or Flexlink ADSL2+ customer. If you have problems with your ADSL2+ line after this operation, please reboot your modem.</p>
<p>-Jared</p>
<p>Update: We have completed the re-profiling of all our ADSL2+ lines. All affected lines should be up and running at the new speeds.</p>]]></content:encoded>
			<wfw:commentRss>http://corp.sonic.net/status/2009/08/03/adsl2-speed-reprofiling/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>CLEC DSLAM maintenance</title>
		<link>http://corp.sonic.net/status/2009/06/24/clec-dslam-maintenance-3/</link>
		<comments>http://corp.sonic.net/status/2009/06/24/clec-dslam-maintenance-3/#comments</comments>
		<pubDate>Wed, 24 Jun 2009 16:54:13 +0000</pubDate>
		<dc:creator>cbc</dc:creator>
				<category><![CDATA[Maintenance]]></category>
		<category><![CDATA[Network]]></category>

		<guid isPermaLink="false">http://corp.sonic.net/status/?p=1000000487</guid>
		<description><![CDATA[This Thursday, at 12:01 am, we will be performing some intrusive maintenance on one of our DSLAM&#8217;s in San Francisco.  This DSLAM serves Fusion &#38; Flexlink ADSL2+ in the Lower Pacific Heights/ Western Addition area.  This work will cause an interruption of service for about 20 minutes while we replace a suspected bad cable.
-Clay]]></description>
			<content:encoded><![CDATA[<p>This Thursday, at 12:01 am, we will be performing some intrusive maintenance on one of our DSLAM&#8217;s in San Francisco.  This DSLAM serves Fusion &amp; Flexlink ADSL2+ in the Lower Pacific Heights/ Western Addition area.  This work will cause an interruption of service for about 20 minutes while we replace a suspected bad cable.</p>
<p>-Clay</p>]]></content:encoded>
			<wfw:commentRss>http://corp.sonic.net/status/2009/06/24/clec-dslam-maintenance-3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Router Maintenance Reloads</title>
		<link>http://corp.sonic.net/status/2009/06/22/router-maintenance-reloads/</link>
		<comments>http://corp.sonic.net/status/2009/06/22/router-maintenance-reloads/#comments</comments>
		<pubDate>Mon, 22 Jun 2009 20:11:30 +0000</pubDate>
		<dc:creator>jared</dc:creator>
				<category><![CDATA[Maintenance]]></category>
		<category><![CDATA[Network]]></category>

		<guid isPermaLink="false">http://corp.sonic.net/status/?p=1000000483</guid>
		<description><![CDATA[This Tuesday, June 23 at 12:01 AM we will be performing maintenance reloads of the routers that terminate our Business-T service, and two Redbacks that terminate traditional DSL service. This will affect all Business-T customers, all Fresno DSL subscribers, and a small subset of DSL customers in the Bay Area. Expected downtime is 5 minutes.
-Jared
Update [...]]]></description>
			<content:encoded><![CDATA[<p>This Tuesday, June 23 at 12:01 AM we will be performing maintenance reloads of the routers that terminate our Business-T service, and two Redbacks that terminate traditional DSL service. This will affect all Business-T customers, all Fresno DSL subscribers, and a small subset of DSL customers in the Bay Area. Expected downtime is 5 minutes.</p>
<p>-Jared</p>
<p>Update June 23 12:31 AM: The Redback reloads were completed without incident, and all DSL customers should be back online at this time. Our Los Angeles <acronym title="Point of Presence">POP</acronym> Business-T router locked up during the reload and required a physical reboot to come back up properly. For this reason Business-T customers in the Los Angeles area experienced approximately 15-20 minutes of downtime. Our other Business-T routers reloaded without incident. All services affected by this maintenance have been restored at this time.</p>]]></content:encoded>
			<wfw:commentRss>http://corp.sonic.net/status/2009/06/22/router-maintenance-reloads/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
