Status
YOLO platform status
Live health of the services behind YOLO, checked by our own API edge over the same connections it serves you with — plus a public record of past incidents. No number here is hand-entered.
All platform components are responding normally.
Components
| Component | State | Latency | Detail | Checked |
|---|---|---|---|---|
| API edge | Operational | 0 ms | responding | 06:55:53 |
| Accounts & profiles | Operational | 6 ms | responding | 06:55:53 |
| Broker execution (demo/paper) | Operational | 0 ms | responding | 06:55:53 |
| Signals & notifications | Operational | 0 ms | responding | 06:55:53 |
| Options strategy engine | Operational | 0 ms | reachable | 06:55:53 |
Incident history
Honest post-incident records, newest first. Entries are added and updated in our version-controlled codebase, so this history cannot be quietly rewritten.
Trading-history database lost after a server failure — fully recovered
A server failure wiped the database that had recently become the sole store for signal, trade and subscription history, so expert and follower records were temporarily missing. No broker orders were affected, and YOLO never holds client funds. We restored the records in full from a retained internal copy and verified the counts matched. We also added automatic nightly backups of that database so a single server failure can no longer cause data loss.
Follower signal feeds appeared empty after a database migration
A bug in the final step of a planned database migration meant follower signal feeds displayed no signals, even though the underlying records were safe. Open positions and broker execution were unaffected. We fixed the migration step, backfilled every affected feed, and verified feeds were fully restored. We now confirm migrated data is present and non-empty before completing any migration of this kind.