Skip to main content
LifeWyn
Algunos sistemas están degradados

Estado del servicio y compromisos

Los componentes que hacen funcionar LifeWyn y los estándares de fiabilidad que nos exigimos. Esta página muestra una comprobación de estado general en vivo; todavía no publicamos un historial de incidencias por componente ni métricas de latencia.

Última comprobación: 06:06 PM

Esto es un resumen general del estado de la plataforma. Los usuarios que hayan iniciado sesión pueden ver el detalle por componente en el Centro de Ayuda de la aplicación.

Components

What we monitor

Each component shows its own result when the health check returns one. Where it does not, the row reads Live status unavailable — meaning we did not get an answer, not that the service is down. We would rather show nothing than show a guess.

OperationalDegradedOutageLive status unavailable
Autenticación y gateway de API
Inicio de sesión, MFA y enrutamiento de solicitudes
Servicios de bóveda y documentos
Almacenamiento cifrado y subida/descarga con URL prefirmadas
Gestión de claves y herencia
Fragmentos de clave, Comprobaciones de Protección y flujo de liberación
Bases de datos y almacenamiento
Postgres y almacenamiento de objetos
Notificaciones
Entrega push, por correo y dentro de la app

Fiabilidad

Dónde estamos

Written plainly, so nobody discovers it during an incident.

  • Every service exposes a health check. This page reads them live rather than showing a status somebody updates by hand.
  • Nightly database backups, encrypted before they leave the server, with a written restore procedure we rehearse. Kept in the same region on a rolling 30-day retention.
  • Security incidents affecting your data will be disclosed to you directly and posted here. Under India's DPDP Act we also notify the Data Protection Board, and affected users within 72 hours.
  • No uptime SLA yet. LifeWyn runs in a single region with no automatic failover, and there is no point-in-time recovery — a restore returns the platform to the last nightly backup.
  • The alerting pipeline is configured but has no on-call receiver wired to it yet. Alerts fire, but nobody is paged automatically outside working hours. This is our highest operational priority.
  • Per-component metrics and an incident history are not published yet. When we publish them, older entries will stay up rather than being quietly removed.

What this means for you

If something here is red

Your vault is not at risk

An outage affects reachability, not integrity. Your records stay encrypted and intact, and nothing is released or lost because a service is slow or briefly unavailable.

Your own export, taken any time on any plan, opens with your passphrase without our servers at all.

Check-ins and releases are not time-critical

The sequence runs over days and weeks, not seconds. A missed check-in during an outage is not treated as silence, and reminders resume when service does.

If you are worried about a release in progress, write to support@lifewyn.com and we will confirm where it stands.

More on reliability, backups and our security posture in the Trust Center.