<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>iWeb Blog » Status</title>
	
	<link>http://blog.iweb.com/en</link>
	<description>iWeb's News, Updates and Notifications</description>
	<lastBuildDate>Wed, 23 May 2012 20:52:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/iWebBlogStatusEN" /><feedburner:info uri="iwebblogstatusen" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><geo:lat>45.46802784900447</geo:lat><geo:long>-73.54191720485687</geo:long><feedburner:emailServiceId>iWebBlogStatusEN</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><item>
		<title>Incident: Communication infrastructure (Resolved)</title>
		<link>http://feedproxy.google.com/~r/iWebBlogStatusEN/~3/nISKsG4WNbA/10217.html</link>
		<comments>http://blog.iweb.com/en/2012/05/incident-communication-infrastructure/10217.html#comments</comments>
		<pubDate>Sat, 19 May 2012 21:13:36 +0000</pubDate>
		<dc:creator>iWebstaff</dc:creator>
				<category><![CDATA[Status]]></category>
		<category><![CDATA[incident_20120519_EN]]></category>

		<guid isPermaLink="false">http://blog.iweb.com/en/?p=10217</guid>
		<description><![CDATA[Communications infrastructure issue
Start: 16:50
Time of resolution: 17:45
Impact: Customers may experience issues when submitting new requests
We are currently investigating a situation that might affect a segment of our communication infrastructure.
The following communications channels are affected: Customer hub ticket submission
We invite you to contact us via telephone or live chat. Our staff will gladly provide any help [...]]]></description>
			<content:encoded><![CDATA[<p>Communications infrastructure issue</p>
<p>Start: 16:50<br />
Time of resolution: 17:45<br />
Impact: Customers may experience issues when submitting new requests</p>
<p>We are currently investigating a situation that might affect a segment of our communication infrastructure.</p>
<p>The following communications channels are affected: Customer hub ticket submission</p>
<p>We invite you to contact us via telephone or live chat. Our staff will gladly provide any help needed.</p>
<p>Our technical team is actively working on finding a solution to this problem. We will communicate with you about the status of this operation when we have more details..</p>
<p>We apologize for any inconvenience this situation may cause. If you have any questions, please do not hesitate to contact our support team (http://www.iweb.com/contacts/).</p>
<p>Thank you for your patience and understanding.</p>
<!-- PHP 5.x --><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=nISKsG4WNbA:KPoEYaBXe6M:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=nISKsG4WNbA:KPoEYaBXe6M:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?i=nISKsG4WNbA:KPoEYaBXe6M:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/iWebBlogStatusEN/~4/nISKsG4WNbA" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.iweb.com/en/2012/05/incident-communication-infrastructure/10217.html/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://blog.iweb.com/en/2012/05/incident-communication-infrastructure/10217.html</feedburner:origLink></item>
		<item>
		<title>Maintenance: Network Infrastructure (R7, R8) [Resolved]</title>
		<link>http://feedproxy.google.com/~r/iWebBlogStatusEN/~3/3BLaYmfvqdc/10200.html</link>
		<comments>http://blog.iweb.com/en/2012/05/maintenance-network-infrastructure-r7-r8/10200.html#comments</comments>
		<pubDate>Mon, 14 May 2012 16:38:20 +0000</pubDate>
		<dc:creator>iWebstaff</dc:creator>
				<category><![CDATA[Status]]></category>
		<category><![CDATA[maintenance_reseau_r7_r8_20120515_en]]></category>

		<guid isPermaLink="false">http://blog.iweb.com/en/?p=10200</guid>
		<description><![CDATA[The maintenance has been successfully completed. In the coming hours, we will  monitor the performance and the stability of the affected services to  make sure that all is working normally.
We apologize  for any inconvenience this situation may have caused. If you have any  questions, please do not hesitate to contact our [...]]]></description>
			<content:encoded><![CDATA[<p>The maintenance has been successfully completed. In the coming hours, we will  monitor the performance and the stability of the affected services to  make sure that all is working normally.</p>
<p>We apologize  for any inconvenience this situation may have caused. If you have any  questions, please do not hesitate to contact our support team (http://www.iweb.com/contacts/).</p>
<p>Thank you for your patience and understanding.</p>
<p>&#8211;</p>
<p>Affected service: R7 and R8 distributions routers<br />
Start: Maintenance will be rescheduled to 2012-05-17 00:00 EDT from 2012-05-16 00:00 EDT<br />
Maintenance duration: 6 hours<br />
Impact: This maintenance will be non service impacting</p>
<p>A maintenance on distribution routers R7 and R8 is planned on 2012-05-16 at 00:00 EDT.</p>
<p>This maintenance will be non service impacting; however, due to the nature of the work we are sending this out as a precautionary notice.</p>
<p>If you have any questions, please do not  hesitate to contact our support team (http://www.iweb.com/contacts/).</p>
<p>Thank you for your patience and  understanding.</p>
<!-- PHP 5.x --><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=3BLaYmfvqdc:WMLexU-Ayos:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=3BLaYmfvqdc:WMLexU-Ayos:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?i=3BLaYmfvqdc:WMLexU-Ayos:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/iWebBlogStatusEN/~4/3BLaYmfvqdc" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.iweb.com/en/2012/05/maintenance-network-infrastructure-r7-r8/10200.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.iweb.com/en/2012/05/maintenance-network-infrastructure-r7-r8/10200.html</feedburner:origLink></item>
		<item>
		<title>Maintenance: Control Center [Resolved]</title>
		<link>http://feedproxy.google.com/~r/iWebBlogStatusEN/~3/P1CUY1AEWkc/10177.html</link>
		<comments>http://blog.iweb.com/en/2012/05/maintenance-control-center-11/10177.html#comments</comments>
		<pubDate>Thu, 10 May 2012 19:20:35 +0000</pubDate>
		<dc:creator>iWebstaff</dc:creator>
				<category><![CDATA[Status]]></category>
		<category><![CDATA[maintenance_cc_20120514_en]]></category>

		<guid isPermaLink="false">http://blog.iweb.com/en/?p=10177</guid>
		<description><![CDATA[Update &#8211; 2012-05-14 8:30 EST &#8211; The maintenance for the Control Center has been successfully completed. In the coming hours, we will  monitor the performance and the stability of the affected services to  make sure that all is working normally.
We apologize  for any inconvenience this situation may have caused. If you have [...]]]></description>
			<content:encoded><![CDATA[<p>Update &#8211; 2012-05-14 8:30 EST &#8211; The maintenance for the Control Center has been successfully completed. In the coming hours, we will  monitor the performance and the stability of the affected services to  make sure that all is working normally.</p>
<p>We apologize  for any inconvenience this situation may have caused. If you have any  questions, please do not hesitate to contact our support team (http://www.iweb.com/contacts/).</p>
<p>&#8211;</p>
<p>Service affected: Control Center<br />
Start: Monday, May 14 between 8:00 and 9:30 EST<br />
Maintenance duration: 90 minutes<br />
Impact: Control Center unavailable during the maintenance.</p>
<p>A maintenance is planned on our network, which will affect the Control Center, Monday, May 14 between 8:00 and 9:30 EST.</p>
<p>The Control Center will be unavailable for 90 minutes during the maintenance period, but access to the servers of our clients and their websites will not be affected.</p>
<p>If you have any questions, please do not hesitate to contact our technical support team (http://www.iweb.com/contacts/).</p>
<!-- PHP 5.x --><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=P1CUY1AEWkc:3sBFq-5EMF8:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=P1CUY1AEWkc:3sBFq-5EMF8:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?i=P1CUY1AEWkc:3sBFq-5EMF8:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/iWebBlogStatusEN/~4/P1CUY1AEWkc" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.iweb.com/en/2012/05/maintenance-control-center-11/10177.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.iweb.com/en/2012/05/maintenance-control-center-11/10177.html</feedburner:origLink></item>
		<item>
		<title>Incident: Control center [Resolved]</title>
		<link>http://feedproxy.google.com/~r/iWebBlogStatusEN/~3/k9hFEeISv8Q/10179.html</link>
		<comments>http://blog.iweb.com/en/2012/05/incident-control-center/10179.html#comments</comments>
		<pubDate>Thu, 10 May 2012 17:52:49 +0000</pubDate>
		<dc:creator>iWebstaff</dc:creator>
				<category><![CDATA[Status]]></category>
		<category><![CDATA[20120510_cc_en]]></category>

		<guid isPermaLink="false">http://blog.iweb.com/en/?p=10179</guid>
		<description><![CDATA[Update 2012-05-10 15:00 EDT &#8211; The incident has been successfully resolved. In the coming hours, we will monitor the performance and the stability of the affected services to make sure that all is working normally. We apologize for any inconvenience this situation may have caused. If you have any questions, please do not hesitate to [...]]]></description>
			<content:encoded><![CDATA[<p>Update 2012-05-10 15:00 EDT &#8211; The incident has been successfully resolved. In the coming hours, we will monitor the performance and the stability of the affected services to make sure that all is working normally. We apologize for any inconvenience this situation may have caused. If you have any questions, please do not hesitate to contact our support team (http://www.iweb.com/contacts/).</p>
<p>Thank you for your patience and understanding.</p>
<p>&#8211;</p>
<p>Start: 2012-05-10 13:45 EDT<br />
Estimated time of resolution: 1 hour<br />
Impact: Control Center unavailability</p>
<p>We are currently investigating a situation that might affect the Control Center (cc.iweb.com).</p>
<p>We invite you to contact us via telephone or live chat if you are in need of technical support. An agent will take care of creating the request for you.</p>
<p>Our technical team is actively working on finding a solution to this problem. We will regularly communicate with you about the status of this operation.</p>
<p>We apologize for any inconvenience this situation may cause. If you have any questions, please do not hesitate to contact our support team (http://www.iweb.com/contacts/).</p>
<p>Thank you for your patience and understanding.</p>
<!-- PHP 5.x --><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=k9hFEeISv8Q:EcIJHTCMapk:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=k9hFEeISv8Q:EcIJHTCMapk:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?i=k9hFEeISv8Q:EcIJHTCMapk:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/iWebBlogStatusEN/~4/k9hFEeISv8Q" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.iweb.com/en/2012/05/incident-control-center/10179.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.iweb.com/en/2012/05/incident-control-center/10179.html</feedburner:origLink></item>
		<item>
		<title>Incident: R1Soft Backup Services [Resolved]</title>
		<link>http://feedproxy.google.com/~r/iWebBlogStatusEN/~3/_7eIQ9CgHE8/10143.html</link>
		<comments>http://blog.iweb.com/en/2012/05/incident-r1soft-backup-services-2/10143.html#comments</comments>
		<pubDate>Tue, 01 May 2012 13:30:29 +0000</pubDate>
		<dc:creator>iWebstaff</dc:creator>
				<category><![CDATA[Status]]></category>
		<category><![CDATA[r1soft_incident_20120501_en]]></category>

		<guid isPermaLink="false">http://blog.iweb.com/en/?p=10143</guid>
		<description><![CDATA[Update 2012-05-01 10:15 EDT &#8211; The incident has been successfully resolved. In the coming hours, we will monitor the performance and the stability of the affected services to make sure that all is working normally. We apologize for any inconvenience this situation may have caused. If you have any questions, please do not hesitate to [...]]]></description>
			<content:encoded><![CDATA[<p>Update 2012-05-01 10:15 EDT &#8211; The incident has been successfully resolved. In the coming hours, we will monitor the performance and the stability of the affected services to make sure that all is working normally. We apologize for any inconvenience this situation may have caused. If you have any questions, please do not hesitate to contact our support team (http://www.iweb.com/contacts/).</p>
<p>&#8211;</p>
<p>Start: 2012-05-01 8:00 EDT<br />
Estimated time of resolution: Resolved<br />
Impact: Backups/Restorations unavailability</p>
<p>We are currently investigating a situation that is affecting our R1Soft backup service.</p>
<p>A limited number of customers might experience problems with their R1Soft interface resulting an error message such as “Running task failed license key invalid”.</p>
<p>Our technical team is actively working on finding a solution to this problem. We will regularly communicate with you about the status of this operation.</p>
<p>We apologize for any inconvenience this situation may cause. If you have any questions, please do not hesitate to contact our support team (http://www.iweb.com/contacts/).</p>
<p>Thank you for your patience and understanding.</p>
<!-- PHP 5.x --><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=_7eIQ9CgHE8:7GZuNCecCz4:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=_7eIQ9CgHE8:7GZuNCecCz4:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?i=_7eIQ9CgHE8:7GZuNCecCz4:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/iWebBlogStatusEN/~4/_7eIQ9CgHE8" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.iweb.com/en/2012/05/incident-r1soft-backup-services-2/10143.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.iweb.com/en/2012/05/incident-r1soft-backup-services-2/10143.html</feedburner:origLink></item>
		<item>
		<title>Maintenance: Control Center [Resolved]</title>
		<link>http://feedproxy.google.com/~r/iWebBlogStatusEN/~3/1KPkIkLnaDY/10137.html</link>
		<comments>http://blog.iweb.com/en/2012/04/maintenance-control-center-10/10137.html#comments</comments>
		<pubDate>Tue, 24 Apr 2012 16:06:33 +0000</pubDate>
		<dc:creator>iWebstaff</dc:creator>
				<category><![CDATA[Status]]></category>
		<category><![CDATA[maintenance_cc_20120426_en]]></category>

		<guid isPermaLink="false">http://blog.iweb.com/en/?p=10137</guid>
		<description><![CDATA[Update &#8211; 2012-04-26 09:30 EST &#8211; The maintenance for the Control Center has been successfully completed. In the coming hours, we will  monitor the performance and the stability of the affected services to  make sure that all is working normally.
We apologize  for any inconvenience this situation may have caused. If you have [...]]]></description>
			<content:encoded><![CDATA[<p>Update &#8211; 2012-04-26 09:30 EST &#8211; The maintenance for the Control Center has been successfully completed. In the coming hours, we will  monitor the performance and the stability of the affected services to  make sure that all is working normally.</p>
<p>We apologize  for any inconvenience this situation may have caused. If you have any  questions, please do not hesitate to contact our support team (http://www.iweb.com/contacts/).</p>
<p>&#8211;</p>
<p>Service affected: Control Center<br />
Start: Thursday, April 26 between 8:00 and 9:30 EST<br />
Maintenance duration: 90 minutes<br />
Impact: Control Center unavailable during the maintenance.</p>
<p>A maintenance is planned on our network, which will affect the Control Center, Thursday, April 26 between 8:00 and 9:30 EST.</p>
<p>The Control Center will be unavailable for 90 minutes during the maintenance period, but access to the servers of our clients and their websites will not be affected.</p>
<p>If you have any questions, please do not hesitate to contact our technical support team (http://www.iweb.com/contacts/).</p>
<!-- PHP 5.x --><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=1KPkIkLnaDY:_8Sdr08JjXk:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=1KPkIkLnaDY:_8Sdr08JjXk:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?i=1KPkIkLnaDY:_8Sdr08JjXk:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/iWebBlogStatusEN/~4/1KPkIkLnaDY" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.iweb.com/en/2012/04/maintenance-control-center-10/10137.html/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://blog.iweb.com/en/2012/04/maintenance-control-center-10/10137.html</feedburner:origLink></item>
		<item>
		<title>Post Mortem: Network Infrastructure Incident (iWeb-NE data center)</title>
		<link>http://feedproxy.google.com/~r/iWebBlogStatusEN/~3/gY57fXH3Ex8/10126.html</link>
		<comments>http://blog.iweb.com/en/2012/04/post-mortem-network-infrastructure-incident-iweb-ne-data-center/10126.html#comments</comments>
		<pubDate>Thu, 19 Apr 2012 21:26:50 +0000</pubDate>
		<dc:creator>iWebstaff</dc:creator>
				<category><![CDATA[Status]]></category>
		<category><![CDATA[20120419_post_mortem_network_infra_en]]></category>

		<guid isPermaLink="false">http://blog.iweb.com/en/?p=10126</guid>
		<description><![CDATA[EN &#8211; ES

Here is the Post Mortem of the network incident of April 17th, 2012 that affected the first network segment of our iWeb-NE data center. The affected network segment houses approximately 25% of our Smart Server clients. Customers with classic, colocation and cloud servers have not been affected by this network incident.
At 12:15 EDT, [...]]]></description>
			<content:encoded><![CDATA[<p><strong><a href="#en">EN</a> &#8211; <a href="#es">ES</a></strong></p>
<p><a name="en"></a><br />
Here is the Post Mortem of the network incident of April 17th, 2012 that affected the first network segment of our iWeb-NE data center. The affected network segment houses approximately 25% of our Smart Server clients. Customers with classic, colocation and cloud servers have not been affected by this network incident.</p>
<p>At 12:15 EDT, a pair of router in the iWeb-NE data center suffered a CPU overload due to a flood of the ARP table.</p>
<p>A global protection was put in place at 13:00 EDT in order to protect the network devices from this abnormal traffic. This allowed us to bring back the network connectivity for the affected customers.</p>
<p>All affected servers were back online at 13:25 EDT.</p>
<p>As soon as the network connectivity was back to normal, our network administrators worked in collaboration with the vendor to find the safest and most definitive solution for our clients.</p>
<p>Before we could implement a longer term solution we experienced another degradation of the network at 16:50 EDT.</p>
<p>The network connectivity came back progressively and as of 17:55 EDT, 70% of the affected customers were back online. Finally, all affected servers were online at 18:05 EDT.</p>
<p>We are still investigating the problem with the manufacturer. A maintenance will be scheduled in order to apply the necessary patches and thus ensure that such problem does not occur again in the future.</p>
<p>Until the maintenance is performed, our network administrators are monitoring the affected network segment and adding an additional layer of redundancy to ensure that such problem does not occur again in the future.</p>
<p>We apologize for any inconvenience this may have caused. If you have any questions, please do not hesitate to contact our support team (http://www.iweb.com/contacts/).</p>
<p>&#8211;<br />
<a name="es"></a></p>
<p>A continuación les presentamos un postmortem del incidente de red ocurrido el 17 de abril de 2012 en nuestro centro de datos iWeb-NE.  El segmento de red afectado por el incidente, sirve cerca del 25% de nuestra clientela de servidores Smart.  Aquéllos que poseen servidores clásicos, cloud o en colocación, no fueron afectados. </p>
<p>Vers 12:15 HAE, une paire de routeurs de distribution du centre iWeb-NE ont subit une surcharge CPU dû à un flux de trafic anormal au niveau de la table ARP des routeurs.</p>
<p>Alrededor de las 12:15 hs., una parte de nuestros routers de distribución del centro iWeb-NE, experimentó una sobrecarga en los CPU causado por un flujo de tráfico anormal en la tabla ARP.</p>
<p>La protección global se activó hacia las 13:00 hs. para proteger nuestros equipos de red.  Gracias a dicha protección la conectividad de red fue gradualmente restablecida. </p>
<p>Los servidores afectados por el incidente volvieron a línea hacia las 13:25 hs.  </p>
<p>Una vez la situación estabilizada, nuestros administradores de red comenzaron a trabajar con el fabricante en una estrategia que permita resolver el  problema de forma permanente. Sin embargo, antes de que pudiera ser aplicada, sufrimos un nuevo incidente de red, esto ocurrió cerca de las 16:50 (Hora del este).<br />
La conectividad fue restablecida gradualmente y cerca del 70% de los clientes afectados volvieron a línea hacia las 17:55 hs.  Por último, la totalidad de los servidores afectados volvió a línea a las 18:05 hs. </p>
<p>Mientras el mantenimiento se lleva a cabo, nuestros administradores vigilarán la red de cerca para asegurarse de que no haya degradación del servicio.  Procedimos igualmente a agregar una capa de redundancia adicional para minimizar los riesgos de una nueva degradación.</p>
<p>Nos disculpamos por cualquier inconveniente que esta situación pueda haberle provocado. </p>
<p>Si tiene alguna pregunta, no dude en comunicarse con nuestro equipo de soporte técnico: http://es.iweb.com/soporte-alojamiento</p>
<!-- PHP 5.x --><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=gY57fXH3Ex8:tGXp_r3ODjo:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=gY57fXH3Ex8:tGXp_r3ODjo:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?i=gY57fXH3Ex8:tGXp_r3ODjo:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/iWebBlogStatusEN/~4/gY57fXH3Ex8" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.iweb.com/en/2012/04/post-mortem-network-infrastructure-incident-iweb-ne-data-center/10126.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.iweb.com/en/2012/04/post-mortem-network-infrastructure-incident-iweb-ne-data-center/10126.html</feedburner:origLink></item>
		<item>
		<title>Incident: Network Infrastructure – iWeb-NE Data Center (1st network segment) – [Resolved]</title>
		<link>http://feedproxy.google.com/~r/iWebBlogStatusEN/~3/FfzfgkM9KyM/10104.html</link>
		<comments>http://blog.iweb.com/en/2012/04/incident-network-infrastructure-smart-servers-2nd-outage/10104.html#comments</comments>
		<pubDate>Tue, 17 Apr 2012 21:08:10 +0000</pubDate>
		<dc:creator>iWebstaff</dc:creator>
				<category><![CDATA[Status]]></category>
		<category><![CDATA[network_incident_20120417_en]]></category>

		<guid isPermaLink="false">http://blog.iweb.com/en/?p=10104</guid>
		<description><![CDATA[The incident&#8217;s post mortem is available here.
&#8211;
Update 2012-04-17 22:00 EDT – All servers should be online. If you are still experiencing network connectivity issues, we invite you to submit a server outage ticket in your customer hub at https://hub.iweb.com/en/ and we will follow-up by mail.  If you already have an open ticket we will get [...]]]></description>
			<content:encoded><![CDATA[<p>The incident&#8217;s post mortem is available <a href="http://blog.iweb.com/en/2012/04/post-mortem-network-infrastructure-incident-iweb-ne-data-center/10126.html">here</a>.</p>
<p>&#8211;</p>
<p>Update 2012-04-17 22:00 EDT – All servers should be online. If you are still experiencing network connectivity issues, we invite you to submit a server outage ticket in your customer hub at https://hub.iweb.com/en/ and we will follow-up by mail.  If you already have an open ticket we will get to it.  Please do not open a duplicate ticket.  Thank you very much for your patience and understanding.</p>
<p>&#8211;</p>
<p>Update 2012-04-17 18:00 EDT &#8211; Most of the affected servers are now back online. If you are still experiencing network connectivity issues, we invite you to submit a server outage ticket in your customer hub at https://hub.iweb.com/en/ and we will follow-up by mail. Thank you very much for your patience and understanding.</p>
<p>&#8211;</p>
<p>Update 2012-04-17 17:55 EDT &#8211; About 20% more servers (70% total) are now back online and the rest is progressively being brought online. We are also in communication with the people at Cisco so they can help us find a permanent solution as quickly as possible. We appreciate your patience.</p>
<p>&#8211;</p>
<p>Update 2012-04-17 17:30 EDT &#8211; About 50% of the affected Smart Servers are back online. The network outage was caused by a high CPU load on the distribution switches of the affected segment of the network and we are still investigating the root cause of this load in order to prevent any new outages. Thank you for your patience.</p>
<p>&#8211;</p>
<p>Update 2012-04-17 17:15 EDT &#8211; This second incident is very similar to the first one and affecting Smart Server customers of one of the network segment in the iWeb-NE data center. We will post an update shortly and we sincerely apologize for the inconveniences this might cause you.</p>
<p>&#8211;</p>
<p>Start: 2012-04-17 16:50 EDT<br />
Estimated time of resolution: 1 hour<br />
Impact: Network unavailability for Smart Servers in one of the network segment of the iWeb-NE datacenter.</p>
<p>We are currently investigating a situation that might affect a segment of our network infrastructure.</p>
<p>Our technical  team is actively working on finding a solution to this  problem. We  will regularly communicate with you about the status of this operation.</p>
<p>We apologize for any inconvenience this situation may cause. If you have any questions, please do not hesitate   to contact our support team (http://www.iweb.com/contacts/).</p>
<p>Thank you for your patience  and  understanding.</p>
<!-- PHP 5.x --><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=FfzfgkM9KyM:DtmsS1d0VFQ:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=FfzfgkM9KyM:DtmsS1d0VFQ:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?i=FfzfgkM9KyM:DtmsS1d0VFQ:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/iWebBlogStatusEN/~4/FfzfgkM9KyM" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.iweb.com/en/2012/04/incident-network-infrastructure-smart-servers-2nd-outage/10104.html/feed</wfw:commentRss>
		<slash:comments>147</slash:comments>
		<feedburner:origLink>http://blog.iweb.com/en/2012/04/incident-network-infrastructure-smart-servers-2nd-outage/10104.html</feedburner:origLink></item>
		<item>
		<title>Incident: Network Infrastructure – iWeb-NE Data Center (1st network segment) – [Resolved]</title>
		<link>http://feedproxy.google.com/~r/iWebBlogStatusEN/~3/yy5C1HQZRfY/10092.html</link>
		<comments>http://blog.iweb.com/en/2012/04/incident-network-infrastructure-smart-servers/10092.html#comments</comments>
		<pubDate>Tue, 17 Apr 2012 16:41:49 +0000</pubDate>
		<dc:creator>iWebstaff</dc:creator>
				<category><![CDATA[Status]]></category>
		<category><![CDATA[20110417_network_problem_en]]></category>

		<guid isPermaLink="false">http://blog.iweb.com/en/?p=10092</guid>
		<description><![CDATA[Update 2012-04-17 13:45 EDT &#8211; The network incident has been successfully resolved. The customer hub interface is now also fully functional. In the coming hours, we will monitor the performance and the stability of the affected services to make sure that all is working normally. We apologize for any inconvenience this situation may have caused. [...]]]></description>
			<content:encoded><![CDATA[<p>Update 2012-04-17 13:45 EDT &#8211; The network incident has been successfully resolved. The customer hub interface is now also fully functional. In the coming hours, we will monitor the performance and the stability of the affected services to make sure that all is working normally. We apologize for any inconvenience this situation may have caused. If you have any questions, please do not hesitate to contact our support team (http://www.iweb.com/contacts/).</p>
<p>Thank you for your patience and understanding.</p>
<p>&#8211;</p>
<p>Update 2012-04-17 13:25 EDT &#8211; The network problem has now been fully resolved but we are experiencing problems with our hub client interface. In the meantime, if you are still experiencing any problem, you can contact our support team by live chat or phone support.</p>
<p>&#8211;</p>
<p>Update 2012-04-17 13:15 EDT &#8211; About 75% of Smart Servers of the affected network segment are back online and fully reachable. Another update will be posted shortly.</p>
<p>&#8211;</p>
<p>Update 2012-04-17 13:10 EDT &#8211; We have made some progress and more servers are back online and fully reachable. For those of you who are still impacted by this outage, rest assured that our network team is doing everything in their power to have this issue fixed as quickly as possible.</p>
<p>&#8211;</p>
<p>Update 2012-04-17 12:55 EDT – 1/3 of the Smart Servers affected by the network problem are back online. An emergency network maintenance is currently ongoing in order to bring the rest online as quickly as possible. Thank you for your patience and understanding.</p>
<p>&#8211;</p>
<p>Start: 12:15<br />
Estimated time of resolution: N/A<br />
Impact: Inaccessibility for the smart servers on one of the segment of our network infrastructure.</p>
<p>We are currently investigating a situation that might affect a segment of our network infrastructure.<br />
Our technical team is actively working on finding a solution to this problem. We will regularly communicate with you about the status of this operation.<br />
We apologize for any inconvenience this situation may cause. If you have any questions, please do not hesitate to contact our support team (http://www.iweb.com/contacts/).<br />
Thank you for your patience and understanding.</p>
<!-- PHP 5.x --><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=yy5C1HQZRfY:8DclnUo64zs:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=yy5C1HQZRfY:8DclnUo64zs:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?i=yy5C1HQZRfY:8DclnUo64zs:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/iWebBlogStatusEN/~4/yy5C1HQZRfY" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.iweb.com/en/2012/04/incident-network-infrastructure-smart-servers/10092.html/feed</wfw:commentRss>
		<slash:comments>183</slash:comments>
		<feedburner:origLink>http://blog.iweb.com/en/2012/04/incident-network-infrastructure-smart-servers/10092.html</feedburner:origLink></item>
		<item>
		<title>Maintenance: Control Center [Resolved]</title>
		<link>http://feedproxy.google.com/~r/iWebBlogStatusEN/~3/8mipuhMeKMk/10082.html</link>
		<comments>http://blog.iweb.com/en/2012/04/maintenance-control-center-9/10082.html#comments</comments>
		<pubDate>Sun, 08 Apr 2012 12:16:21 +0000</pubDate>
		<dc:creator>iWebstaff</dc:creator>
				<category><![CDATA[Status]]></category>
		<category><![CDATA[maintenance_cc_en_20120410]]></category>

		<guid isPermaLink="false">http://blog.iweb.com/en/?p=10082</guid>
		<description><![CDATA[Update &#8211; 2012-04-10 09:00 EST &#8211; The maintenance for the Control Center has been successfully completed. In the coming hours, we will  monitor the performance and the stability of the affected services to  make sure that all is working normally.
We apologize  for any inconvenience this situation may have caused. If you have [...]]]></description>
			<content:encoded><![CDATA[<p>Update &#8211; 2012-04-10 09:00 EST &#8211; The maintenance for the Control Center has been successfully completed. In the coming hours, we will  monitor the performance and the stability of the affected services to  make sure that all is working normally.</p>
<p>We apologize  for any inconvenience this situation may have caused. If you have any  questions, please do not hesitate to contact our support team (http://www.iweb.com/contacts/).</p>
<p>&#8211;</p>
<p>Service affected: Control Center<br />
Start: Tuesday, April 10 between 8:00 and 9:30 EST<br />
Maintenance duration: 90 min.<br />
Impact: Control Center unavailable during the maintenance.</p>
<p>A maintenance is planned on our network, which will affect the Control Center, Tuesday, April 10 between 8:00 and 9:30 EST.</p>
<p>The Control Center will be unavailable for 90 minutes during the maintenance period, but access to the servers of our clients and their websites will not be affected.</p>
<p>If you have any questions, please do not hesitate to contact our technical support team (http://www.iweb.com/contacts/).</p>
<!-- PHP 5.x --><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=8mipuhMeKMk:tcKcg9fMlRI:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=8mipuhMeKMk:tcKcg9fMlRI:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?i=8mipuhMeKMk:tcKcg9fMlRI:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/iWebBlogStatusEN/~4/8mipuhMeKMk" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.iweb.com/en/2012/04/maintenance-control-center-9/10082.html/feed</wfw:commentRss>
		<slash:comments>5</slash:comments>
		<feedburner:origLink>http://blog.iweb.com/en/2012/04/maintenance-control-center-9/10082.html</feedburner:origLink></item>
		<item>
		<title>Maintenance: Phone System (last phase) [Resolved]</title>
		<link>http://feedproxy.google.com/~r/iWebBlogStatusEN/~3/PWKjNMCKdoI/10051.html</link>
		<comments>http://blog.iweb.com/en/2012/03/maintenance-phone-system-last-phase/10051.html#comments</comments>
		<pubDate>Tue, 27 Mar 2012 12:00:01 +0000</pubDate>
		<dc:creator>iWebstaff</dc:creator>
				<category><![CDATA[Status]]></category>
		<category><![CDATA[phone_system_20120328_en]]></category>

		<guid isPermaLink="false">http://blog.iweb.com/en/?p=10051</guid>
		<description><![CDATA[Update – 2012-03-29 00:15 AM EDT – The maintenance for our phone system has been successfully completed. In the coming hours, we will monitor the performance and the stability of the affected services to make sure that all is working normally.
We apologize for any inconvenience this situation may have caused. If you have any questions, [...]]]></description>
			<content:encoded><![CDATA[<p>Update – 2012-03-29 00:15 AM EDT – The maintenance for our phone system has been successfully completed. In the coming hours, we will monitor the performance and the stability of the affected services to make sure that all is working normally.</p>
<p>We apologize for any inconvenience this situation may have caused. If you have any questions, please do not hesitate to contact our support team (http://www.iweb.com/contacts/).</p>
<p>Thank you for your patience and understanding.</p>
<p>&#8211;</p>
<p>Service affected: Phone System<br />
Start: Wednesday, March 28 2012 at 11:00 PM EDT<br />
Maintenance duration: 2 hours<br />
Impact: This maintenance will be non service impacting</p>
<p>A maintenance will be conducted on our phone systems in order to apply various fixes and updates. This is the last phase of a serie of maintenances that have been previously planned in order to upgrade the capacity, stability and quality of our phone system.</p>
<p>The maintenance will take place on Wednesday, March 28, 2012 from 11:00 PM EDT to Thursday, March 29 at 1:00 AM EDT.</p>
<p>This maintenance will be non service impacting; however, due to the nature of the work we are sending this out as a precautionary notice.</p>
<p>Thank you for your attention.</p>
<!-- PHP 5.x --><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=PWKjNMCKdoI:qknYCnfGnzA:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=PWKjNMCKdoI:qknYCnfGnzA:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?i=PWKjNMCKdoI:qknYCnfGnzA:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/iWebBlogStatusEN/~4/PWKjNMCKdoI" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.iweb.com/en/2012/03/maintenance-phone-system-last-phase/10051.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.iweb.com/en/2012/03/maintenance-phone-system-last-phase/10051.html</feedburner:origLink></item>
		<item>
		<title>Incident: Smart Server provisioning with Debian Lenny [Resolved]</title>
		<link>http://feedproxy.google.com/~r/iWebBlogStatusEN/~3/DVDl0z77mDQ/10035.html</link>
		<comments>http://blog.iweb.com/en/2012/03/incident-smart-server-provisioning-with-debian-lenny/10035.html#comments</comments>
		<pubDate>Mon, 26 Mar 2012 18:44:30 +0000</pubDate>
		<dc:creator>iWebstaff</dc:creator>
				<category><![CDATA[Status]]></category>
		<category><![CDATA[20120326_en_smart_debian]]></category>

		<guid isPermaLink="false">http://blog.iweb.com/en/?p=10035</guid>
		<description><![CDATA[Update 2012-03-28 3:00 PM EDT &#8211; The synchronization of our mirror has now completed and Debian operating system installations and reinstallations are now back to functioning normally for Smart Server clients. In the coming hours, we will monitor the performance and the stability of the affected services to make sure that all is working normally.
We [...]]]></description>
			<content:encoded><![CDATA[<p>Update 2012-03-28 3:00 PM EDT &#8211; The synchronization of our mirror has now completed and Debian operating system installations and reinstallations are now back to functioning normally for Smart Server clients. In the coming hours, we will monitor the performance and the stability of the affected services to make sure that all is working normally.</p>
<p>We apologize for any inconvenience this situation may have caused. If you have any questions, please do not hesitate to contact our support team (http://www.iweb.com/contacts/).</p>
<p>Thank you for your patience and understanding.</p>
<p>&#8211;</p>
<p>Update 2012-03-27 4:00 PM EDT &#8211; The synchronization of our mirror from Debian&#8217;s archive is still ongoing. We expect the synchronisation to complete by tomorrow (Wednesday). A new update will be posted tomorrow when we have more details. In the meantime, if you have any questions, please do not hesitate to contact our support team.</p>
<p>&#8211;</p>
<p>Update 2012-03-26 4:00 PM EDT &#8211; We are currently synchronizing our mirror from the Debian archive and should be able to normally install / reinstall Debian Lenny on our Smart Servers as soon as the synchronization completes. In the meantime, our provisioning team is manually installing the operating system if a new Smart Server is bought with Debian Lenny (this might take a little longer than the usual automatic process).</p>
<p>&#8211;</p>
<p>Start: 2012-03-26 2:00 PM EDT<br />
Estimated time of resolution: Resolved<br />
Impact: Smart Server installations and reinstallations with Debian Lenny not being able to complete successfully at this time.</p>
<p>We are currently investigating a situation that might affect our Smart Server provisioning system and all Debian Lenny installation and reinstallation are not able to complete properly. We strongly suggest you do not reinstall your server with Debian Lenny until we correct this problem.</p>
<p>Our technical  team is actively working on finding a solution to this problem. We  will regularly communicate with you about the status of this operation.</p>
<p>We apologize for any inconvenience this situation may cause. If you have any questions, please do not hesitate   to contact our support team (http://www.iweb.com/contacts/).</p>
<p>Thank you for your patience  and  understanding.</p>
<!-- PHP 5.x --><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=DVDl0z77mDQ:4TE3HFMb5_g:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=DVDl0z77mDQ:4TE3HFMb5_g:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?i=DVDl0z77mDQ:4TE3HFMb5_g:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/iWebBlogStatusEN/~4/DVDl0z77mDQ" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.iweb.com/en/2012/03/incident-smart-server-provisioning-with-debian-lenny/10035.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.iweb.com/en/2012/03/incident-smart-server-provisioning-with-debian-lenny/10035.html</feedburner:origLink></item>
		<item>
		<title>Maintenance: Control Center [Resolved]</title>
		<link>http://feedproxy.google.com/~r/iWebBlogStatusEN/~3/MYNqFigMK1Q/10039.html</link>
		<comments>http://blog.iweb.com/en/2012/03/maintenance-control-center-8/10039.html#comments</comments>
		<pubDate>Sat, 24 Mar 2012 12:00:14 +0000</pubDate>
		<dc:creator>iWebstaff</dc:creator>
				<category><![CDATA[Status]]></category>
		<category><![CDATA[20120327_maintenance_cc_en]]></category>

		<guid isPermaLink="false">http://blog.iweb.com/en/?p=10039</guid>
		<description><![CDATA[Update &#8211; 2012-03-27 09:35 EST &#8211; The maintenance for the Control Center has been successfully completed. In the coming hours, we will  monitor the performance and the stability of the affected services to  make sure that all is working normally.
We apologize  for any inconvenience this situation may have caused. If you have [...]]]></description>
			<content:encoded><![CDATA[<p>Update &#8211; 2012-03-27 09:35 EST &#8211; The maintenance for the Control Center has been successfully completed. In the coming hours, we will  monitor the performance and the stability of the affected services to  make sure that all is working normally.</p>
<p>We apologize  for any inconvenience this situation may have caused. If you have any  questions, please do not hesitate to contact our support team (http://www.iweb.com/contacts/).</p>
<p>&#8211;</p>
<p>Service affected: Control Center<br />
Start: Tuesday, March 27 between 8:00 and 9:30 EST<br />
Maintenance duration: 90 min.<br />
Impact: Control Center unavailable during the maintenance.</p>
<p>A maintenance is planned on our network, which will affect the Control Center, Thursday, March 27 between 8:00 and 9:30 EST.</p>
<p>The Control Center will be unavailable for 90 minutes during the maintenance period, but access to the servers of our clients and their websites will not be affected.</p>
<p>If you have any questions, please do not hesitate to contact our technical support team (http://www.iweb.com/contacts/).</p>
<!-- PHP 5.x --><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=MYNqFigMK1Q:04v-4vBOphM:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=MYNqFigMK1Q:04v-4vBOphM:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?i=MYNqFigMK1Q:04v-4vBOphM:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/iWebBlogStatusEN/~4/MYNqFigMK1Q" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.iweb.com/en/2012/03/maintenance-control-center-8/10039.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.iweb.com/en/2012/03/maintenance-control-center-8/10039.html</feedburner:origLink></item>
		<item>
		<title>Maintenance: Phone System [Resolved]</title>
		<link>http://feedproxy.google.com/~r/iWebBlogStatusEN/~3/NEHnWMxFN4c/10016.html</link>
		<comments>http://blog.iweb.com/en/2012/03/maintenance-phone-system-5/10016.html#comments</comments>
		<pubDate>Fri, 16 Mar 2012 17:34:05 +0000</pubDate>
		<dc:creator>iWebstaff</dc:creator>
				<category><![CDATA[Status]]></category>
		<category><![CDATA[maint_phone_en_20120319]]></category>

		<guid isPermaLink="false">http://blog.iweb.com/en/?p=10016</guid>
		<description><![CDATA[Update – 2012-03-19 7:00 EDT – The maintenance for our phone system has been successfully completed. In the coming hours, we will  monitor the performance and the stability of the affected services to  make sure that all is working normally.
We apologize  for any inconvenience this situation may have caused. If you have [...]]]></description>
			<content:encoded><![CDATA[<p>Update – 2012-03-19 7:00 EDT – The maintenance for our phone system has been successfully completed. In the coming hours, we will  monitor the performance and the stability of the affected services to  make sure that all is working normally.</p>
<p>We apologize  for any inconvenience this situation may have caused. If you have any  questions, please do not hesitate to contact our support team (http://www.iweb.com/contacts/).</p>
<p>Thank you for your patience and understanding.</p>
<p>&#8211;</p>
<p>Service affected: Phone System<br />
Start: Monday March 19 2012 at 5H00 AM EDT<br />
Maintenance duration: 2h<br />
Impact: Phone navigation menu unavailable during maintenance (calls will be directly forwarded to customer service).</p>
<p>A routine maintenance will be conducted on our phone systems in order to apply various fixes and updates. The maintenance will take place on Monday, March 19, 2012 from 5h00 EST to 07H00 EST.</p>
<p>The phone navigation menu will be unavailable during maintenance and calls will be forwarded directly to customer service. You still will be able to contact us via the livechat or by creating a ticket in your Customer Hub.</p>
<p>Thank you for your attention.</p>
<!-- PHP 5.x --><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=NEHnWMxFN4c:p3AVQMAIGu8:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=NEHnWMxFN4c:p3AVQMAIGu8:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?i=NEHnWMxFN4c:p3AVQMAIGu8:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/iWebBlogStatusEN/~4/NEHnWMxFN4c" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.iweb.com/en/2012/03/maintenance-phone-system-5/10016.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.iweb.com/en/2012/03/maintenance-phone-system-5/10016.html</feedburner:origLink></item>
		<item>
		<title>Maintenance: Jinn and Lumiva email infrastructure [RESOLVED]</title>
		<link>http://feedproxy.google.com/~r/iWebBlogStatusEN/~3/2RYFekJSz_g/10010.html</link>
		<comments>http://blog.iweb.com/en/2012/03/maintenance-jinn-and-lumiva-email-infrastructure-2/10010.html#comments</comments>
		<pubDate>Mon, 12 Mar 2012 02:56:10 +0000</pubDate>
		<dc:creator>iWebstaff</dc:creator>
				<category><![CDATA[Status]]></category>
		<category><![CDATA[jinn_lumiva_20120314_en]]></category>

		<guid isPermaLink="false">http://blog.iweb.com/en/?p=10010</guid>
		<description><![CDATA[Update &#8211; 2012-3-14 10:15 &#8211; The maintenance for our mail servers Jinn and Lumiva has been successfully completed. No impact on services were noted. Systems will be monitored closely for any issues. 
We thank you for your comprehension.
___
Affected services: Jinn and Lumiva email infrastructure
Impact: No service outage is to be expected
Start: Wednesday, March 14, 2011 [...]]]></description>
			<content:encoded><![CDATA[<p>Update &#8211; 2012-3-14 10:15 &#8211; The maintenance for our mail servers Jinn and Lumiva has been successfully completed. No impact on services were noted. Systems will be monitored closely for any issues. </p>
<p>We thank you for your comprehension.</p>
<p>___</p>
<p>Affected services: Jinn and Lumiva email infrastructure<br />
Impact: No service outage is to be expected<br />
Start: Wednesday, March 14, 2011 at 06:00 EDT</p>
<p>A preventive maintenance will be conducted Wednesday, March 14, 2011 at 06:00 EDT for the mail clusters Jinn and Lumiva.</p>
<p>This maintenance will be NON SERVICE IMPACTING; however, due to the nature of the work we are sending this out as a precautionary notice.</p>
<p>If you have any questions, please do not hesitate to contact our technical support team at http://www.iweb.com/contacts.</p>
<p>Thank you for your attention.</p>
<!-- PHP 5.x --><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=2RYFekJSz_g:swfN38aheBI:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=2RYFekJSz_g:swfN38aheBI:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?i=2RYFekJSz_g:swfN38aheBI:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/iWebBlogStatusEN/~4/2RYFekJSz_g" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.iweb.com/en/2012/03/maintenance-jinn-and-lumiva-email-infrastructure-2/10010.html/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://blog.iweb.com/en/2012/03/maintenance-jinn-and-lumiva-email-infrastructure-2/10010.html</feedburner:origLink></item>
		<item>
		<title>Maintenance: Control Center [Resolved]</title>
		<link>http://feedproxy.google.com/~r/iWebBlogStatusEN/~3/_jRGI7ncots/9994.html</link>
		<comments>http://blog.iweb.com/en/2012/03/maintenance-control-center-7/9994.html#comments</comments>
		<pubDate>Mon, 05 Mar 2012 12:03:25 +0000</pubDate>
		<dc:creator>iWebstaff</dc:creator>
				<category><![CDATA[Status]]></category>
		<category><![CDATA[maintenance_cc_20120308_en]]></category>

		<guid isPermaLink="false">http://blog.iweb.com/en/?p=9994</guid>
		<description><![CDATA[Update &#8211; 2012-03-08 09:00 EST &#8211; The maintenance for the Control Center has been successfully completed. In the coming hours, we will  monitor the performance and the stability of the affected services to  make sure that all is working normally.
We apologize  for any inconvenience this situation may have caused. If you have [...]]]></description>
			<content:encoded><![CDATA[<p>Update &#8211; 2012-03-08 09:00 EST &#8211; The maintenance for the Control Center has been successfully completed. In the coming hours, we will  monitor the performance and the stability of the affected services to  make sure that all is working normally.</p>
<p>We apologize  for any inconvenience this situation may have caused. If you have any  questions, please do not hesitate to contact our support team (http://www.iweb.com/contacts/).</p>
<p>&#8211;</p>
<p>Service affected: Control Center<br />
Start: Thursday, March 8 between 8:00 and 9:30 EST<br />
Maintenance duration: 90 min.<br />
Impact: Control Center unavailable during the maintenance.</p>
<p>A maintenance is planned on our network, which will affect the Control Center, Thursday, March 8 between 8:00 and 9:30 EST.</p>
<p>The Control Center will be unavailable for 90 minutes during the maintenance period, but access to the servers of our clients and their websites will not be affected.</p>
<p>If you have any questions, please do not hesitate to contact our technical support team (http://www.iweb.com/contacts/).</p>
<!-- PHP 5.x --><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=_jRGI7ncots:tooaIQY7XY8:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=_jRGI7ncots:tooaIQY7XY8:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?i=_jRGI7ncots:tooaIQY7XY8:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/iWebBlogStatusEN/~4/_jRGI7ncots" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.iweb.com/en/2012/03/maintenance-control-center-7/9994.html/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://blog.iweb.com/en/2012/03/maintenance-control-center-7/9994.html</feedburner:origLink></item>
		<item>
		<title>Maintenance: Phone System [Resolved]</title>
		<link>http://feedproxy.google.com/~r/iWebBlogStatusEN/~3/SrzTH98FIxc/9975.html</link>
		<comments>http://blog.iweb.com/en/2012/03/maintenance-phone-system-4/9975.html#comments</comments>
		<pubDate>Mon, 05 Mar 2012 12:00:24 +0000</pubDate>
		<dc:creator>Stéphane Jose</dc:creator>
				<category><![CDATA[Status]]></category>
		<category><![CDATA[maint_phone_20120301]]></category>

		<guid isPermaLink="false">http://blog.iweb.com/en/?p=9975</guid>
		<description><![CDATA[Update &#8211; 2012-03-09 @ 02:00 AM EST &#8211; The maintenance for the phone system has been successfully completed. In the coming hours, we will  monitor the performance and the stability of the affected services to  make sure that all is working normally.
We apologize  for any inconvenience this situation may have caused. If [...]]]></description>
			<content:encoded><![CDATA[<p>Update &#8211; 2012-03-09 @ 02:00 AM EST &#8211; The maintenance for the phone system has been successfully completed. In the coming hours, we will  monitor the performance and the stability of the affected services to  make sure that all is working normally.</p>
<p>We apologize  for any inconvenience this situation may have caused. If you have any  questions, please do not hesitate to contact our support team (http://www.iweb.com/contacts/).</p>
<p>&#8211;</p>
<p>Service affected: Phone System<br />
Start: Thursday, March 8, 2012 at 23:30 EST<br />
Maintenance duration: 2h<br />
Impact: Phone navigation menu unavailable during maintenance (calls will be directly forwarded to customer service).</p>
<p>A routine maintenance will be conducted on our phone systems in order to apply various fixes and updates. The maintenance will take place on Thursday, March 8, 2012  from 23:30 EST to 01:30 EST.</p>
<p>The phone navigation menu will be unavailable during maintenance and calls will be forwarded directly to customer service. You still will be able to contact us via the livechat or by creating a ticket in your Customer Hub.</p>
<p>Thank you for your attention.</p>
<!-- PHP 5.x --><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=SrzTH98FIxc:e7rj_J57-3Y:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=SrzTH98FIxc:e7rj_J57-3Y:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?i=SrzTH98FIxc:e7rj_J57-3Y:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/iWebBlogStatusEN/~4/SrzTH98FIxc" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.iweb.com/en/2012/03/maintenance-phone-system-4/9975.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.iweb.com/en/2012/03/maintenance-phone-system-4/9975.html</feedburner:origLink></item>
		<item>
		<title>SLA Credits: Network incident</title>
		<link>http://feedproxy.google.com/~r/iWebBlogStatusEN/~3/X0INm_MQpnw/9860.html</link>
		<comments>http://blog.iweb.com/en/2012/02/sla-credits-network-incident-2/9860.html#comments</comments>
		<pubDate>Tue, 14 Feb 2012 21:08:20 +0000</pubDate>
		<dc:creator>Stéphane Jose</dc:creator>
				<category><![CDATA[Status]]></category>
		<category><![CDATA[CC9feb]]></category>

		<guid isPermaLink="false">http://blog.iweb.com/en/?p=9860</guid>
		<description><![CDATA[Dear Customers,
As you know, we experienced a problem that affected the performance of a segment of our network from Wednesday, February 8 to Thursday, February 9, 2012.  As mentioned in our previous communications two of our distribution routers (out of a fleet of 20 routers) experienced CPU overload caused by abnormal traffic originating from [...]]]></description>
			<content:encoded><![CDATA[<p>Dear Customers,</p>
<p>As you know, we experienced a problem that affected the performance of a segment of our network from Wednesday, February 8 to Thursday, February 9, 2012.  As mentioned in our previous communications two of our distribution routers (out of a fleet of 20 routers) experienced CPU overload caused by abnormal traffic originating from one of our distribution switches. The problem is now under control and we have applied all necessary mesures to prevent this particular situation from happening again.</p>
<p>As always we are determined to meet our Service Level Agreements (<a href="http://iweb.com/legal">http://iweb.com/legal</a>). iWeb will compensate its clients with a credit equivalent to one day of service for the first 15 minutes of unavailability and a credit of one day of service for each of the following hours. The credit can be claimed up to the monthly amount paid for the service. Unavailability is defined by failed PING commands to the IP address of the server hosting your web site. This unavailability must be directly caused by problems in the connection linking iWeb Technologies Inc. to the Internet and must be verifiable from multiple external Internet hosts.</p>
<p>To file a claim, simply open a ticket in your customer-hub. Click on the product category for which you claim the credit and chose the Financials option. Follow the link entitled &#8220;SLA credit request&#8221; and fill out the form.  File a single claim for all applicable server but make sure to provide all required information for each.</p>
<p>For more information please contact a customer service representative (<a href="http://iweb.com/contact-us">http://iweb.com/contact-us</a>).</p>
<p>Sincerely,</p>
<p>The iWeb Team</p>
<p>&#8211;</p>
<p>Estimado cliente:</p>
<p>Como es de su conocimiento, tuvimos un problema que afectó el rendimiento de un segmento de nuestra red desde el miércoles 8 de febrero hasta el jueves 9 de febrero.</p>
<p>Como mencionábamos en anteriores comunicaciones, dos de nuestros routers de distribución (de un flota de 20), sufrieron una sobrecarga de CPU, provocada por un tráfico anormal procedente de un conmutador de distribución. Aplicamos las medidas y acciones correctivas que se impongan para evitar que esta situación se repita.</p>
<p>Como de costumbre, estamos decididos a cumplir con nuestros Acuerdos de nivel de servicio (http://es.iweb.com/acerca-de-nosotros). iWeb recompensará a sus clientes con un crédito equivalente a un día de servicio por los 15 primeros minutos de indisponibilidad y un credito de un día de servicio para cada una de las siguientes horas. El crédito puede ser reclamado hasta el monto mensual pagado por el servicio. La falta de acceso es definida por una respuesta « imposible » del pedido « ping » hacia la dirección IP que alberga su sitio. Esta falta de acceso debe ser causada por problemas ligados a las redes conectadas a los servidores de iWeb Technologies a Internet y debe poder constatarse a partir de varias fuentes de acceso a Internet.</p>
<p>Para hacer una reclamación, simplemente abra un ticket en su Hub cliente. Haga clic en la categoría de producto por el que reclama el crédito y seleccione la opción &#8220;Aspectos financieros&#8221;. Sigue el enlace  &#8220;Solicitud de crédito SLA&#8221; y rellene el formulario. Presente un solo reclamo por todos los servidores aplicables, pero asegúrese de proporcionar toda la información requerida por cada uno.</p>
<p>Para más información póngase en contacto con un representante de servicio al cliente (<a href="http://es.iweb.com/contactos">http://es.iweb.com/contactos</a>).</p>
<p>Atentamente:</p>
<p>El equipo de iWeb </p>
<!-- PHP 5.x --><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=X0INm_MQpnw:olAnL5yK09c:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=X0INm_MQpnw:olAnL5yK09c:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?i=X0INm_MQpnw:olAnL5yK09c:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/iWebBlogStatusEN/~4/X0INm_MQpnw" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.iweb.com/en/2012/02/sla-credits-network-incident-2/9860.html/feed</wfw:commentRss>
		<slash:comments>9</slash:comments>
		<feedburner:origLink>http://blog.iweb.com/en/2012/02/sla-credits-network-incident-2/9860.html</feedburner:origLink></item>
		<item>
		<title>Maintenance: Control Center [Resolved]</title>
		<link>http://feedproxy.google.com/~r/iWebBlogStatusEN/~3/0rBq97IiA04/9847.html</link>
		<comments>http://blog.iweb.com/en/2012/02/maintenance-control-center-6/9847.html#comments</comments>
		<pubDate>Tue, 14 Feb 2012 19:35:31 +0000</pubDate>
		<dc:creator>Stéphane Jose</dc:creator>
				<category><![CDATA[Status]]></category>
		<category><![CDATA[CC_20120215]]></category>

		<guid isPermaLink="false">http://blog.iweb.com/en/?p=9847</guid>
		<description><![CDATA[Update: 03:00 EST &#8211; Maintenance was successfully completed and took only 3 hours. All services are now up and running. If you have any questions please contact our technical support team (http://www.iweb.com/contacts/). 
&#8211;
Service affected: Control Center
Start: between 00:00 EST and 6:00 EST on Wednesday, February 15, 2012
Maintenance duration: 6 hrs.
Impact: Control Center unavailable  during [...]]]></description>
			<content:encoded><![CDATA[<p>Update: 03:00 EST &#8211; Maintenance was successfully completed and took only 3 hours. All services are now up and running. If you have any questions please contact our technical support team (http://www.iweb.com/contacts/). </p>
<p>&#8211;</p>
<p>Service affected: Control Center<br />
Start: between 00:00 EST and 6:00 EST on Wednesday, February 15, 2012<br />
Maintenance duration: 6 hrs.<br />
Impact: Control Center unavailable  during the maintenance. </p>
<p>We will conduct an emergency maintenance on our network, which will affect the Control Center between 00:00 EST and 6:00 EST on Wednesday, February 15, 2012. The Control Center will be unavailable during the maintenance period, but access to the servers of our clients and their websites will not be affected.</p>
<p>If you have any questions, or need to open a support ticket during this period, please contact our technical support team via the livechat or by phone (http://www.iweb.com/contacts/). </p>
<p>We apologize for any inconvenience this may have caused. We appreciate your patience and your understanding.</p>
<!-- PHP 5.x --><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=0rBq97IiA04:DUH7fJiJGdg:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=0rBq97IiA04:DUH7fJiJGdg:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?i=0rBq97IiA04:DUH7fJiJGdg:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/iWebBlogStatusEN/~4/0rBq97IiA04" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.iweb.com/en/2012/02/maintenance-control-center-6/9847.html/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://blog.iweb.com/en/2012/02/maintenance-control-center-6/9847.html</feedburner:origLink></item>
		<item>
		<title>Maintenance: electrical equipment of iWeb-CO [Resolved]</title>
		<link>http://feedproxy.google.com/~r/iWebBlogStatusEN/~3/5Px3m9s_-Pc/9843.html</link>
		<comments>http://blog.iweb.com/en/2012/02/maintenance-electrical-equipment-iweb-co/9843.html#comments</comments>
		<pubDate>Tue, 14 Feb 2012 14:46:32 +0000</pubDate>
		<dc:creator>Stéphane Jose</dc:creator>
				<category><![CDATA[Status]]></category>
		<category><![CDATA[maint-elec-CO-20120215]]></category>

		<guid isPermaLink="false">http://blog.iweb.com/en/?p=9843</guid>
		<description><![CDATA[Service affected: Electrical equipment of iWeb-CO
Start: Wednesday, February 15, 2012 from 6:00 am EST to 15:00 EST
Maintenance duration: 9h
Impact: No impact is anticipated.
Following the maintenance conducted two weeks ago, we will proceed  with minor work on the Nun&#8217;s Island iWeb-CO building&#8217;s electrical systems on Wednesday, February 15, 2012  from 6:00 am EST to [...]]]></description>
			<content:encoded><![CDATA[<p>Service affected: Electrical equipment of iWeb-CO<br />
Start: Wednesday, February 15, 2012 from 6:00 am EST to 15:00 EST<br />
Maintenance duration: 9h<br />
Impact: No impact is anticipated.</p>
<p>Following the maintenance conducted two weeks ago, we will proceed  with minor work on the Nun&#8217;s Island iWeb-CO building&#8217;s electrical systems on Wednesday, February 15, 2012  from 6:00 am EST to 15:00 EST.</p>
<p>A series of control tests of our systems will be held in the afternoon from 13:00 EST that will cause a short loss of power in the building.</p>
<p>Again, no impact will be felt by our colocation customers hosted on the 3rd floor, as UPS and generators will ensure their protection.</p>
<p>Thank you for your attention.</p>
<!-- PHP 5.x --><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=5Px3m9s_-Pc:zsbbw3Edi-8:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=5Px3m9s_-Pc:zsbbw3Edi-8:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?i=5Px3m9s_-Pc:zsbbw3Edi-8:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/iWebBlogStatusEN/~4/5Px3m9s_-Pc" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.iweb.com/en/2012/02/maintenance-electrical-equipment-iweb-co/9843.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.iweb.com/en/2012/02/maintenance-electrical-equipment-iweb-co/9843.html</feedburner:origLink></item>
		<item>
		<title>Post Mortem: Network Infrastructure Incident</title>
		<link>http://feedproxy.google.com/~r/iWebBlogStatusEN/~3/rXqtMVY31FI/9830.html</link>
		<comments>http://blog.iweb.com/en/2012/02/post-mortem-network-incident/9830.html#comments</comments>
		<pubDate>Fri, 10 Feb 2012 22:05:58 +0000</pubDate>
		<dc:creator>iWeb Technologies</dc:creator>
				<category><![CDATA[Status]]></category>
		<category><![CDATA[CC9feb]]></category>

		<guid isPermaLink="false">http://blog.iweb.com/en/?p=9830</guid>
		<description><![CDATA[EN &#8211; ES

We experienced a problem that affected the performance of a segment of our network from Wednesday, February 8 to Thursday, February 9.
As of 10:30 PM EST,  Wednesday evening, two of our distribution routers (on a fleet of 20 routers) experienced CPU overload caused by abnormal traffic originating from one of our distribution switches.
We found that this abnormal traffic was received on specific ports and that the percentage of CPU utilization rose rapidly to 100%. We worked with the manufacturer to determine the exact nature of this traffic and once identified it was blocked in order [...]]]></description>
			<content:encoded><![CDATA[<p><strong><a href="#en">EN</a> &#8211; <a href="#es">ES</a></strong></p>
<p><a name="en"></a><br />
We experienced a problem that affected the performance of a segment of our network from Wednesday, February 8 to Thursday, February 9.</p>
<p>As of 10:30 PM EST,  Wednesday evening, two of our distribution routers (on a fleet of 20 routers) experienced CPU overload caused by abnormal traffic originating from one of our distribution switches.</p>
<p>We found that this abnormal traffic was received on specific ports and that the percentage of CPU utilization rose rapidly to 100%. We worked with the manufacturer to determine the exact nature of this traffic and once identified it was blocked in order to restore connectivity.</p>
<p>Connectivity for servers connected to these routers was gradually restored starting at around 4:00 AM EST. Thursday morning, 90% of affected servers were again accessible. At about 5:00 PM EST, network connectivity to all servers was finally restored.</p>
<p>We continue to investigate the problem with the manufacturer and maintenance will be performed next week to implement the corrective actions necessary to prevent this situation from happening again.</p>
<p>This incident did not cause any data loss for customers and no server hardware has been affected. LAN connectivity was also maintained at all times.</p>
<p>The network is now stable and we are closely monitoring its performance.</p>
<p>We apologize for any inconvenience this may have caused.</p>
<p>We appreciate your patience and your understanding.</p>
<p>&#8211;<br />
<a name="es"></a></p>
<p>Tuvimos un problema que afectó el rendimiento de un segmento de nuestra red desde el miércoles 8 de febrero hasta el jueves 9 de febrero.</p>
<p>Desde las 22.30 hs. (tiempo del este) del miércoles, dos de nuestros routers de distribución (de un flota de 20), sufrieron una sobrecarga de CPU, provocada por un tráfico anormal procedente de un conmutador de distribución.</p>
<p>Pudimos constatar que este tráfico anormal fue recibido en ciertos puertos y que el porcentaje de uso del CPU subió rápidamente hasta alcanzar el 100%.  Trabajamos con el fabricante para determinar la causa exacta del este tráfico y después de haberlo identificarlo, lo bloqueamos con el fin de restaurar la conectividad.</p>
<p>La conectividad de los servidores relacionados con estos routers fue gradualmente restablecida y hacia las 4.00 hs. (tiempo del este), 90% de los servidores afectados ya se encontraban accesibles.  Sobre las 17.00 hs. (tiempo del este), la conectividad de todos los servidores fue restablecida.</p>
<p>Seguimos estudiando el problema con el fabricante y un mantenimiento se llevará a cabo la semana que viene para aplicar las medidas y acciones correctivas que se impongan para evitar que esta situación se repita.</p>
<p>El incidente no provocó ninguna pérdida de datos de clientes y ningún servidor fue afectado a nivel de hardware.</p>
<p>La red ha recuperado su estabilidad y estamos monitoreando su rendimiento.</p>
<!-- PHP 5.x --><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=rXqtMVY31FI:3mws76rZMGM:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=rXqtMVY31FI:3mws76rZMGM:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?i=rXqtMVY31FI:3mws76rZMGM:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/iWebBlogStatusEN/~4/rXqtMVY31FI" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.iweb.com/en/2012/02/post-mortem-network-incident/9830.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.iweb.com/en/2012/02/post-mortem-network-incident/9830.html</feedburner:origLink></item>
		<item>
		<title>Maintenance: Control Center [Resolved]</title>
		<link>http://feedproxy.google.com/~r/iWebBlogStatusEN/~3/lQgRXZ-AJn8/9797.html</link>
		<comments>http://blog.iweb.com/en/2012/02/maintenance-control-center-5/9797.html#comments</comments>
		<pubDate>Thu, 09 Feb 2012 17:49:13 +0000</pubDate>
		<dc:creator>Stéphane Jose</dc:creator>
				<category><![CDATA[Status]]></category>
		<category><![CDATA[CC9feb]]></category>

		<guid isPermaLink="false">http://blog.iweb.com/en/?p=9797</guid>
		<description><![CDATA[Update 16:20 EST: Maintenance is now over. Control Center is available again.  If  you have any questions, or need to open a support ticket, please contact our technical support team via the  customer hub (http://hub.iweb.com/contacts/). Thank you for your patience and your understanding.
&#8211;
Update 16:00 EST: Maintenance is still ongoing. Next update at [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Update 16:20 EST: Maintenance is now over. Control Center is available again.  If  you have any questions, or need to open a support ticket, please contact our technical support team via the  customer hub (http://hub.iweb.com/contacts/). Thank you for your patience and your understanding.</strong></p>
<p>&#8211;</p>
<p>Update 16:00 EST: Maintenance is still ongoing. Next update at approximately 16:30EST.</p>
<p><strong>&#8211;<br />
</strong></p>
<p>Update 15:30 EST: Maintenance is still ongoing. Next update at approximately 16:00 EST.</p>
<p>&#8211;</p>
<p>Update 14:35 EST: Maintenance is still ongoing due to unforeseen issues. Next update at approximately  15:30 EST.</p>
<p>&#8211;</p>
<p>Update 13:45 EST: Maintenance will take an extra 20 minutes. Thank you for your attention.</p>
<p>&#8211;</p>
<p>Service affected: Control Center<br />
Start: Thursday, February 9 at 12h45 EST<br />
Maintenance duration: 60 min.<br />
Impact: Control Center unavailable  during the maintenance.<span style="text-decoration: line-through;"><br />
</span></p>
<p>An emergency  maintenance is being conducted on our systems, which will affect the   Control  Center on Thursday, February 9 at 12:45 EST in order to apply new network configurations.</p>
<p>The  Control Center  will be inaccessible  during this 60 minutes  maintenance period. Access to the servers of  our clients and their websites will NOT be affected.<span style="text-decoration: line-through;"><br />
</span></p>
<p>If  you have any questions, or need to open a support ticket during   this  period, please contact our technical support team via the livechat   or  by phone (http://www.iweb.com/contacts/).</p>
<p>Thank you for your attention.</p>
<!-- PHP 5.x --><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=lQgRXZ-AJn8:AdD_pHIK1lo:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=lQgRXZ-AJn8:AdD_pHIK1lo:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?i=lQgRXZ-AJn8:AdD_pHIK1lo:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/iWebBlogStatusEN/~4/lQgRXZ-AJn8" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.iweb.com/en/2012/02/maintenance-control-center-5/9797.html/feed</wfw:commentRss>
		<slash:comments>44</slash:comments>
		<feedburner:origLink>http://blog.iweb.com/en/2012/02/maintenance-control-center-5/9797.html</feedburner:origLink></item>
		<item>
		<title>Incident: Network infrastructure (Smart Servers) [Resolved]</title>
		<link>http://feedproxy.google.com/~r/iWebBlogStatusEN/~3/ChZRUV3-i0E/9769.html</link>
		<comments>http://blog.iweb.com/en/2012/02/incident-network-infrastructure-14/9769.html#comments</comments>
		<pubDate>Thu, 09 Feb 2012 04:18:56 +0000</pubDate>
		<dc:creator>iWebstaff</dc:creator>
				<category><![CDATA[Status]]></category>
		<category><![CDATA[Incident_(network)_20120208]]></category>

		<guid isPermaLink="false">http://blog.iweb.com/en/?p=9769</guid>
		<description><![CDATA[
Update 09/02/2012 17:40  EST &#8211; The incident affecting our network network is now resolved. Note that a few servers are still experiencing connectivity issues. As these problems are not necessarily connected to the network outage we experienced, we must investigate them manually one by one. If you have already created a ticket, there is [...]]]></description>
			<content:encoded><![CDATA[<div id="gt-res-content">
<div dir="ltr"><strong>Update 09/02/2012 17:40  EST &#8211; The incident affecting our network network is now resolved. Note that a few servers are still experiencing connectivity issues. As these problems are not necessarily connected to the network outage we experienced, we must investigate them manually one by one. If you have already created a ticket, there is no need to create a new one, our sysadmins will give you an update directly. You can also followp on your ticket directly by replying to it by email.</strong></div>
<div dir="ltr"><strong><br />
To open a new ticket please use the &#8220;Server Unavailable&#8221; option in your customer hub (hub.iweb.com) so a sysadmin can follow up directly with you. When you create a ticket, it </strong><strong>currently </strong><strong>will not be displayed in the customer hub. Do not worry, we have it in our system.The response time on the chat and on the phone is also back to more normal levels.</p>
<p>A more detailed technical update will also be published in the next 24-48h following our postmortem.</p>
<p></strong><strong>Thank you again for your patience and your understanding.</strong></p>
</div>
<div dir="ltr"><strong><br />
</strong></div>
</div>
<p>&#8211;</p>
<p>Update 2012-02-09 16:15 EST &#8211; Number of servers still affected is now down to less that 20. VLANs of affected servers had to be reconfigured and IP addressing had to be corrected on some servers. Next update at 17:00 EST<strong><br />
</strong></p>
<p><strong>&#8211;<br />
</strong></p>
<p>Update 2012-02-09 15:35 EST -We have made some progress as more affected servers are now accessible. We came down to about 150 servers still unreachable. Our network admins are still working on adjusting network configurations to provide our clients with a permanent solution. Next status update will be published at approx 16:15 EST.</p>
<p><strong>&#8211;<br />
</strong></p>
<p>Update 2012-02-09 14:45 EST &#8211; An emergency network maintenance is currently ongoing in order to apply new network configurations (<a href="http://blog.iweb.com/en/2012/02/maintenance-control-center-5/9797.html">http://blog.iweb.com/en/2012/02/maintenance-control-center-5/9797.html</a>). We expect this will help alleviate the connectivity problems still affecting approximately 450 servers. Next status update will be published at 15:30EST .<strong><br />
</strong></p>
<p>&#8211;</p>
<p><strong><a href="#en">EN</a> &#8211; <a href="#es">ES</a></strong></p>
<p><a name="en"></a><br />
Update 2012-02-09 12:20 EST- 90% of IP addressing and traffic on our NE datacenter (Smart Servers) are back     to normal.</p>
<p>For those still having difficulties accessing their servers or     websites, we advise you to perform the following actions in order to re-establish your services since they have been sucessfull with     customers.</p>
<p>1. Determine if you can access your server via ssh</p>
<p>2. Perform a DNS query to reestablish ARP (Address Resolution     Protocol)</p>
<ul>
<li>logon to server via ssh using  public IP (do not use domain name)</li>
<li> attempt to ping any public website, such as google.com</li>
</ul>
<p>3. Attempt to restart services and network</p>
<ul>
<li> Restart any unresponsive services</li>
<li> then restart network by typing the following commands:</li>
</ul>
<p style="padding-left: 30px;">CentOS: service network restart OR /etc/init.d/network restart<br />
Debian/Ubuntu: /etc/init.d/networking restart</p>
<p>If these actions are unsuccessful, please log a &#8220;server not working &#8221; ticket in the customer hub, if you have not already created one.</p>
<p>When you create a ticket it will not show up in the customer hub at     the moment. But do not worry we have it in our system. If you     already created a ticket for the ongoing issue please do not create     a new one.</p>
<p>We remind you that due to the greater amount of tickets to be     treated, the response time on the chat and the phone is slower than     normal.</p>
<p>&#8211;<br />
<a name="es"></a><br />
Actualización 2012&#8242;02009 12:20 ET &#8211; El 90% de los IPS y del     trafico sobre nuestro centro de datos NE (Servidores Smart) es     devuelta a la normalidad.</p>
<p>Para aquellos que siguen teniendo dificultades al acceder a sus     servidores u sitios web, aconsejamos que usted ejecute las     siguientes acciónes para restaurar sus servicios, ya que esto ha     sido exitoso para muchos clientes.</p>
<p>1. Determine si puede accesar a su servidor a travez de SSH.</p>
<p>2. Ejecute una demanda DNS para restablecer la ARP (Address     Resolution Protocol- Protocolo de la resolución de direcciónes)</p>
<p>-contactese al servidor via ssh usando la IP publica (no use el     nombre de dominio)<br />
-intente hacer un ping a cualquier sitio web,  por ejemplo <a href="http://google.com/" target="_blank">google.com</a></p>
<p>3. Intente reiniciar los servicios de red en ejecutando el comando     siguiente:<br />
-Para un servidor CentOS: service network restart<br />
-Para un servidor Debian/Ubuntu: /etc/init.d/networking restart</p>
<p>Si estas acciónes han fracazado, por favor haga un ticket &#8220;Servidor     fuera de uso&#8221; via el Hub Cliente unicamente si usted todavia no ha     creado uno.<br />
Cuando usted cree el ticket, este no sera mostrado en el Hub Cliente     por el momento. Usted no debe preocuparse, lo tenemos en nuestro     sistema.</p>
<p>Si usted ya ha creado el ticket para este problema, por favor no     cree nuevos tickets.</p>
<p>Le recordamos que debido a un gran numero de ticket que estan en     espera de ser tratados, la respuesta al chat es mas lenta que de     costumbre.</p>
<p>&#8211;</p>
<p>Update 2012-02-09 9:00 AM EST -We are currently investigating a problem with DNS resolving that affects some of our clients. Still no ETA. Thanks again for your patience.<strong><br />
</strong></p>
<p>Due to the greater amount of tickets to be treated, the response time on the chat and the phone is slower than normal.</p>
<p>Thank you for your patience.</p>
<p>&#8211;</p>
<p><span style="color: #000000;">Update 2012-02-09 8:00 AM </span>EST <span style="color: #000000;">- When  you create a ticket it will not show up in the customer hub at the  moment. But do not worry we have it in our system. If you already  created a ticket for the ongoing issue please do not create a new one. </span></p>
<p>&#8211;</p>
<p>Update 2012-02-09 7:00 AM EST we are waiting for another update from our network team. Due to the greater amount of tickets to be treated, the response time on the chat and the phone is slower than normal.</p>
<p>Thank you for your patience.</p>
<p>&#8211;</p>
<p>Update 2012-02-09 5:00 AM EST: Networking issue is now stable in our datacenter.</p>
<p>If you still encounter issues on the server side please do the following:</p>
<p>restart all unresponsive services</p>
<p>ping your personalized NS (ns1.yourdomain.com and ns2.yourdomain.com) if your server is the DNS authority</p>
<p>then type commands:</p>
<p>CentOS: service network restart OR /etc/init.d/network restart</p>
<p>Debian/Ubuntu: /etc/init.d/networking restart</p>
<p>If it still do not work for you, we invite you to open a ticket in the &#8220;Server unreachable&#8221; section of your Customer Hub (hub.iweb.com) so a sysadmin can follow up directly with you.</p>
<p>&#8211;</p>
<p>Update 2012-02-09 4:10 AM EDT:Network team had to reboot several routers on NE datacenter. Some Smart Servers will be unavailable for a few minutes. Thank you for your patience.</p>
<p>&#8211;</p>
<p>Update 2012-02-09 3:30 AM EST: A minority of clients may still experience some connectivity issues. For those still having problems please mention your server ID on our live chat and an agent will do additional verifications.</p>
<p>&#8211;</p>
<p>Update 2012-02-09 2:50 AM EST: The Network is now fully functionnal and all services, <span style="text-decoration: underline;"> except Ping</span>, are up and running so you might temporailiy receive false positive monitoring alerts although all affected Smart Servers are now accessible. The Our network team will investigate the problem and we should be able to post a more complete description of the incident later on today.</p>
<p>&#8211;</p>
<p>Update 2012-02-09 1:25 AM EST: This incident is affecting a segment of our Smart Server network and all Classic servers are not being affected by this issue. Our network team is still working on the problem.</p>
<p>&#8211;</p>
<p>Start: 2012-02-09 11:00 PM EST<br />
Estimated time of resolution: N/A<br />
Impact:  Some servers from our NE datacenter</p>
<p>We are currently investigating a situation that might affect a segment of our network infrastructure.<br />
Our technical  team is actively working on finding a solution to this  problem. We  will regularly communicate with you about the status of this operation.<br />
We apologize for any inconvenience this situation may cause. If you have any questions, please do not hesitate to contact our support team (http://www.iweb.com/contacts/).</p>
<p>Thank you for your patience  and  understanding.</p>
<!-- PHP 5.x --><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=ChZRUV3-i0E:RfdNcUr9x2k:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=ChZRUV3-i0E:RfdNcUr9x2k:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?i=ChZRUV3-i0E:RfdNcUr9x2k:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/iWebBlogStatusEN/~4/ChZRUV3-i0E" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.iweb.com/en/2012/02/incident-network-infrastructure-14/9769.html/feed</wfw:commentRss>
		<slash:comments>860</slash:comments>
		<feedburner:origLink>http://blog.iweb.com/en/2012/02/incident-network-infrastructure-14/9769.html</feedburner:origLink></item>
		<item>
		<title>Maintenance: Control Center [Resolved]</title>
		<link>http://feedproxy.google.com/~r/iWebBlogStatusEN/~3/RbMGmHWzMck/9702.html</link>
		<comments>http://blog.iweb.com/en/2012/01/maintenance-control-center-4/9702.html#comments</comments>
		<pubDate>Fri, 27 Jan 2012 20:47:58 +0000</pubDate>
		<dc:creator>Stéphane Jose</dc:creator>
				<category><![CDATA[Status]]></category>
		<category><![CDATA[maintenance_CC_20120131]]></category>

		<guid isPermaLink="false">http://blog.iweb.com/en/?p=9702</guid>
		<description><![CDATA[Update: 2012/01/31 9:00 EST -  Maintenance was successful. All services are now up and running.
&#8211;
Service affected: Control Center / Customer Hub
Start: Tuesday, January 31 between 8:00 and 9:30 EST
Maintenance duration: 90 min.
Impact: Control Center unavailable  during the maintenance. Customer Hub may temporarily display random blank pages.

A  maintenance is planned on our systems, which will [...]]]></description>
			<content:encoded><![CDATA[<p>Update: 2012/01/31 9:00 EST -  Maintenance was successful. All services are now up and running.</p>
<p>&#8211;</p>
<p>Service affected: Control Center / Customer Hub<br />
Start: Tuesday, January 31 between 8:00 and 9:30 EST<br />
Maintenance duration: 90 min.<br />
Impact: Control Center unavailable  during the maintenance. Customer Hub may temporarily display random blank pages.<span style="text-decoration: line-through;"><br />
</span></p>
<p>A  maintenance is planned on our systems, which will affect the  Control  Center and the Customer-hub, Tuesday, January 31, 2012 at  08:00 EST.</p>
<p>The  Control Center  will be inaccessible and the Customer Hub Customer Hub  may temporarily display random blank pages during this 90 minutes  maintenance period.<br />
Access to the servers of  our clients and their websites will not be affected.<span style="text-decoration: line-through;"><br />
</span></p>
<p>If  you have any questions, or need to open a support ticket during  this  period, please contact our technical support team via the livechat  or  by phone (http://www.iweb.com/contacts/).</p>
<p>Thank you for your attention.</p>
<!-- PHP 5.x --><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=RbMGmHWzMck:UAEkE-3Jb1s:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=RbMGmHWzMck:UAEkE-3Jb1s:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?i=RbMGmHWzMck:UAEkE-3Jb1s:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/iWebBlogStatusEN/~4/RbMGmHWzMck" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.iweb.com/en/2012/01/maintenance-control-center-4/9702.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.iweb.com/en/2012/01/maintenance-control-center-4/9702.html</feedburner:origLink></item>
		<item>
		<title>Maintenance: electrical equipments on iWeb-CO [Resolved]</title>
		<link>http://feedproxy.google.com/~r/iWebBlogStatusEN/~3/xNC5cwTCjQY/9675.html</link>
		<comments>http://blog.iweb.com/en/2012/01/maintenance-electrical-equipments-on-iweb-co/9675.html#comments</comments>
		<pubDate>Tue, 24 Jan 2012 13:08:17 +0000</pubDate>
		<dc:creator>Stéphane Jose</dc:creator>
				<category><![CDATA[Status]]></category>
		<category><![CDATA[maint_elect_CO-20120125]]></category>

		<guid isPermaLink="false">http://blog.iweb.com/en/?p=9675</guid>
		<description><![CDATA[
Update: Maintenance was successfuly conducted. All systems are now powered normally.

&#8211;

Update : Maintenance will now be conducted on Thursday, January 26 and Friday, January 27.


&#8211;
Update: we must postpone the maintenance to a later date. A new date will be announced on this blog as soon as possible. Thank you for your attention.


&#8211;

Service affected: Electrical equipments [...]]]></description>
			<content:encoded><![CDATA[<div id="gt-res-content">
<div dir="ltr">Update: Maintenance was successfuly conducted. All systems are now powered normally.</div>
<div dir="ltr"></div>
<div dir="ltr">&#8211;</div>
<div dir="ltr"></div>
<div dir="ltr">Update : Maintenance will now be conducted on Thursday, January 26 and Friday, January 27.</div>
<div dir="ltr"><strong><br />
</strong></div>
<div dir="ltr">&#8211;</div>
<div dir="ltr">Update: we must postpone the maintenance to a later date. A new date will be announced on this blog as soon as possible. Thank you for your attention.</div>
<div dir="ltr"><strong><br />
</strong></div>
<div dir="ltr">&#8211;</div>
</div>
<p>Service affected: Electrical equipments on iWeb-CO datacenter<br />
Start: <span style="text-decoration: line-through;">Wednesday, January 25, 2012 from 7:00 EST</span> Thursday, January 26, 2012 from 7:00 EST<br />
Maintenance duration: 48 hours<br />
Impact: No impact is expected.</p>
<p>To maintain and improve the reliability of the infrastructure supporting our iWeb-CO datacenter colocation facility (Nun&#8217;s Island), work on the electrical equipment will be conducted <span style="text-decoration: line-through;">on Wednesday, January 25 and Thursday, January 26</span> Thursday, January 26 and Friday, January 27, 2012.</p>
<p>For the duration of the maintenance, our facilities will be powered by either of our power generators and no impact is expected for our customers.</p>
<p>If you have any questions, please contact our technical support team (http://www.iweb.com/contacts/).</p>
<p>Thank you for your patience and your understanding.</p>
<!-- PHP 5.x --><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=xNC5cwTCjQY:ljWJ4v5RduU:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?a=xNC5cwTCjQY:ljWJ4v5RduU:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/iWebBlogStatusEN?i=xNC5cwTCjQY:ljWJ4v5RduU:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/iWebBlogStatusEN/~4/xNC5cwTCjQY" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blog.iweb.com/en/2012/01/maintenance-electrical-equipments-on-iweb-co/9675.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.iweb.com/en/2012/01/maintenance-electrical-equipments-on-iweb-co/9675.html</feedburner:origLink></item>
	</channel>
</rss>

