Questions we get,answered straight.

OVHcloud datacentre RBX9, in Gravelines, France (51.01°N 2.13°E). Encrypted daily backups are held in Strasbourg, off the primary site. There is one primary node today; a second operational node and a separate backup node are being implemented, and the failover design is written down.

Managed hosting and managed SMTP, measured quarterly, and written into the terms with a stated remedy. It is not the same number as the measured uptime on the status page. That figure answers a different question, and the two are kept apart on purpose.

The primary node goes down with it, and the status page says so. There is no automatic multi-region failover, and we will not pretend there is. The failover design is documented, the backups are off-site and tested, and a named person is on call to restore or fail over on a schedule you will see in writing.

No, on purpose. We operate one well-understood node and would rather tell you that than promise a cluster we cannot run well. If your workload genuinely needs multi-region active-active, that is a different shop, and we will say so and point you there.

The named on-call person, and you. Source, runbooks, DNS, and the accounts stay yours throughout the engagement. You are never locked to the person who built it.

Within 48 hours, and the reply is S/MIME-signed so you can verify it came from us and not from someone who bought a lookalike domain.

Bulk or cold marketing mail, autonomous agents with no human in the loop, training foundation models, training on your data, rescue work on a codebase nobody will let us change, and multi-region failover. The full list is on the capabilities page, and it is the most useful part of the site.

It is quoted after we have read your brief and looked at what exists. A signed scope fixes its price. There are no retainers with no defined output, and if the honest answer is that you should change nothing, that is a valid result and you still get the document.