# Cluster outage — Vultr non-payment lockout (operator-attested)

**Date recorded:** 2026-11-16 (UTC)
**Evidence class:** `FOUNDER_ATTESTED_UNVERIFIED` (no Vultr invoice, suspension notice or payment receipt is in the repository)
**Recorded by:** the operator/founder, Vincent Noriega
**Affects:** the cluster outage and reboot window on 2026-11-16; the 48-hour soak that stopped during that window

## What the operator reports

The founder states that the Vultr account was locked because a payment was missed. The lockout removed access to the cluster hosts. The founder paid the outstanding balance and regained access. The cluster was restored afterwards.

This is recorded as the operator's account of the outage. It is not presented as a third-party finding, and no Vultr document has been attached.

## What this explains

- Why the cluster and its soak lost connectivity during the outage window.
- Why a host reboot/restore was needed.
- Why the 48-hour soak `soak-multiregion-48h-2026-11-16-mr03d` stopped at **1.636 h** rather than completing; the run is **STOPPED / NOT A PASSED SOAK**, not evidence of a 48-hour result.

## What this does NOT explain

- The **PBFT safety incident** on `cain-mr-02` (two conflicting 3-of-4 quorum certificates at sequence 1872339, view 3437) is a separate code-level safety finding. It was measured at checkpoint 0 before the outage window and is not caused by a missed payment.
- It does not make the old cluster a valid trust anchor. `cain-mr-02` remains quarantined.
- It does not convert the 48-hour run into a pass. The soak is still not established; 72 h and longer were not run.

## Corrective action

- Add automated Vultr billing alerts and auto-pay; the outage must not recur because of a missed invoice.
- Keep the cluster status page honest during an outage: "OPERATOR OUTAGE — ACCESS LOST" is a valid state; "4/4 HEALTHY" is not.
- Resume a fresh 48-hour soak from a clean checkpoint after the cluster is stable, and do not count the interrupted run.

## Limits

- Founder-attested only; independent verification would require the Vultr invoice/suspension record and a payment receipt.
- This note is an addendum to the signed 2026-11-15 incident bundle. It does not rewrite or invalidate the signed artifacts.
