Status
All SAIHM systems are monitored on a 15-minute cadence and their state is published, not asserted. The snapshot below is live-checked and auto-refreshes; on-chain claims are reproducible from mainnet data plus the published schema. Checked every 15 minutes; the timestamp of the last check appears here once the live feed loads. The machine-readable feed is /status-systems.json.
Critical systems
Operational status of the systems behind the SAIHM protocol and its distribution. Component-level snapshot; operator-level infrastructure metrics are not published.
| System | Status |
|---|---|
| Website & docs | Operational |
| Chat assistant | Operational |
MCP endpoint (/mcp) | Operational |
| Free-join & onboarding API | Operational |
| On-chain anchoring (COTI V2 mainnet) | Operational |
Audit channels
- On-chain anchors: COTI V2 mainnet via public block explorer.
- Machine-readable surface: /.well-known/saihm.json.
- Security disclosures: security.txt.
Common questions
- Where can I check whether SAIHM is up?
- On this page, and in machine-readable form at /status-systems.json, which is regenerated on a 15-minute cadence and carries the timestamp of its own last check. If that feed goes stale, the badges here report the status as unconfirmed rather than continuing to show the last known good value.
- What counts as a critical system?
- The website and docs, the chat assistant, the MCP endpoint at
/mcp, the free-join and onboarding API, and on-chain anchoring. Component-level status is published; operator-level infrastructure metrics are not. - How do I verify a SAIHM claim independently?
- Audit anchors are readable on the public block explorer, the machine-readable protocol surface is at /.well-known/saihm.json, and the source is Apache 2.0. Nothing on this page needs to be taken on trust.
- How do I report an outage or a security issue?
- Security disclosures go through security.txt. Anything else reaches the operations desk at ops@saihm.coti.global.