L'esperienza di Lettermint.co con OVHcloud:

Some incidents were acknowledged late. Some were never clearly acknowledged. Some only appeared on the status page after customers had already been impacted for hours (or even days!).

A few examples (these are the ones we shared with the OVH team):

  • Feb 23, 2025: unable to create nodes for a full day (Keystone errors, 500s).
  • Mar 26, 2025: node timeouts in GRA11, never properly acknowledged.
  • Apr 8, 2025: BYOIP issue where Microsoft services were unreachable.
  • Apr 11, 2025: major production incident, multiple nodes down. Support replied 11 days later.
  • Apr–May 2025: recurring DNS issues (even domains like Stripe intermittently failed to resolve).
  • Aug 27, 2025: unannounced cluster updates → replication issues → data corruption → restore from backup.
  • Sep 2, 2025: ~2.5 hours downtime across the entire region due to Keystone (an OpenStack service they use).
  • Sep 10, 2025: another outage (~30+ minutes).
  • Oct 2025: CEPH/block storage instability and Kubernetes API issues.
  • Nov 2025 onward (3-AZ Paris): Object Storage problems begin.
  • Dec 2025 – Apr 2026: repeated S3 timeouts and 503s for months.
  • Feb 5, 2026: OVHcloud restarted all nodes at once (PDB ignored).
  • Mar 5, 2026: similar issue again.