Status

System status and operational updates.

Live health, availability posture, and incident communication for cyang.io services. This page favors clear public signals without turning every read into expensive dependency fan-out.

Snapshot type
Cached public health summary
Use case
Operational visibility and customer confidence
Current service posture

Public status snapshot is temporarily unavailable.

This page is withholding system-level health claims until a fresh public readiness snapshot is available.

Live mode with snapshot-backed public statusPer-service cards and history stay unpublished until they have explicit backing data.
Snapshot unavailable
Last updated Unavailable (Unavailable)
Auto-refresh retries while the public snapshot is unavailable
Overall platform status

Live public snapshot summary

Public traffic reads a cached readiness snapshot. Deeper dependency diagnostics stay on operator-only surfaces until they can be published with explicit backing data.

30-day uptime
Snapshot unavailable
This public page is waiting for a fresh cached readiness snapshot before publishing service-wide health claims.
Incident publication
Manual
Historical incident entries are published intentionally rather than inferred from one health check.
Service detail

Why live mode stays conservative

The public status page avoids fabricating service-by-service health cards from a single cached readiness result.

Live snapshot mode

Live public status is currently backed by the cached readiness snapshot above. Per-service latency, uptime, and trend cards only appear in preview mode, where they are explicitly presented as modeled scenarios rather than published live facts.

Incident history

Recent events

Live snapshot mode

This public page shows the current cached service snapshot. Historical incident publishing stays manual so we do not fabricate timelines from a single health check.

Snapshot model

How this status page stays cheap and accurate

Current source
Cached public health snapshot
Anonymous traffic reads a lightweight summary instead of live dependency fan-out.
Refresh policy
Manual plus slow auto-refresh
Live mode only polls while visible, backs off when healthy, and resumes immediately only once the cached snapshot is stale.
Historical reporting
Published intentionally
We do not synthesize incident timelines or uptime history from a single transient health check.
Technical diagnostics (advanced)

This section is intended for engineering review and integration troubleshooting.

The cached public readiness snapshot is unavailable or stale, so this block only shows the current public fallback state.
{
  "service": "cyang.io",
  "ok": null,
  "timestamp": null,
  "environment": "production",
  "build": "current",
  "status": "snapshot_unavailable",
  "error": "PUBLIC_SNAPSHOT_UNAVAILABLE"
}

Need help or updates?

Contact support for account-specific questions, or subscribe for daily platform updates delivered at 6:00 AM UTC.