Public testing phase We’re in a public testing phase — feel free to look around, but we’re not taking orders yet. Ordering opens 1 October 2026. See plans →

Uptime, the status page and the SLA

We publish how the platform is doing, live, at veldhost.eu/status — five components (web hosting, control panel & API, DNS, email, backups), each measured every five minutes, with 90-day history bars and a measured uptime percentage. Grey means "no data", never "we'd rather not say".

What we commit to

  • Starter — best-effort operation. We run everything with the same care, but there's no contractual uptime figure.
  • Pro — a 99.5% monthly availability target for your production site.
  • Business — a 99.9% monthly target on a confirmed dedicated setup, backed by service credits: 10% of the monthly fee below 99.9%, 25% below 99.0%, 50% below 95.0% (capped at one month, claim within 30 days of the affected month).

The full, legally binding version — including what counts as downtime and what's excluded — is the Hosting SLA. Credits never limit your statutory rights.

How downtime is counted

Availability is measured monthly against your production site's public endpoint. A blip only counts as downtime after at least two consecutive failed checks and five minutes of continuous unavailability — so a single dropped request doesn't start a stopwatch, and neither does maintenance we announced in advance.

If something breaks

Platform-wide issues appear on the status page; anything affecting just your site shows in your dashboard's Monitoring section, in plain language. You never need to email us to find out whether it's us or you — but you can always contact support.

Subscribe to status updates

You do not have to keep the status page open. At the bottom of veldhost.eu/status you can leave an email address; we send one confirmation link first (double opt-in) and, once confirmed, an email each time a platform incident is opened and again when it is resolved. Every email has a one-click unsubscribe link and nothing else is ever sent to that address.

Prefer a feed reader or want to pipe it into Slack? There is an Atom feed at /status/feed.atom — one entry per incident update, newest first, never served from cache. Sites with a public status page have the same two options on their own page: a subscribe box and /status/<site>/feed.atom.