BleedWatch
00 // STATUS

BleedWatch system status.

Live operational status for the public site, dashboard, API, scanner workers, AgentGuard, SaintScan, KMS proxy, and database layer.

Last fetched 2026-05-07 09:12 UTC.

All systems operational

0 incidents in the last 30 days.

Status data below is a rebuild fixture shaped after the canonical status-board integration.

01 // COMPONENTS

Component checks.

Each card mirrors the shape expected from the live status endpoint: component state, rolling uptime, recent heartbeat, and seven-day health.

Updated every 30 seconds in production

Web

bleedwatch.com

OK

Marketing site, trust center, pricing, docs entry, and public intel routes.

UPTIME

99.99%

Last checked 2026-05-07 09:12 UTC

Dashboard

app.bleedwatch.com

OK

Authenticated tenant dashboard, scan review, remediation routing, and evidence views.

UPTIME

99.95%

Last checked 2026-05-07 09:12 UTC

API

api.bleedwatch.com

OK

Public status endpoint, app APIs, scan orchestration, and integration callbacks.

UPTIME

99.97%

Last checked 2026-05-07 09:11 UTC

Scanner fleet

EASM artifact and dependency surface

OK

EASM artifact scanning, registry refresh, DNS normalization, and evidence extraction.

UPTIME

99.91%

Last checked 2026-05-07 09:09 UTC

AgentGuard

AI agent + MCP posture

OK

AI agent posture checks, MCP inventory, permission graph review, and prompt-injection routing.

UPTIME

99.96%

Last checked 2026-05-07 09:08 UTC

SaintScan

Active validation gateway

OK

Sandboxed active validation, MCP gateway policy, circuit breakers, and audit finalization.

UPTIME

99.90%

Last checked 2026-05-07 09:07 UTC

KMS

Encryption key management

OK

Envelope encryption path, per-tenant DEK mediation, and sensitive preview handling.

UPTIME

99.99%

Last checked 2026-05-07 09:06 UTC

Database

Primary tenant data store

OK

Primary data store, tenant isolation policies, audit tables, and scan metadata.

UPTIME

99.98%

Last checked 2026-05-07 09:06 UTC

02 // INCIDENT HISTORY

Resolved incidents.

Closed incidents include date, duration, root cause, and the concrete remediation note. Customer-impacting events also trigger email and in-app notification.

Resolved2026-04-2931 minutes

Delayed package registry refresh

ROOT CAUSE

Upstream NPM metadata throttling caused queue backoff during a scheduled registry sync.

RESOLUTION

Worker concurrency was reduced, stale cursors were replayed, and registry backoff thresholds were tuned.

Resolved2026-04-1218 minutes

Slack notification retries elevated

ROOT CAUSE

Webhook retry policy used an overly aggressive backoff after transient Slack 5xx responses.

RESOLUTION

Retry windows were widened and duplicate notification suppression was added to the integration queue.

Resolved2026-03-2744 minutes

SaintScan validation queue paused

ROOT CAUSE

Circuit-breaker calibration paused one active-validation queue while the digest cache was refreshed.

RESOLUTION

Digest cache warmup moved ahead of validation admission, and the affected queue was replayed.

SUBSCRIBE

Get status updates by email or Slack.

Production wiring should attach this form to the canonical status endpoint and incident notifier. The rebuild keeps the public subscription surface ready.

Email updates

Component alerts, incident updates, maintenance windows, and resolution summaries.