From 60f5404d7bb36eecdccadd88d34517502a1dfd30 Mon Sep 17 00:00:00 2001
From: Florent Tapponnier <160007691+Flotapponnier@users.noreply.github.com>
Date: Sun, 26 Jul 2026 05:51:48 +0200
Subject: [PATCH] docs(ccip): link OpenChainBench live latency measurement on
 execution-latency page

---
 src/content/ccip/ccip-execution-latency.mdx | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/src/content/ccip/ccip-execution-latency.mdx b/src/content/ccip/ccip-execution-latency.mdx
index dafd437d1f7..9177c1f6303 100644
--- a/src/content/ccip/ccip-execution-latency.mdx
+++ b/src/content/ccip/ccip-execution-latency.mdx
@@ -169,6 +169,10 @@ This section provides an overview of the finality methods CCIP uses to determine
 | Zircuit           | Finality tag                              | 21 minutes                  |
 | ZKsync            | [Block depth](#block-depth) (1200 blocks) | 20 minutes                  |
 
+## Observed end-to-end latency
+
+The finality times listed above are the source-chain component of CCIP's total execution time. For a live measurement of the full pipeline (source transaction to destination `Execute` including DON commit, RMN verification, and executor delivery), see the [OpenChainBench Chainlink CCIP latency benchmark](https://openchainbench.com/benchmarks/chainlink-ccip-latency). The benchmark polls the public [CCIP Tools API](https://docs.chain.link/ccip/tools/api) every 60 seconds, computes per-source-chain p50/p90/p99 over a 24-hour window from `receiptTimestamp - sendTimestamp` on `status: SUCCESS` messages, and exposes both the raw distribution and the source code of the observer.
+
 This page provides details on the expected latency for a cross-chain transaction using CCIP, covering the different stages of transaction processing and the factors that influence overall execution times.
 
 For a comprehensive understanding of CCIP's architecture and how messages flow through the system, refer to the [CCIP detailed architecture](/ccip/concepts/architecture/overview) documentation.