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

> ## Agent Instructions
> These are the docs for Sevalla, a platform for deploying applications, databases, static sites, object storage and load balancers. The dashboard is at https://app.sevalla.com.
> Bold text in steps is an exact dashboard label.
> To act on a Sevalla account, prefer the Sevalla MCP server (https://mcp.sevalla.com/mcp, see https://docs.sevalla.com/ai-agents/overview.md), then the Sevalla CLI (https://docs.sevalla.com/developer-tools/cli.md), then the REST API (https://api-docs.sevalla.com, OpenAPI spec at https://api.sevalla.com/v3/openapi.json).
> Every page index is at https://docs.sevalla.com/llms.txt.

# System status

> Check whether Sevalla and the providers it depends on are working at status.sevalla.com, see past incidents, and subscribe by email, Slack, Microsoft Teams or feed.

The Sevalla status page at [status.sevalla.com](https://status.sevalla.com) shows whether Sevalla's services and the providers it depends on are working, with every open incident and scheduled maintenance.

## What the status page shows

| Group | Components |
| - | - |
| Sevalla | Dashboard, Applications, Databases, Static sites, Object storage, API |
| Google Cloud Platform | Google Kubernetes Engine, Google BigQuery, Google Cloud Networking, Google Cloud Pub/Sub, Google Cloud SQL |
| Cloudflare | CDN/Cache, API, Analytics, R2, Workers, Workers KV |
| GitHub | API Requests, Pull Requests, Webhooks |
| Atlassian Bitbucket | API, Webhooks, Authentication and user management |
| Claude | Claude API (api.anthropic.com) |

Each component shows its current state, and Sevalla's own components also show their uptime over the past 90 days. Past incidents are under [Incident history](https://status.sevalla.com/history), and the uptime record under [historical uptime](https://status.sevalla.com/uptime).

When the dashboard can't reach Sevalla, it shows `Sevalla can’t be reached.` with a **Status page** link, so you can tell an outage from a problem with your own connection.

If you have a problem the status page doesn't show, [contact support](/support/get-help).

## Subscribe to updates

<Steps>
  <Step title="Open the subscribe menu">
    On [status.sevalla.com](https://status.sevalla.com), click **Subscribe to Updates**.
  </Step>

  <Step title="Choose how to get updates">
    Pick a method from the table and complete its fields.
  </Step>
</Steps>

| Method | What you get | How to subscribe |
| - | - | - |
| Email | An email whenever an incident is created, updated or resolved | Enter your email address and click **Subscribe via Email**. If the page asks for a one-time code, enter the code from the email it sends you. |
| Slack | Incident updates and maintenance messages in a Slack channel | Click **Subscribe via Slack**, then choose the workspace and channel. |
| Microsoft Teams | Incident updates and maintenance messages in a Teams channel | Paste the channel's webhook URL in **Channel's Webhook URL** and click **Subscribe via Teams**. |
| Feed | Every incident in your feed reader | Add `https://status.sevalla.com/history.atom` (Atom) or `https://status.sevalla.com/history.rss` (RSS). |

## Unsubscribe

* **Email**: use the unsubscribe link at the bottom of any status email.
* **Slack or Microsoft Teams**: remove the Statuspage app or the incoming webhook from the channel.
* **Feed**: remove the feed from your reader.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.