> For the complete documentation index, see [llms.txt](https://docs.kaio.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kaio.xyz/product-operations/availability-management.md).
# Availability
## Overview
The KAIO infrastructure runs on Amazon Web Services (AWS) and MongoDB components. Both offer Service Level Agreements (SLAs) in order to guarantee the availability of their services. Availability refers to how consistently a system is operational and accessible. It determines the system's reliability, aiming to minimize downtime.
### Service Uptime
| EKS | EC2 | Amplify | S3 | Cognito | SES | Lambda | MongoDB |
|---|
| 99.95% | 99.5% | 99.95% | 99.9% | 99.9% | 99.9% | 99.95% | 99.95% |
## **Amazon Web Services**
AWS operates data centers in multiple geographic regions. Each region contains one or more Availability Zones (AZs), which are physically separate data centers within a region. These are designed to provide high availability and fault tolerance. Services hosted on AWS can be distributed across multiple AZs for redundancy and resilience. Currently KAIO uses a single AZ for services running on AWS, with the option of using multiple ones in the future for improved availability.
### **EKS**
KAIO uses an [Amazon EKS](https://aws.amazon.com/eks/) Kubernetes service to manage most of its infrastructure in the AWS cloud, running on EC2 instances. This includes the blockchain network infrastructure itself, the API backend system, and a subgraph ([The Graph](https://thegraph.com/)) keeping track of the KAIO smart contracts.
**Service Commitment**: AWS will use commercially reasonable efforts to make the Kubernetes endpoint for an Amazon EKS Cluster available with a Monthly Uptime Percentage of at least 99.95% during any monthly billing cycle.
**Availability Definition**: Availability for EKS is defined as the success of at least one connection request in a 5-minute interval.
### **EC2**
KAIO uses [Amazon EC2](https://aws.amazon.com/ec2/) instances to run most of its infrastructure. These in turn are managed and controlled by EKS, as described previously.
**Service Commitment**: For each individual Amazon EC2 instance, AWS will use commercially reasonable efforts to make the Single EC2 Instance available with an Instance-Level Uptime Percentage of at least 99.5%, in each case during any monthly billing cycle. If in the future KAIO has more than one instance hosted on different Availability Zones in the same region, AWS will use commercially reasonable efforts to make Amazon EC2 available for each AWS region with a Monthly Uptime Percentage of at least 99.99%.
**Availability Definition**: Availability for EC2 is defined as follows:
* For the Instance-Level SLA, availability is defined as the time the single EC2 Instance has external connectivity.
* For the Region-Level SLA, availability is defined as the time at least one of the running instances deployed in two or more Availability Zones concurrently, has external connectivity.
### **Amplify**
KAIO uses [AWS Amplify](https://aws.amazon.com/amplify/) to host its frontend website.
**Service Commitment**: AWS will use commercially reasonable efforts to make Amplify Console available with a Monthly Uptime Percentage for each AWS region, during any monthly billing cycle, of at least 99.95%.
**Availability Definition**: Availability for Amplify is defined as the success rate of requests in a 5-minute interval.
### **S3**
KAIO uses an [Amazon S3](https://aws.amazon.com/s3/) bucket to host media, such as legal documents, images, and others.
**Service Commitment**: AWS will use commercially reasonable efforts to make the Amazon S3 Services each available with a Monthly Uptime Percentage of at least 99.9%, in each case during any monthly billing cycle.
**Availability Definition**: Availability for S3 is defined as the success rate of requests in a 5-minute interval.
### Cognito
KAIO uses [Amazon Cognito](https://aws.amazon.com/cognito/) for customer identity and access management.
**Service Commitment**: AWS will use commercially reasonable efforts to make Cognito available with a Monthly Uptime Percentage for each AWS region of at least 99.9%, during any monthly billing cycle.
**Availability Definition**: Availability for Cognito is defined as the success rate of requests in a 5-minute interval.
### SES
KAIO uses [Amazon SES](https://aws.amazon.com/ses/) for sending out email notifications.
**Service Commitment**: AWS will use commercially reasonable efforts to make the Included Services each available with a Monthly Uptime Percentage for each AWS region, during any monthly billing cycle, of at least 99.9%.
**Availability Definition**: Availability for SES is defined as the success rate of requests in a 5-minute interval.
### Lambda
KAIO uses [AWS Lambda](https://aws.amazon.com/lambda/) for automating user tasks.
**Service Commitment**: AWS will use commercially reasonable efforts to make Lambda available with a Monthly Uptime Percentage for each AWS region, during any monthly billing cycle, of at least 99.95%.
**Availability Definition**: Availability for Lambda is defined as the success rate of requests in a 5-minute interval.
## MongoDB
MongoDB operates data centers in multiple geographic regions. Each region contains one or more Availability Zones, designed to provide high availability and fault tolerance. KAIO uses MongoDB Atlas, which has a three-node minimum replica set distributed across AZs in the same region. There is also the option to improve reliability further in the future by using multiple regions.
### Atlas
KAIO uses a [MongoDB Atlas](https://www.mongodb.com/atlas/database) database to store user data.
**Service Commitment**: MongoDB will use commercially reasonable efforts to maximize the availability of MongoDB Atlas, and provide a Monthly Uptime Percentage of at least 99.95%. This applies only to MongoDB Atlas deployments at level M10 or above that have been up for a minimum of 24 hours.
**Availability Definition**: Availability for Atlas is defined as the success of at least one connection request in a 1-minute interval.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.kaio.xyz/product-operations/availability-management.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.