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

# Status Monitoring

> How Antei monitors service uptime, integration health, and internal systems for real-time availability and performance.

<Icon icon="signal" size={26} color="#4B5563" />

# Status Monitoring

Antei maintains real-time observability across its infrastructure, integrations, and processing pipelines to ensure high availability and early anomaly detection.

***

## Platform Monitoring

| Layer                     | Tooling                           | Frequency               |
| :------------------------ | :-------------------------------- | :---------------------- |
| **Application APIs**      | Xano health monitors              | Every 60 seconds        |
| **Cloudflare Workers**    | Native logging + synthetic checks | On trigger / 1 min      |
| **PostgreSQL (GCP)**      | GCP Cloud Monitoring              | Every 30 seconds        |
| **File Storage (R2)**     | Cloudflare Insights               | On access               |
| **Render & Railway Apps** | Built-in health checks            | On deploy + every 5 min |

***

## Integration Monitoring

Each connected integration (e.g., Stripe, Xero, Gmail) is tracked for authentication validity, sync errors, and data freshness.

* **Token health & expiry tracking**
* **Sync frequency adherence alerts**
* **Webhook delivery status & retries**

> 🔄 You can view per-integration sync health in your Antei dashboard under **Org Settings → Integrations**.

***

## Data Pipeline Monitoring

* **Ingestion failures** are logged in real-time and retried using exponential backoff logic
* **Validation outcomes** (processed, unprocessed, errored) are logged and can be filtered per entity
* **Reconciliation jobs** are tracked by status and trigger notifications on failure

***

## User-Facing Status

A public status page is under development. Until then:

* All service-related issues are communicated via in-app banners or email alerts
* SLA-impacting events are documented in [Audit Logs](/trust-center/Security/audit-logs)

***

## Alerts & Escalation

Critical alerts trigger incident workflows based on:

* Downtime > 1 minute for critical APIs
* Error rates > 2% over 5 minutes
* Sync failures for core integrations

Our team is notified via internal alerting channels (e.g., email, Slack, PagerDuty).

***

## Next Steps

* [→ Architecture Overview](/trust-center/Infrastructure%20&%20Availability/architecture-overview)
* [→ Disaster Recovery](/trust-center/Infrastructure%20&%20Availability/disaster-recovery)
* [→ SLA Commitments](/trust-center/Infrastructure%20&%20Availability/sla)