System status

Core

  • Console
  • Approvals
  • Agents
  • Routines & background work
  • Connected tools
  • Billing

Developers

  • Zuger API
  • Zuger MCP
  • Webhooks

Channels

  • Email delivery
  • Chats
  • Moléson website widget
  • Kesch calls

Platform

  • Zuger Store
  • File uploads & storage
  • Sign-in & passkeys
  • Website

Zuger KYA

  • VerifierComing soon
  • Transparency logComing soon
  • DirectoryComing soon

Built, and not launched. Each part is left out of the summary at the top, and this page will report it like every other part once it is live.

The last ninety days

A reading every five minutes, kept for ninety days. Uptime counts only the time a part was fully operational; a day with no readings says so rather than passing for a good one.

  • Operational
  • Degraded
  • Outage
  • No data

Each bar is one day, in UTC.

Past incidents

Incident reports

Posted by a person at Zuger while it happened: what was affected, every update, and how it ended.

Measured

Every stretch in the last ninety days when anything was degraded or down: when it started, when it ended, and which parts it touched.

What the states mean

  • Operational

    Working as it should. Runs start, approvals resolve, the API answers.

  • Degraded

    Working, slower or with a feature out. An outage delays work; it never loses it — a run interrupted resumes or reports, and never half-commits.

  • Outage

    Not available. Approvals stay operational in every degraded state of the platform — the one thing a founder must be able to do mid-incident is decide.

  • Coming online

    Built, and not live yet. It is left out of the summary at the top until it goes live.

Get incident updates by email

We email you when Zuger posts an incident on this page, an update or its end. You confirm by the link we send, and one click stops them.

Free plan · No card

Something looks wrong?

Write to us and a person answers. If an incident affects customers we publish a timeline.