From 3e29a41b97f76a9d4a895c7a5b128d25b64d15c3 Mon Sep 17 00:00:00 2001 From: Ben Echols Date: Wed, 28 Jan 2026 23:13:39 -0800 Subject: [PATCH] Update Temporal Cloud latency stats with January 2026 data - Add January 2026 latency measurements (p50, p90, p99) - Reorganize section with "Historical latency data" heading - Keep March 2024 data for comparison Co-Authored-By: Claude Opus 4.5 --- .../temporal-cloud/service-availability.mdx | 20 ++++++++++++++----- 1 file changed, 15 insertions(+), 5 deletions(-) diff --git a/docs/evaluate/temporal-cloud/service-availability.mdx b/docs/evaluate/temporal-cloud/service-availability.mdx index 4a854829d0..8ccdcf1e7e 100644 --- a/docs/evaluate/temporal-cloud/service-availability.mdx +++ b/docs/evaluate/temporal-cloud/service-availability.mdx @@ -40,7 +40,21 @@ Please contact your AE or Support to enable this feature. Temporal Cloud has a p99 latency SLO of 200ms per region. -In March 2024, latency over a week-long period for starting and signaling Workflow Executions was as follows: +The same SLO for normal Worker requests (commands and polling) apply to Nexus in both the caller and handler Namespaces. + +### Historical latency data + +Latency over a week-long period for starting and signaling Workflow Executions was as follows: + +#### January 2026 + +| Operation | p50 | p90 | p99 | +| :--------------------------------- | :----: | :--: | ---: | +| `StartWorkflowExecution` | 14ms | 21ms | 69ms | +| `SignalWorkflowExecution` | 11ms | 19ms | 46ms | +| `SignalWithStartWorkflowExecution` | 19ms | 37ms | 95ms | + +#### March 2024 | Operation | p90 | p99 | | :--------------------------------- | :--: | ---: | @@ -48,9 +62,5 @@ In March 2024, latency over a week-long period for starting and signaling Workfl | `SignalWorkflowExecution` | 14ms | 40ms | | `SignalWithStartWorkflowExecution` | 24ms | 61ms | -As Temporal continues working on improving latencies, these numbers will progressively decrease. - -The same SLO for normal Worker requests (commands and polling) apply to Nexus in both the caller and handler Namespaces. - Latency observed from the Temporal Client is influenced by other system components like the Codec Server, egress proxy, and the network itself. Also, concurrent operations on the same Workflow Execution may result in higher latency.