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

# Service status

> Real-time SafarAPI availability and incident history

<Note>
  A public real-time status page (`status.safarapi.com`) is being provisioned.
  Until it is live, the availability commitments and incident communication on
  this page apply, and approved partners are notified directly per the SLA.
</Note>

## Components monitored

| Component         | Endpoint                                 | SLA target     |
| ----------------- | ---------------------------------------- | -------------- |
| Core API          | `api.safarapi.com/api/partner/v1/*`      | 99.5 % monthly |
| Authentication    | `api.safarapi.com/api/partner/v1/auth/*` | 99.5 % monthly |
| Console           | `console.safarapi.com`                   | 99.0 % monthly |
| Documentation     | `developers.safarapi.com`                | best-effort    |
| Webhooks delivery | (queue depth)                            | \< 5 min p95   |

## Incident notifications

<Note>
  Self-service subscription will be available when `status.safarapi.com` is
  provisioned (component-level email, SMS, or webhook — webhook recommended for
  your bank's alerting stack: PagerDuty, Opsgenie, Slack). Until then, approved
  partners receive incident notifications **directly** per the SLA, on the
  components their integration depends on.
</Note>

## Incident communication

For incidents impacting active partners:

* **First update** within 15 minutes of detection (acknowledged + impact assessment).
* **Resolution update** at most every 30 minutes for active incidents.
* **Postmortem** within 5 business days for any incident classified Major or Critical.

For security‑specific incidents (data breach, suspected compromise), the 72‑hour GDPR / Loi 09‑08 notification policy applies in addition to status‑page updates.

## SLA credits

If monthly uptime falls below 99.5 %, SafarAPI credits **5 %** of your monthly invoice for **every 0.1 %** below target. Credits are applied automatically on the following month's settlement — no claim required.

Example: 98.8 % uptime in May = (99.5 − 98.8) / 0.1 × 5 % = **35 % credit** of May invoice on June settlement.

## How we measure

Uptime is measured by **external probes** (UptimeRobot + Pingdom redundancy) hitting `GET https://api.safarapi.com/api/partner/v1/health` from at least 3 geographically distinct points, every minute. A check is "down" only if **2 of 3 probes** fail in the same 60-second window. This eliminates single-probe false positives.

Latency p95 is sampled server-side from the audit log (`partner_api_audit_log.latency_ms`), aggregated per 5-minute window, computed from the 95th percentile of all customer-facing requests (excluding `/health` and admin endpoints).