A calm, monitored service.

How the Service is monitored, and how an incident is communicated. Ethere does not publish a fixed uptime figure it has not measured over a full period.

What is monitored

The public endpoints, the database, the widget path, and the backup archive. Automated alerts watch for anomalies, including a stalled transaction-log archive or a stale backup.

How incidents are communicated

When an incident affects the Service, Ethere posts a notice in the dashboard and emails the owner of each affected organization. A post-incident note states what happened and what changed.

Recovery objectives

A full encrypted backup each week, incremental encrypted backups on the other days, and continuous transaction-log shipping, with an encrypted copy held on separate infrastructure. The recovery point objective is minutes, not hours, and recovery is drilled against the off-site copy.

Planned maintenance

Where maintenance may interrupt the Service, Ethere gives advance notice and schedules it for the quietest window available.