Status

Katsura Labs status

Operational

All systems operational.

Last updated: loading...

Status updates

Subscribe for operational notices or report concerns with reproducible details.

Subscribe by email Report a problem

Public reports intentionally omit internal routes, hostnames, and implementation details.

API platform

Operational

Authentication, event intake, and report generation availability.

Public service area

Event ingestion

Operational

Webhook capture and persistence health for scan workflows.

Public service area

Recovery Autopilot dashboard

Operational

Scan execution experience and report access for customers.

Public service area

HookTrace console

Operational

Webhook operations, retries, and replay workflows.

Public service area

Authentication

Operational

Sign-in reliability, session validity, and access controls.

Public service area

Notifications & billing integrations

Operational

Email delivery, billing events, and third-party integration status.

External dependency area

Recent notices

Incident history

Latest resolved incidents with customer-safe impact and resolution context.

Delayed event processing

Resolved

A subset of incoming events processed with elevated latency. Dashboard updates appeared later than expected.

Severity: MediumStarted: February 1, 2026 — 5:02 UTCResolved: February 1, 2026 — 5:48 UTC

Customer action: no action required. Backfill and processing resumed automatically.

Email delivery retries

Resolved

Some status-alert emails were delayed while the provider retried accepted messages.

Severity: LowStarted: January 28, 2026 — 8:41 UTCResolved: January 28, 2026 — 9:10 UTC

Customer action: no action required.

Maintenance

Scheduled maintenance

No scheduled maintenance

Clear

If a window is scheduled, we publish start time, duration, and user-facing impact.

Communication standard

How incidents are communicated

InvestigatingIdentifiedMonitoringResolved

Every incident update includes customer impact, mitigation progress, public-system areas affected, and timeline checkpoints. Internal topology, hostnames, credentials, and infrastructure vendor specifics are never published on this public status page.