Firma electrónica, notarización y entrega de documentos en línea

SignSealShip

Live status · self-reported · uncached

Production health without the marketing filter.

This page asks the production API and its dependencies for their current state on every request. It reports unknowns and degraded checks as plainly as operational ones.
  • Last checked 2026-08-04 01:53 UTC
  • API v1.0.0.0
  • No page cache

All systems operational

Website

You're reading a page it just served — that's the check.

OPERATIONAL

API & checkout

Health endpoint answered normally.

OPERATIONAL

E-sign engine

First-party engine, served by the same API measured above.

OPERATIONAL

Document sealing (KMS)

Sealing with Google Cloud KMS asymmetric keys.

OPERATIONAL

Database

Live connectivity check passed.

OPERATIONAL

Notary sessions

Our side of session coordination — partner network availability isn't probed here.

OPERATIONAL

Shipping & tracking

Our side of label and tracking coordination — carrier networks aren't probed here.

OPERATIONAL

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.

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-08-01 23:09 UTC · resolved 2026-08-01 23:13 UTC

Service availability incidentCRITICALRESOLVED

detected 2026-08-01 18:20 UTC · resolved 2026-08-01 18:35 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-29 19:19 UTC · resolved 2026-07-29 19:26 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-29 18:41 UTC · resolved 2026-07-29 18:50 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-29 17:34 UTC · resolved 2026-07-29 17:42 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 21:24 UTC · resolved 2026-07-28 21:29 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 21:17 UTC · resolved 2026-07-28 21:23 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 21:09 UTC · resolved 2026-07-28 21:14 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 21:01 UTC · resolved 2026-07-28 21:06 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 20:53 UTC · resolved 2026-07-28 20:59 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 20:47 UTC · resolved 2026-07-28 20:52 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 20:41 UTC · resolved 2026-07-28 20:46 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 20:33 UTC · resolved 2026-07-28 20:38 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 20:25 UTC · resolved 2026-07-28 20:31 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 20:18 UTC · resolved 2026-07-28 20:22 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 20:10 UTC · resolved 2026-07-28 20:16 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 20:02 UTC · resolved 2026-07-28 20:07 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 19:54 UTC · resolved 2026-07-28 19:59 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 19:48 UTC · resolved 2026-07-28 19:52 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 19:39 UTC · resolved 2026-07-28 19:43 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 19:28 UTC · resolved 2026-07-28 19:34 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 19:21 UTC · resolved 2026-07-28 19:26 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 19:13 UTC · resolved 2026-07-28 19:19 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 19:07 UTC · resolved 2026-07-28 19:13 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 18:58 UTC · resolved 2026-07-28 19:03 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 18:49 UTC · resolved 2026-07-28 18:54 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 18:40 UTC · resolved 2026-07-28 18:46 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 18:30 UTC · resolved 2026-07-28 18:35 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 18:24 UTC · resolved 2026-07-28 18:30 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 18:17 UTC · resolved 2026-07-28 18:22 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 18:11 UTC · resolved 2026-07-28 18:16 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 17:55 UTC · resolved 2026-07-28 18:06 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 17:46 UTC · resolved 2026-07-28 17:52 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 17:37 UTC · resolved 2026-07-28 17:43 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 17:27 UTC · resolved 2026-07-28 17:33 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 17:20 UTC · resolved 2026-07-28 17:26 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 17:13 UTC · resolved 2026-07-28 17:19 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 17:05 UTC · resolved 2026-07-28 17:11 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 17:00 UTC · resolved 2026-07-28 17:04 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 16:51 UTC · resolved 2026-07-28 16:57 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 16:43 UTC · resolved 2026-07-28 16:49 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 16:36 UTC · resolved 2026-07-28 16:42 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 16:29 UTC · resolved 2026-07-28 16:35 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 16:23 UTC · resolved 2026-07-28 16:29 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 16:16 UTC · resolved 2026-07-28 16:22 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 16:10 UTC · resolved 2026-07-28 16:15 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 16:00 UTC · resolved 2026-07-28 16:05 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 15:50 UTC · resolved 2026-07-28 15:55 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 15:41 UTC · resolved 2026-07-28 15:48 UTC

Infrastructure monitoring alertCRITICALRESOLVED

detected 2026-07-28 15:33 UTC · resolved 2026-07-28 15:38 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.