Status
System status
Public uptime history starts when third-party monitoring is connected. Until then this page publishes no uptime percentages and no incident log, because we would rather show nothing than numbers nobody measured. If something looks broken, tell us and we'll confirm whether it's on our side.
How incidents are reported
- Every incident that affects customers is posted on the live status page with the date, the affected component, how long it lasted and what we changed afterwards.
- Our servers are checked from outside every ten minutes by a scheduled job that runs on GitHub, not on our infrastructure, so an outage is recorded even when everything of ours is down. Its run history is the record we will publish once it is long enough to mean something.
- Your data stays exportable during an incident. Export reads the same records the app does, so if you can sign in, you can take your data with you (exit process).
Availability targets
These are targets, not yet a service-level agreement. The service runs on a single server (security page), and an SLA with credits is only worth the measurement behind it. When the outside check has 90 days of history, the targets below become an SLA with credits and this page says so, with the date.
| Plan | Monthly uptime target | Support response |
|---|---|---|
| Starter | 99.9% | 2 business days |
| Professional | 99.9% | 1 business day |
| Enterprise | 99.95% | 4 business hours |