The status page, incidents and planned maintenance
Where to look when SignSpry seems slow or down: the public status page, what each state means, and what to do next.
The status page at signspry.com/status shows whether SignSpry is working right now, how it has done over the last 90 days, and any incident or planned maintenance. It is public, needs no sign-in, and has a Status link in the website footer.
What you see
The banner gives the overall state:
| Banner | Meaning |
|---|---|
| All systems operational | Everything is fine |
| Some systems are degraded | A check is failing or an incident is open |
| Some systems are down | A major incident is open |
| Planned maintenance in progress | Work announced in advance is under way |
Five components, each with its own state (Operational, Degraded, Outage, Maintenance, or No data yet) and a 90-day bar chart:
- Website and app
- Signing and sealing
- Email delivery
- API and webhooks
- Reminders and scheduled sends
Each bar is one day. Green is 99.5% or better, amber 95% or better, red below that, and an empty bar means no data that day.
Incidents and maintenance
When something goes wrong, SignSpry posts an incident with a title, the components affected and timestamped updates that move through Investigating, Identified, Monitoring and Resolved. Resolved incidents stay under Past incidents for 90 days. Planned work appears under Planned maintenance before it starts.
How it is measured
- Every 10 minutes SignSpry runs the same health checks that keep the service running (database, disk, email delivery, the signing fonts, and that the scheduler itself ran) and records the result for each component.
- A 10-minute check that never happened, because the server or its timer was down, counts against that day.
- The "Reminders and scheduled sends" component turns degraded if the scheduler has not run for about half an hour.
For developers
/status.json returns the same data for machines: the overall status, each component with its 90-day uptime, and incidents with their updates. It is cached for about a minute and can be read from other sites.
When something seems wrong
- Open the status page. An open incident usually explains it.
- If nothing is posted, try again in a few minutes and check your own network.
- If it persists, open a ticket or write to support@signspry.com with what you were doing and the time (see Getting help).
- If a signer says an email never arrived, read The signer says no email arrived. Most of those are address problems rather than outages.