<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Maintenance and incidents on wallabag.it</title><link>https://deploy-preview-54--wallabagit-website.netlify.app/en/blog/maintenance/</link><description>Recent content in Maintenance and incidents on wallabag.it</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 22 Dec 2016 00:00:00 +0000</lastBuildDate><atom:link href="https://deploy-preview-54--wallabagit-website.netlify.app/en/blog/maintenance/index.xml" rel="self" type="application/rss+xml"/><item><title>All wallabag.it websites unavailable on December, 22 during 8 hours</title><link>https://deploy-preview-54--wallabagit-website.netlify.app/en/blog/2016/12/22/all-wallabag.it-websites-unavailable-on-december-22-during-8-hours/</link><pubDate>Thu, 22 Dec 2016 00:00:00 +0000</pubDate><guid>https://deploy-preview-54--wallabagit-website.netlify.app/en/blog/2016/12/22/all-wallabag.it-websites-unavailable-on-december-22-during-8-hours/</guid><description>&lt;p&gt;On December, 21 at 22pm (Paris time), our server didn’t respond. Our monitoring service alerted us and our websites were available quickly (websites were down for 17 minutes and 7 seconds).&lt;/p&gt;
&lt;p&gt;Few minutes later, new downtime. When our server restarted, websites were still unavailable and our users saw this page:&lt;/p&gt;
&lt;p&gt;The problem wasn’t detected immediatly and we saw it (thanks to some users on our Twitter account), we restarted our web server and all was OK at 8am (Paris time).&lt;/p&gt;</description></item></channel></rss>