Jepsen started as a series of blog posts and conference talks before becoming a consultancy in 2016. Jepsen has analyzed dozens of databases, coordination services, and queues—revealing replica divergence, data loss, stale reads, read skew, lock conflicts, and much more. Below are the analyses published on jepsen.io.
| System | Date | Version |
|---|---|---|
| ParticleDB | 2026-10-31 | 1.1.4 |
| Orkes Conductor | 2026-10-20 | 5.3.2 |
| MariaDB Galera Cluster | 2026-03-16 | 12.1.2 |
| NATS | 2025-12-08 | 2.12.1 |
| Capela | 2025-08-07 | dda5892 |
| TigerBeetle | 2025-06-06 | 0.16.11 |
| Amazon RDS for PostgreSQL | 2025-04-29 | 17.4 |
| Bufstream | 2024-11-12 | 0.1.0 |
| jetcd | 2024-08-08 | 0.8.2 |
| Datomic | 2024-05-15 | 1.0.7075 |
| RavenDB | 2024-01-31 | 6.0.2 |
| MySQL | 2023-12-19 | 8.0.34 |
| Redpanda | 2022-04-29 | 21.10.1 |
| Radix DLT | 2022-02-05 | 1.0-beta.35.1 |
| Scylla | 2020-12-23 | 4.2-rc3 |
| Redis-Raft | 2020-06-23 | 1b3fbf6 |
| PostgreSQL | 2020-06-12 | 12.3 |
| MongoDB | 2020-05-15 | 4.2.6 |
| Dgraph | 2020-04-30 | 1.1.1 |
| etcd | 2020-01-30 | 3.4.3 |
| YugaByte DB | 2019-09-05 | 1.3.1 |
| TiDB | 2019-06-12 | 2.1.7 |
| YugaByte DB | 2019-03-26 | 1.1.9 |
| FaunaDB | 2019-03-05 | 2.5.4 |
| MongoDB | 2018-10-23 | 3.6.4 |
| Dgraph | 2018-08-23 | 1.0.2 |
| Aerospike | 2018-03-07 | 3.99.0.3 |
| Hazelcast | 2017-10-06 | 3.8.3 |
| Tendermint | 2017-09-05 | 0.10.2 |
| CockroachDB | 2017-02-16 | beta-20160829 |
| MongoDB | 2017-02-07 | 3.4.0‑rc3 |
| VoltDB | 2016-07-12 | 6.3 |
| RethinkDB | 2016-01-22 | 2.2.3 |
| RethinkDB | 2016-01-04 | 2.1.5 |
Get Tested
You can hire Jepsen to analyze a database, queue, or other kind of system. Jepsen also offers training and consulting to help you build and extend your own tests.
Ethics
All public Jepsen analyses are performed in accordance with our ethics policy.
Techniques
Jepsen occupies a particular niche of the correctness testing landscape. We emphasize:
-
Opaque-box systems testing: we evaluate real binaries running on real clusters. This allows us to test systems without access to their source, and without requiring deep packet inspection, formal annotations, etc. Bugs reproduced in Jepsen are observable in production, not theoretical. However, we sacrifice some of the strengths of formal methods: tests are nondeterministic, and we cannot prove correctness, only find errors.
-
Testing under distributed systems failure modes: faulty networks, unsynchronized clocks, and partial failure. Many test suites only evaluate the behavior of healthy clusters, but production systems experience pathological failure modes. Jepsen shows behavior under strain.
-
Generative testing: we construct random operations, apply them to the system, and construct a concurrent history of their results. That history is checked against a model to establish its correctness. Generative (or property-based) tests often reveal edge cases with subtle combinations of inputs.