System status

Is ForkMesh working?

Live status for the website, API, database, git hosting network, and realtime sync — each with a 30-day history sampled once a minute. Uptime is computed only from samples that were actually recorded; minutes where the sampler itself didn't run are red monitoring failures. Missing, stale, empty, and rate-limited monitoring use distinct red shades so they cannot be confused with an observed service outage. Click a system to see exactly what its check tests. We are still tuning monitoring and optimizing traffic usage for bots. On an upgraded instance, the API and scheduled checks fail closed rather than report operational while a historical Worker-held wallet key still requires the documented offline export, zero-balance reconciliation, and scrub.

Checking status…

Systems

Each system shows its last 60 one-minute checks, then its last 24 hourly checks and 30-day history. Hover a square for its status and reason; click a system's name to see exactly what its health check tests.

Hover a square for details.

Loading…
Operational Degraded Down Missing sample Stale monitoring No monitoring data Rate limited Later today (not elapsed)