<?xml version="1.0" encoding="utf-8"?>
				<rss version="2.0">
					<channel>
						<title>Maintenance information</title>
						<link>http://noc.leaseweb.com/</link>
						<language>en</language>
						<description>A list of all planned maintenance windows for the LeaseWeb network.</description><item>
				<title>Easynet maintenance [Update]</title>
				<link>http://noc.leaseweb.com/maintenance.php?i=139</link>
				<guid>http://noc.leaseweb.com/maintenance.php?i=139</guid>
				<description>Startdate: August 20th 2008 00:01:00 &lt;BR/&gt;Enddate: August 20th 2008 06:00:00&lt;BR/&gt;&lt;BR/&gt;Dear customer,&lt;BR/&gt;&lt;BR/&gt;We have scheduled this maintenance for two reasons. &lt;BR/&gt;&lt;BR/&gt;The first one is to test the redundant setup. During the outage on 08-07-2008 our backup router failed to take over when the primary failed with a hardware failure. The last few weeks we have tested the backup router and have found the problem of the failure(further explained in the rfo). We will test the backup router in controlled steps so impact to customers is minimal. If at any time we run in to problems we will fall back to the primary router. During the swap customers can experience packetloss and loss of connection for a few minutes. Customers located in suite 1D will also be swapped physical to the backup uplink we have supplied in the racks. When all customers are swapped over to the backup router we will turn off the primary router. If everything checks out we will start we the second phase of the maintenance.&lt;BR/&gt;&lt;BR/&gt;The second phase is to replace some structured cabling. We already replaced all the second uplinks in suite 1D to our customers and our shared racks. At this step we are running on the second uplinks and replace the primary uplinks. All cables are already in place and only needs to be connected. After we have completed this step we will swap back to the primary router with the new uplinks.&lt;BR/&gt;&lt;BR/&gt;We have chosen for a large time frame so we can do this maintenance in small steps and verify every step. During this time frame customers should only be affected for a short time during the swap to the backup router and back to the primary router.&lt;BR/&gt;&lt;BR/&gt;During the maintenance customers can check noc.leaseweb.com for updates. At anytime during the maintenance they can also email or call us for an update.&lt;BR/&gt;&lt;BR/&gt;Kind regards,&lt;BR/&gt;&lt;BR/&gt;LeaseWeb - NOC&lt;BR/&gt;&lt;BR/&gt;[update 23:39]&lt;BR/&gt;All engineers are onsite and are preparing for the maintenance.&lt;BR/&gt;&lt;BR/&gt;[update 00:00]&lt;BR/&gt;We are swapping traffic for customers in room 2F.&lt;BR/&gt;&lt;BR/&gt;[update 00:09]&lt;BR/&gt;Customers in room 2F are switches over.&lt;BR/&gt;&lt;BR/&gt;[update 00:10]&lt;BR/&gt;Preparing on switching customers in room 2A.&lt;BR/&gt;&lt;BR/&gt;[update 00:17]&lt;BR/&gt;All customers in room 2A have been switched.&lt;BR/&gt;&lt;BR/&gt;[update 00:26]&lt;BR/&gt;Starting switching customers to secondary uplink in room 1D.&lt;BR/&gt;&lt;BR/&gt;[update 01:41]&lt;BR/&gt;We are currently having a loop which is causing packetloss. We are still investigating.&lt;BR/&gt;&lt;BR/&gt;[update 02:00]&lt;BR/&gt;Loop has been found still investigating.&lt;BR/&gt;&lt;BR/&gt;[update 02:20]&lt;BR/&gt;We are splitting up the engineers on site. One group is working on the loop problem the other group is working on the cables to the primary router. This way we try to reduce the window running production on the backup router.&lt;BR/&gt;&lt;BR/&gt;[update 02:44]&lt;BR/&gt;The loop problem is resolved. Traffic should be stable now.&lt;BR/&gt;&lt;BR/&gt;[update 03:23]&lt;BR/&gt;Some customers are still having problems with packetloss. We are migrating back to the primary router to resolve this.&lt;BR/&gt;&lt;BR/&gt;[update 04:40]&lt;BR/&gt;All traffic has been restored to primary router. Traffic should be restored to all customers.</description>
			</item><item>
				<title>EvoSwitch KPN maintenance</title>
				<link>http://noc.leaseweb.com/maintenance.php?i=127</link>
				<guid>http://noc.leaseweb.com/maintenance.php?i=127</guid>
				<description>Startdate: August 14th 2008 21:00:00 &lt;BR/&gt;Enddate: August 15th 2008 06:45:00&lt;BR/&gt;&lt;BR/&gt;Dear customer,&lt;BR/&gt;&lt;BR/&gt;One of our darkfiber providers (KPN) has scheduled a maintenance window from 14 August 21:00 till 15 August 06:45 at EvoSwitch. All traffic will be routed via our other darkfiber providers so the impact to our customers will be minimal.  Short periods of packetloss / higher latency can occur during convergence.&lt;BR/&gt;&lt;BR/&gt;Kind regards,&lt;BR/&gt;&lt;BR/&gt;LeaseWeb&lt;BR/&gt;&lt;BR/&gt;Timezone is CEST</description>
			</item>
		</channel>
		</rss>