<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hosting on Lagomorph</title><link>https://lagomor.ph/tags/hosting/</link><description>Recent content in Hosting on Lagomorph</description><generator>Hugo</generator><language>en</language><copyright>Alex S.</copyright><lastBuildDate>Tue, 04 Aug 2026 13:52:00 +0900</lastBuildDate><atom:link href="https://lagomor.ph/tags/hosting/index.xml" rel="self" type="application/rss+xml"/><item><title>Do not use OVHcloud for production services</title><link>https://lagomor.ph/indieweb/20260804/1352-note/</link><pubDate>Tue, 04 Aug 2026 13:52:00 +0900</pubDate><guid>https://lagomor.ph/indieweb/20260804/1352-note/</guid><description>&lt;h2 id="summary"&gt;Summary&lt;/h2&gt;
&lt;p&gt;Two failures of OVHcloud&amp;rsquo;s control plane took a single VPS offline within four days. Neither originated inside the guest. Neither could be fully resolved by the account holder.&lt;/p&gt;
&lt;p&gt;In the first incident, OVHcloud&amp;rsquo;s automated backup issued a filesystem freeze through &lt;code&gt;qemu-guest-agent&lt;/code&gt; and did not complete the corresponding thaw. All processes that performed disk I/O entered uninterruptible sleep. OVHcloud simultaneously locked the service in the state &lt;code&gt;backuping&lt;/code&gt;. The Control Panel and API then refused reboot, stop, and start operations with &lt;code&gt;Action not available while VPS is backuping&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>