Status

A live status widget is rendered at the top of this page. The page pulls it from our /api/status endpoint and shows four signals:

• Web app — whether the Astro SSR front door answers
• Database — whether the SQLite + Drizzle layer responds to a health query
• Email (SMTP) — whether outbound transactional mail is flowing
• Last build — timestamp of the most recent deploy to production

What happens when something goes red

We run a lightweight monitor off the same endpoint. When any of the four signals flips to red for more than 60 seconds, every superadmin on the MSPercury operator team receives an incident email within five minutes. If you are a customer, you do not get individually paged — but the widget on this page flips immediately, so refreshing here is the fastest way to check.

For recurring or extended outages we post a short incident note at the bottom of this page once the dust settles. We do not keep a theatrical incident history: if the widget is green, the system is green.

Uptime target

MSPercury is a free, pay-what-you-want product. That means no SLA, no service credits, no contractual uptime guarantees.

What we do commit to is a target: 99.5% monthly uptime on the web app and database. Roughly a 3.6-hour budget per month for planned and unplanned downtime combined. We hit it or we improve the setup — that is the working relationship.

If your use case genuinely needs a signed uptime contract with financial remedies, we are not the right fit today. Email info@mspercury.com anyway — there may be a path, but it is not the default.

Where we live

Everything runs on a Hetzner Cloud VPS in Germany (Falkenstein region). nginx fronts the app, Let’s Encrypt handles TLS, and backups are written nightly to a separate Hetzner volume. No component of the hot path sits outside the EU.