What the status page measures
The status page lists these areas, each with a probe of its own. Here is what the probe checks and what it does not; measuring rules as of 1 October 2026.
Whether every customer system responds, along the same path as your browser.
Whether an individual screen calculates correctly is not tested by the probe.
Whether sign-in responds and rejects a wrong sign-in.
Whether a platform error occurs when posting an invoice, generating its PDF or sending invoices and reminders.
Whether all customer systems run the same version.
During a rollout a maintenance entry appears here.
Whether the REST interface of every customer system responds and configured event notifications are delivered.
Whether our outgoing mail server accepts our credentials.
Whether a message reaches its recipient is not shown by the probe.
Whether finAPI is reachable and accepts our access.
Whether fetching from an individual bank works is not shown by the probe.
The central service through which ZeptronIT submits your filings on your behalf.
Maintenance and communication
Updates arrive continuously. If a change needs a brief interruption, we announce it as maintenance on the status page and by email, with the time frame and the affected areas.
- A change needs a brief interruption
- Notice on the status page and by emailwith the time frame and the affected areas
- Maintenance within the announced window
The bank connection and ELSTER transmission have their own areas on the status page. If something is wrong there, you see it instead of having to ask us.
Availability, without sugarcoating.
The measured figures are on our status page, per component and with the history of the past days. Where we do not measure yet, it says so there. A number that only stands there because nobody looked is not something you will find with us.
Incidents appear at status.zepdesk.de with their time and impact.
Maintenance is also announced by email.