OVH Failure Exposes Weak Backbones: Lemmy Forces Migration Away From Hosting Giant
Lemmy.ca suffered a major hardware failure on January 5th/6th, taking 26 hours to resolve due to a physical power supply issue at its hosting vendor, OVH. This prolonged downtime directly triggered the decision to plan a migration to self-controlled, enterprise-grade hardware.
The community discourse splits over the critique. Some users, like 'AceTKen', viciously attacked the 24hr service as 'pretty piss-poor.' Others, such as 'Shadow', point to the concrete record of the 26-hour recovery time and criticize the basic infrastructure failure. While some point to OVH's affordable pricing, former staff cited professional anecdotes detailing support limitations, fueling the discontent.
The overwhelming sentiment demands shedding OVH. The failure of a simple power supply, requiring such extensive downtime, leads the community to a firm conclusion: the platform requires direct control over its hardware to guarantee uptime, making the migration a perceived necessity, not an option.
Key Points
OVH failed to keep the service up after a power supply failure.
The Jan 5th incident required 26 hours for a physical fix, suggesting basic operational failure.
The support provided by OVH was incompetent.
Accusations range from 'pretty piss-poor' 24hr service to systemic support shortcomings.
The migration to self-owned hardware is necessary for stability.
The move is framed as giving Lemmy 'a HUGE boost in server resources' and crucial control over recovery.
OVH's general performance is declining over time.
Users like 'Skyline969' flagged the history of service credits due to recurring downtime.
The 24-hour response time is suspect.
User 'adeapoton' questioned the narrative around the initial outage repair time against claims of poor support.
Source Discussions (4)
This report was synthesized from the following Lemmy discussions, ranked by community score.