> ## Documentation Index
> Fetch the complete documentation index at: https://developers.essal.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# System Status

> Monitor Essal platform uptime, incidents, and scheduled maintenance.

The Essal status page provides real-time visibility into platform health across all six apps and supporting infrastructure.

## Status Page

Visit [status.essal.cloud](https://status.essal.cloud) to view:

* Current operational status for each app and API endpoint
* Active and historical incidents with timeline updates
* Scheduled maintenance windows
* 90-day uptime statistics per component

## Components Monitored

| Component            | Description                           |
| -------------------- | ------------------------------------- |
| **API Gateway**      | Core API routing and authentication   |
| **Essal Office**     | Document, sheet, and file operations  |
| **Essal Access**     | Identity, SSO, and session management |
| **Essal Sales**      | CRM contacts, deals, and pipelines    |
| **Essal Careers**    | Job postings and application tracking |
| **Essal Project**    | Tasks, sprints, and time tracking     |
| **Essal Guard**      | Policies, audit logs, and alerts      |
| **Webhook Delivery** | Event fan-out and delivery            |
| **Sandbox**          | Sandbox environment availability      |

## Subscribing to Incidents

Subscribe to status updates via email, Slack, or RSS:

1. Visit [status.essal.cloud](https://status.essal.cloud)
2. Click **Subscribe to Updates**
3. Choose your notification channel

## SLA Commitments

| Plan       | API Uptime SLA |
| ---------- | -------------- |
| Standard   | 99.5% monthly  |
| Business   | 99.9% monthly  |
| Enterprise | 99.95% monthly |

SLA credits are issued automatically for qualifying downtime. Review the full SLA at [legal.essal.cloud/sla](https://legal.essal.cloud/sla).

## Incident Communication

When a platform incident occurs:

1. A status incident is created within **5 minutes** of detection
2. Updates are posted every **30 minutes** until resolution
3. A post-incident report is published within **48 hours** of resolution