Live measurement is paused.

Incident history.

Dated incident summaries state affected customer behavior, known impact, remediation status and remaining limitations. Historical incidents do not by themselves establish current exploitability.

• Historical usage-settlement incident

  On 17 September 2026, monitoring found that metered session usage had not reduced prepaid credit, leaving usage above credited balances. A production correction settled outstanding usage once, recorded the funds restriction, and returned the monitor to clear; the incident was marked resolved that day. No affected session was running, so parking a running session at exhaustion was not demonstrated. A later amendment corrected an overstated monitoring count. Account identities, balances and operational recovery instructions are omitted; the customer-impacting billing failure and test limitation remain visible.

  17 September 2026 · Historical record; any production observation is limited to the dated test described below.

  record ↗ · 3ddfb9e8316d

• Historical credit-authorization incident

  The incident record describes a defect, present from 31 August 2026 and found on 16 September, that allowed a signed-in customer to alter its own credit balance. The 17 September record reports passing laboratory checks for a correction that restricts credit changes while preserving legitimate purchases and ledger reads. It explicitly leaves production deployment verification and ledger review as follow-up work in this version. The record does not establish whether customers misused the defect. Production follow-up belongs to separate later evidence; this historical disclosure is not proof of current exploitability.

  31 August 2026 · Historical record; any production observation is limited to the dated test described below.

  record ↗ · 5afd378db114

• Resolved historical status-display incident

  On 15 September 2026, KeepState identified a website error that displayed fresh service-health information as paused. The affected site release had gone live on 14 September. The incident record reports that the service itself was operational; the fault was in how the website interpreted freshness. It records a display correction, regression checks and monitoring changes shipped with the incident release. This account distinguishes a misleading status display from a service outage. It is historical incident evidence, not a live availability measurement.

  15 September 2026 · Historical evidence; the scope and environment are described in the recorded result.

  record ↗ · f5b4f3651e83