# Status

> What we can say about operations today: there is no independent status service yet and no availability figures, and this page does not show outages.

> **Status on 8 November 2026:** Registration is currently closed. The Free plan runs as a test phase with the existing accounts. We maintain this page by hand; it does not show outages.

## In short

- There is no independent status service yet. The [Roadmap](https://privymail.eu/en/roadmap.md) lists it as "not yet set up".
- This page belongs to the website and sits on the same server. If the server goes down, this page is unreachable too. It is therefore not an outage indicator.
- We publish no availability figures, no response times and no outage history. We do not quote a number without evidence.
- For the test phase we promise no availability (section 3.2 of the [Terms of use](https://privymail.eu/en/terms-free.md)).

## Status on 8 November 2026

The details are statements by the operator, not measurements. They follow the [Roadmap](https://privymail.eu/en/roadmap.md).

| Area | Status |
|---|---|
| [This website](https://privymail.eu/en/transparency.md) | is served as long as you read this page; there is no published measurement of its reachability |
| [Registration of new accounts](https://privymail.eu/en/pricing.md) | currently closed; we name no date for opening |
| [Existing accounts](https://privymail.eu/en/roadmap.md): sign-in, webmail, IMAP and SMTP | in operation during the test phase, with no promise of availability |
| [Mail to and from other providers](https://privymail.eu/en/roadmap.md) | not yet enabled |
| [Independent status service](https://privymail.eu/en/roadmap.md) | not set up |

## What we publish today

Little is published, and none of it says anything about availability.

- **The signed manifest.** Every morning around 5 am (Europe/Berlin) the server creates a new, signed snapshot: time of capture, release, versions of the operating system and tools, TLS issuer. It shows what is installed, not whether the website was reachable yesterday. Downloads and signature verification are under [Transparency](https://privymail.eu/en/transparency.md), and the post [This website can be verified](https://privymail.eu/en/blog/verifiable-website.md) explains how it comes about.
- **Checks before every publication.** The server checks the website's source every two minutes. Each change is built as a new release, checked and only then switched over in a single step. If a step fails, the previous state stays online. The footer of every page names the commit of the running state.
- **The mail status in the manifest.** It reads `internal_beta` and means: test phase of the Free plan. That is a self-attested statement, not a measurement of live operation.

## What does not exist

- No published availability in percent and no response times.
- No continuous measurement from outside our own server that we publish.
- No figures on mail delivery. Mail to other providers is not enabled, and between privymail.eu accounts we publish no measurements.
- No list of past outages and no statement of how long an outage lasted.

## If something does not work

Write to us through the [Contact](https://privymail.eu/en/contact.md) page and give the address, the time and the error message. Never send a password or an app password. We promise no response time. What happens during restarts and maintenance is described under [Maintenance](https://privymail.eu/en/maintenance.md).

## How we maintain this page

The page does not update itself. We change it by hand when a status changes and then set the date at the top anew. An independent status service is planned on the [Roadmap](https://privymail.eu/en/roadmap.md), with no date.

---

- privymail.eu: patchletter UG (haftungsbeschränkt) · Germany
- Commit: `71cd013265df`
- This page as HTML: https://privymail.eu/en/status/
- Deutsche Fassung: https://privymail.eu/status.md