> For the complete documentation index, see [llms.txt](https://docs.taloflow.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taloflow.ai/security/security-operations/availability-and-continuity.md).

# Availability & Continuity

Monitoring, redundancy, and continuity approach for the Taloflow platform.

### Scope

This page covers how we monitor availability and how we maintain service continuity.

For detailed recovery objectives and failover options, see [Disaster Recovery](/security/security-operations/disaster-recovery.md).

For backup schedules and log retention, see [Logs, Audit Logs, and Backups](/security/platform-controls/logs-audit-logs-and-backups.md).

### Uptime and SLA

Taloflow provides commercially reasonable efforts to maintain platform availability.

We do not offer a specific uptime SLA in the standard agreement.

For contractual terms, see the [Master Services Agreement](broken://spaces/-MQkUmzRViVxDERN9vKk/pages/5LECXwqL6dNCfhbUrGJG).

### Monitoring and incident communication

Live uptime and incident updates are published on the [Status](broken://spaces/-MQkUmzRViVxDERN9vKk/pages/-MbItRgwaHx3aHJU8JPQ) page.

If you’re seeing an outage or degradation, contact us via the [Support Hub](broken://spaces/-MQkUmzRViVxDERN9vKk/pages/7w2btLpaU63hhnW4Dd7q).

### Redundancy

Taloflow uses service clustering and network redundancies to reduce single points of failure.

Redundancy and continuity controls are complemented by backups and restore procedures.

### Continuity and recovery

Taloflow manages infrastructure, backups, and disaster recovery procedures.

Customers do not need to configure or maintain separate disaster recovery systems for Taloflow.

For RTO / data loss guidance and emergency options, see [Disaster Recovery](/security/security-operations/disaster-recovery.md).

### Related pages

* [Incident Response](/security/security-operations/incident-response.md)
* [Security Overview](/security/security-overview.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.taloflow.ai/security/security-operations/availability-and-continuity.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.