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. Pre-launch surfaces are listed so you can see the rollout map at a glance.
| Service | URL | Status | Notes |
|---|---|---|---|
| Marketing site | chainmore.io | Operational | Static HTML, hosted on Netlify, security headers enforced. |
| Merchant dashboard | app.chainmore.io | Pre-launch | Production deploy not yet scheduled. Local development runs from the ChainMore app stack. |
| Gateway API | api.chainmore.io | Pre-launch | Payment-orchestration HTTP API. Goes live with the first paying merchant. |
| Identity provider | auth.chainmore.io | Pre-launch | OIDC issuer (Keycloak). Goes live with the dashboards. |
Active incidents
Scheduled maintenance
Last 90 days
The Processor maintains a rolling 90-day history of resolved incidents. Tracking starts on the day the first paying merchant is onboarded; the gateway and dashboards are not yet in scope, so this section will populate from go-live.
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". Active merchants are subscribed automatically as part of onboarding.
- 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-04-30, 19:50 UTC. Independent of primary stack: hosted on Netlify (marketing infrastructure), not on the production hosting target for the dashboards or gateway.