A Public Status Page for Piskes AI Studio

Starting today, Piskes AI Studio has a public status page at status.piskes.com, showing live operational status for all 17 apps along with the shared infrastructure underneath them — the AI Gateway, identity and sign-in, and the shared data layer every app relies on. Anyone can check it, no login required, and anyone can subscribe to updates by email or RSS for the specific components they care about.

How it works

The status page pulls from the same health checks and monitoring that our own team already watches internally, so what's shown reflects real system state rather than a manually updated page that lags behind reality. Components are broken out individually — an issue affecting Email doesn't show every other app as degraded if they're unaffected — and each incident gets its own timeline entry with updates posted as we investigate, identify, and resolve it, kept afterward as a historical record rather than deleted once resolved.

Where this is useful

This is aimed at exactly the moment status pages matter most: something seems wrong, and the fastest way to find out whether it's a known, being-worked-on issue or something specific to your workspace is checking a page that's independent of the tools that might themselves be affected. It also gives a historical uptime record per component, useful for any workspace that needs to report on the reliability of tools they depend on.

What's included

Live component status, incident history, and email and RSS subscriptions are live today. Per-workspace status notifications routed directly into Chat, so an incident affecting a component your workspace actually uses shows up where your team already is, are planned as a follow-up integration.

The status page is available now at status.piskes.com, independent of Piskes AI Studio sign-in, so it stays reachable even during an incident that affects authentication itself.