Service levels
Service levels
Availability targets, backups and support for your configuration.
Availability
This page is a summary. The Terms of Service govern.
| Configuration | Topology | Monthly uptime | Remedy |
|---|---|---|---|
| Single-zone | One dedicated instance in one zone | best-effort | — |
| HA | Two zones · writer + cross-zone standby · automatic failover | 99.9% | pro-rata service credit against the next invoice |
| HA+ | Multi-zone · writer + two standbys · higher-capacity configuration | 99.95% | pro-rata service credit against the next invoice |
| Enterprise | As HA+, under an annual agreement with negotiated quotas | 99.99% | pro-rata service credit against the next invoice |
Uptime is measured per instance per calendar month. Scheduled maintenance, force-majeure events and outages caused by your own configuration are excluded from the calculation, as defined in the Terms. Credits are the sole remedy for availability shortfalls.
Backups and recovery
- Backups
- Encrypted nightly snapshots are included, integrity-checked daily and kept in the instance’s region.
- Point-in-time recovery
- Opt-in. Restore lands on a 5 s roll-up boundary; 500 ms with the Intra-Segment PITR add-on.
- Retention window
- 7 or 30 days self-serve, up to 35 days. Longer windows are agreed per deployment on Enterprise.
- Restore path
- From the console or the HTTP API.
Support
Email support@originchaindb.com for support. Enterprise agreements include a named support engineer. Response-time commitments are written into the agreement.
Custom service terms
Custom availability, retention and support terms are agreed on Enterprise contracts.
Build with OriginChainDB