SLA & Status
Service Level Agreement
| Metric | Target |
|---|---|
| Availability | 99.99% (≤ 4.3 min downtime / month) |
| p50 latency | < 80ms |
| p95 latency | < 150ms |
| p99 latency | < 200ms |
Latency is measured end-to-end from request received to response sent, excluding network transit time.
Status Page
Real-time service status, incident reports, and scheduled maintenance windows are published at:
You can subscribe to notifications via:
- Email — per-incident and maintenance alerts
- Webhook — programmatic status updates for your monitoring stack
Health Endpoint
GET https://api.recivr.com/healthNo authentication required. Returns 200 with:
json
{
"status": "ok",
"service": "rts"
}Recommended polling interval: 30 seconds. Use this for connectivity checks and load balancer health probes.
Response Headers
Every response includes tracing headers:
| Header | Description |
|---|---|
X-Recivr-Latency | Total processing time |
X-Recivr-Env | Environment (production) |
Incident Communication
During incidents:
- Status page is updated within 5 minutes of detection
- Root cause analysis is published within 48 hours of resolution
- Affected clients are notified via email
Versioning Policy
| Change type | Action | Notice |
|---|---|---|
| New optional field added | No version bump | Changelog updated |
| New enum value added | No version bump | Changelog updated |
| Field renamed or removed | New version (/v2/) | 6 months deprecation notice |
| Response shape change | New version (/v2/) | 6 months deprecation notice |
Support
| Channel | Details |
|---|---|
| Technical Support | support@recivr.com |
| Status Page | status.recivr.com |
| Documentation | docs.recivr.com |
| Dashboard | dashboard.recivr.com |