Status and incidents
Availability is promised in the Service level agreement. This page says how Merki reports it.
Quick path
- Check
https://status.merki.devfor live endpoint health. - Subscribe to incident updates there.
- SLA remedies are claimed, not automatic. See below.
Details
| Topic | Decision |
|---|---|
| Status page | https://status.merki.dev: per-endpoint availability, scheduled maintenance, active incidents. |
| Incident comms | Updates at detection, mitigation, and resolution. Postmortems for SLA-breaching incidents within 5 business days. |
| Maintenance | Announced at least 72 hours ahead; excluded from SLA measurement. |
| Remedies | Where the 99.9% target is missed, customers may claim service credits per the SLA schedule (10% below 99.9%, 25% below 99.5%, 50% below 99.0% of monthly spend on the affected endpoint). File within 30 days via billing@merki.dev. |
| Models without uptime | Most catalog rows show n/a for uptime — no SLA target is offered for those models yet. Only models with a measured uptime value are covered. |
Checklist
- [ ] Status page is bookmarked before you need it.
- [ ] Incident contact for your team is set.
- [ ] Credit claims reference the affected endpoint and month.
Next step
Read the enforceable terms: Service level agreement.