splitforms status.

Yes. An automated check probes every component listed above about every 5 minutes and records the result. This page and the JSON at /api/status are rebuilt from those records roughly once a minute, so what you see is at most a few minutes old.

Each day's bar is computed only from the checks recorded that day: an operational check counts as 1, a degraded check as 0.5, a down check as 0. Days with no recorded checks are shown in grey and are excluded from the percentage — we never fill in uptime we did not measure.

Operational: the last check succeeded within the normal response time. Degraded: the check succeeded but was slow, or (for webhooks) more than half of the last hour's deliveries failed. Down: the check failed, timed out, or almost every recent webhook delivery failed. No data: the component could not be observed on that run.

Email [email protected] with the request ID, timestamp, form access key, HTTP status, and the result you expected. Never send your account password.

No. The uptime shown here is measured, not contractual. No contractual uptime SLA is currently published. Contact splitforms before relying on the service for a workflow that requires contractual availability guarantees.

Keep the HTTP status and response body, check this page and Recent Activity in the dashboard, and retry once the reported error is resolved. Use the API reference to interpret documented response codes.