diff --git a/docs/CaseStudies.md b/docs/CaseStudies.md
index dbdc815846..7000234ac8 100644
--- a/docs/CaseStudies.md
+++ b/docs/CaseStudies.md
@@ -74,12 +74,12 @@ See [Monitoring K8S with VictoriaMetrics](https://docs.google.com/presentation/d
 Numbers:
 
 * The number of active time series per VictoriaMetrics instance is 40M.
-* The total number of time series per VictoriaMetrics instance is 400M+.
+* The total number of time series per VictoriaMetrics instance is 5000M+.
 * Ingestion rate per VictoriaMetrics instance is 1M data points per second.
-* The total number of datapoints per VictoriaMetrics instance is 8 trillions.
-* The average time series churn rate is ~3M per day.
+* The total number of datapoints per VictoriaMetrics instance is 8.5 trillions.
+* The average time series churn rate is ~80M per day.
 * The average query rate is ~100 per second (mostly alert queries).
-* Query duration: median is ~70ms, 99th percentile is ~1.5sec.
+* Query duration: median is ~20ms, 99th percentile is ~1.5sec.
 * Retention: 3 months.
 
 > Alternatives that we’ve played with before choosing VictoriaMetrics are: federated Prometheus, Cortex, IronDB and Thanos.