System Status

Real-time status for BumpHQ services

Components

Dashboard & API Operational

Disboard Automated Bumping Operational

Portal Server Management Operational

Ghost Ping Scheduler Operational

Authentication & Billing Operational

90-day uptime

Dashboard & API

—

Incident history

Elevated Disboard bump error rate — Camoufox subprocess crashes Resolved

A subset of automated Disboard bump attempts were failing due to SIGBUS crashes in the Camoufox browser subprocess (the component that handles Cloudflare clearance). Affected bumps were retried automatically and recovered within 10 seconds in most cases. Customer-facing impact was minimized by retry middleware introduced in Stage 0.3.

2026-05-05 · Update

A subprocess isolation fix was deployed (posix_spawn refactor). Crash rate dropped from ~380/day to ~190/day (~50% reduction). A second-stage posix_spawn fix is scheduled for Stage 2.1 and is expected to eliminate the remaining crashes.

2026-05-05 · Resolved

Crash rate stabilized at baseline (~190/day). Customer-visible errors are masked by retry middleware. Monitoring continues. Incident closed.

Opened: 2026-05-05 · Resolved: 2026-05-05 · Duration: ~2 hours customer impact

Database WAL pinning — intermittent API slowness Resolved

The internal SQLite WAL (write-ahead log) grew to 32GB due to a long-held database reader connection, causing write latency spikes. Dashboard API responses became intermittently slow (>2s on some endpoints). The Overwatch service was restarted to drain the pinned connection.

2026-05-04 · Resolved

Root cause fixed: database connections are now wrapped with autocommit mode and writer isolation. An automated WAL health probe now runs every 5 minutes and alerts before the condition recurs. No further incidents expected.

Opened: 2026-05-04 · Resolved: 2026-05-04 · Duration: ~4 hours elevated latency

Subscribe to incident notifications: status@bumphq.co