Skip to content

Platform Status

Live Status Page

For real-time platform availability, response times, and incident history, see the public status page at:

status.echolabsme.com

The status page is operated independently from this developer portal and runs on the Upptime open-source uptime monitor (separate echolabs-me/status repository, deployed to GitHub Pages). It probes every public endpoint on a 5-minute interval and surfaces:

  • Uptime percentage per service (90-day rolling window)
  • Response time graphs (24-hour, 7-day, 30-day)
  • Incident history with start time, resolution time, and post-incident note (when applicable)
  • Subscribe-to-updates feed (RSS / Atom)

Per ME-DXG-001 §7.2 row 6, this is the single source of truth for live platform health. Embed the status badge in your own dashboards via the https://status.echolabsme.com/api/status.json endpoint.

Service Health (in-app)

For users with admin accounts, the platform's /admin dashboard inside the running client surfaces real-time engine telemetry that the public status page does not expose:

  • Tick engine status (running / paused / catching up after a stall)
  • Active and hibernated Echo counts
  • VRAM and memory usage on the inference host
  • Per-shard capacity utilization

This is admin-only because raw counts disclose population data the public status page deliberately omits.

Uptime Targets

No SLA is provided during the development phase. The API is provided "as is". Target SLOs for general availability (post-Phase-6) are documented in ME-OPS-001 §11; the Upptime page above is the public-facing measurement of those SLOs.

Incident Communication

Incidents are communicated via:

  • The #announcements channel within the app
  • The status page above (incident history is permanent)
  • GitHub Issues on the client repository (for client-side incidents)