From 213b9fab4b90ee194f52a44de785c50654981371 Mon Sep 17 00:00:00 2001
From: Florent Tapponnier <160007691+Flotapponnier@users.noreply.github.com>
Date: Mon, 3 Aug 2026 19:09:26 +0200
Subject: [PATCH] fix: update report date to Aug 3 2026 + data snapshot period

---
 src/content/reports/rpc/2026-08-state-of-public-rpc.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/content/reports/rpc/2026-08-state-of-public-rpc.mdx b/src/content/reports/rpc/2026-08-state-of-public-rpc.mdx
index 342aca0b..d64ccc15 100644
--- a/src/content/reports/rpc/2026-08-state-of-public-rpc.mdx
+++ b/src/content/reports/rpc/2026-08-state-of-public-rpc.mdx
@@ -2,7 +2,7 @@
 title: "Best Free Public RPC 2026: Speed, Reliability, and What to Use"
 category: "rpc"
 slug: "2026-08-state-of-public-rpc"
-publishedAt: "2026-08-01"
+publishedAt: "2026-08-03"
 period: "August 2026"
 summary: "Free public RPCs are faster than ever, and less reliable than most builders assume. This report benchmarks the leading providers by what actually matters: correctness first, latency second."
 heroFinding: "The fastest free RPC in this cohort fails one call in five. The most reliable didn't fail a single probe in the measurement window."
@@ -115,7 +115,7 @@ Latency leadership at the top is typically stable — the same provider that win
 
 ## Provider Wins Across 19 Chains
 
-19 chains, 3 probe regions — 57 regional contests. A "win" is the lowest p50 among providers returning a classified `ok` response in that region for that chain. Data snapshot: July 28, 2026 — live current rankings on the [RPC hub](/rpc).
+19 chains, 3 probe regions — 57 regional contests. A "win" is the lowest p50 among providers returning a classified `ok` response in that region for that chain. Data snapshot: August 2026 — live current rankings on the [RPC hub](/rpc).
 
 **Win count summary**