LIVE STATUS · SELF-REPORTED · UNCACHED
System status
This page is generated by asking our production API how it feels, right now — the same live health checks our own monitoring uses. No third-party badge, no cache, no spin.
Last checked: 2026-07-12 02:12 UTC · API v1.0.0.0
All systems operational
Website
You're reading a page it just served — that's the check.
API & checkout
Health endpoint answered normally.
E-sign engine
First-party engine, served by the same API measured above.
Document sealing (KMS)
Sealing with Google Cloud KMS asymmetric keys.
Database
Live connectivity check passed.
Notary sessions
Our side of session coordination — partner network availability isn't probed here.
Shipping & tracking
Our side of label and tracking coordination — carrier networks aren't probed here.
Statuses are live checks run at request time and self-reported by the platform, not third-party monitoring. Incident history covers the last 90 days of service-affecting incidents from our automated ops monitor.
INCIDENT HISTORY
The last 90 days
Service-affecting incidents recorded by our automated ops monitor. Titles are generic by design — incident details can reference customer orders, so they stay internal.
detected 2026-07-11 21:30 UTC · resolved 2026-07-11 21:52 UTC
detected 2026-06-12 06:30 UTC · resolved 2026-07-11 21:22 UTC
detected 2026-06-12 01:05 UTC · resolved 2026-07-11 21:22 UTC
How to read this page
Every load of this page runs two live checks against production: the API health endpoint (which probes the database and reports which document sealer is active) and the public status feed (which carries incident history). We publish what those checks return, including when the answer is "degraded." For how the platform protects your documents, see Security & Trust. Seeing something this page doesn't? support@signsealship.com.