Operational state, in plain sight.
Current service status, active incidents, and 90-day history. Hosted on infrastructure independent of the primary production stack so an outage of the stack does not take this page down with it.
Services
The public ChainMore surfaces and their current state. Merchants get access after a review; until then the dashboard, API and checkout are in early access.
| Service | URL | Status | Notes |
|---|---|---|---|
| Marketing site | chainmore.io | Operational | Static HTML, hosted on Netlify, security headers enforced. |
| Merchant dashboard | app.chainmore.io | Early access | For merchants with access. New merchants request access at app.chainmore.io/get-started. |
| Gateway API | api.chainmore.io | Early access | HTTP API for merchants with an API key. |
| Hosted checkout | checkout.chainmore.io | Early access | Payment page for the merchant's customers. |
| Sign-in | auth.chainmore.io | Running | Sign-in for the merchant dashboard. |
Active incidents
Scheduled maintenance
Last 90 days
Resolved incidents of the last 90 days are listed here.
Severity reference
For incidents that do occur, ChainMore uses the severity classification documented in the incident-response runbook:
- SEV-1 (critical), customer-impacting, full-service outage or data integrity at risk. Acknowledgement within the response time stated in the SLA, customer-facing status banner up within 30 minutes of classification, post-incident blameless postmortem within 5 business days.
- SEV-2 (high), customer-impacting, degraded service or partial outage. Customer-facing status update within 1 hour of classification.
- SEV-3 (medium), internal or low-impact. Update on the next business-hour cycle.
- SEV-4 (informational), internal-only, no customer impact. Logged for the postmortem record, no public banner.
Get notified
Two paths, depending on what you want:
- Per-incident email, send a request to support@chainmore.io with subject "Status updates subscription".
- RSS / Atom feed, planned. Will publish at
/status.atomwhen the first incident lands. Until then there is nothing to subscribe to.
Why this page is intentionally simple
No JavaScript, no external dependencies, no auto-polling. The status page is the document of last resort during an outage; the more moving parts it carries, the more likely it is to fail in the exact moment it matters. Updates are pushed by Operations as part of incident response (see /security for the responsible-disclosure path and the incident-response runbook the ops team works from).
Last updated: 2026-10-07. Independent of primary stack: hosted on Netlify (marketing infrastructure), not on the production hosting target for the dashboards or gateway.