All systems operational.
Live health of the splitforms form submission API, email delivery, dashboard, magic-link auth, webhooks, file storage, and the public marketing site. Last checked May 9, 2026 · checked hourly.
No incidents reported in the last 90 days. Uptime measured against a one-minute health probe on each component.
System components · 8
Past incidents · last 90 days
When something does break, you'll see the post-mortem here with the cause, duration, and what we changed to keep it from happening again.
splitforms runs on:
- Vercel — Compute, edge runtime, and CDN for the Next.js app.
- Supabase — Postgres, magic-link Auth, and Storage for file uploads.
- AWS SES — Outbound email — submission notifications and auto-responders.
- Cloudflare — DNS, edge caching for static assets, DDoS shield.
Why we publish status.
A form backend lives in the critical path of a customer's contact, signup, and lead pipeline — when it's down, their site silently loses leads. The honest response is to publish what we know: what's up, what's impaired, and what we're doing about it. This page is updated by an automated probe and edited by humans during incidents. If the page itself is unreachable, assume splitforms is having a bad day and email hello@splitforms.com.
Status FAQ.
How uptime is measured, what each status label means, and what to do when something goes wrong.
What does "operational" mean on this page?
A component shows "Operational" when its primary endpoint is responding within expected latency and error budget. "Degraded" means partial impairment — e.g. elevated latency or partial regional failure. "Outage" means the component is fully unavailable to most users. Today every splitforms component is Operational.
How is uptime measured?
We treat any 5xx response on the canonical health path of a component as downtime, sampled at one-minute intervals. The 90-day, 30-day, and 7-day numbers above are rolling windows over those samples. Marketing pages and the API reference are measured against successful HTML responses from the Vercel edge.
Where can I report an issue?
Email hello@splitforms.com with as much detail as you can — request ID, timestamp, your form's access key (not your account password), and what you saw vs. what you expected. We reply to every email and post-mortem any incident affecting the form submission API on this page.
Is there an SLA?
We aim for 99.9% uptime on a best-effort basis across all plans. There is no formal SLA on the free tier. Pro and 4-year customers get priority incident response, but no contractual uptime guarantee in v0 — we don't want to promise something we can't credibly enforce as a small team.
Can I get downtime alerts?
Email hello@splitforms.com with the subject "Status updates" and we'll add you to a low-volume incident notification list. A self-serve subscribe button (RSS, Atom, and email) is on the roadmap at /roadmap.
How long is submission data retained?
Submissions are retained for 30 days on the Free tier, 12 months on Pro, and 12 months on the 4-year plan. After that they're deleted from primary storage. Webhook delivery logs follow the same retention as their parent submissions.
What happens if splitforms is offline during a submission?
If the splitforms API returns a 5xx during submission, the browser receives the error and your form's existing client-side error path runs — most templates we ship surface an inline retry message. We do not silently drop submissions. When the incident resolves, no manual replay is needed because the request never persisted on our side; the user retries and the second attempt lands normally.
A form backend you can actually rely on.
1,000 free submissions per month, no credit card. Pro is $5/mo for 5,000 submissions, and the $59 4-year plan covers 48 months of access at 15,000 submissions per month.