No open incident
No incident is open.
Nothing has been declared. Incidents are written by hand; the figures below are measured by our own scheduled checks.
During an incident, the fastest path is email. A reply from a person beats a dot on a page.
Email info@pixelandprocess.deMeasured availability
Share of checks that got the expected response over the last 30 days. We check every 5 minutes.
Measured by Formspring’s own scheduled checks from our own infrastructure, not an independent monitor. A check proves a page or endpoint responded, not that every feature works. Declared incidents below are written by hand.
All components: 99.95% from 19,885 checks. Last checked Nov 17, 2026, 03:00 AM UTC.
| Component | Availability | Checks | Last checked |
|---|---|---|---|
| Marketing site Home page. | 99.92% | 3,977 | Nov 17, 2026, 03:00 AM UTC |
| Sign-in page Where customers reach the dashboard. | 99.97% | 3,977 | Nov 17, 2026, 03:00 AM UTC |
| Public docs Documentation index. | 99.92% | 3,977 | Nov 17, 2026, 03:00 AM UTC |
| Form handler Hosted submission endpoint, checked with a preflight request to an id that does not exist. A not-found answer shows the handler routed the request and looked it up. No submission is sent. | 99.97% | 3,977 | Nov 17, 2026, 03:00 AM UTC |
| API Unauthenticated request; a 401 means the API answered. | 100.00% | 3,977 | Nov 17, 2026, 03:00 AM UTC |
What this page is, and isn’t
Measured availability above comes from automated checks. The subsystems below are the parts of Formspring we open incidents against, and the incidents are written by the person handling them.
There are no health dots and no all-clear banner: an endpoint answering is not proof that every feature works.
| Subsystem | What it covers | Open incidents |
|---|---|---|
| Marketing site | Public site, docs, and pricing pages. | None declared |
| Dashboard | Authenticated app for forms, submissions, and team admin. | None declared |
| Form ingestion | Public submission endpoint and spam screening. | None declared |
| Webhook delivery | Signed outbound deliveries with retry and dead-letter handling. | None declared |
| Email notifications | Owner emails, autoresponders, and password resets. | None declared |
| File storage | Encrypted uploads in EU object storage with signed, expiring download links. | None declared |
| Billing | Subscriptions, invoices, and plan changes. | None declared |
| MCP server | Agent endpoint for reading and managing forms from connected AI tools. | None declared |
Declared incidents
Every incident posted here, newest first, with start time, affected parts and a running log.
Nothing has been declared here yet.
That’s the state of this log, not a report on the last 90 days. When an incident is opened it appears here and stays, resolved or not.
Getting told
There’s no incident mailing list yet. This page used to offer one, and nothing behind it sent mail, so the box is gone until that exists. Until then, write to us and a person answers.
Incident policy
Material incidents are posted with start time, affected systems and mitigation status, and get a postmortem within five business days. Team and Scale customers can request an incident-specific RCA in writing; the DPA and security overview set the contractual scope.
