Scenario
Checkpoint propagation and regional arrival lag.
The probe(s) subscribe with Sui SubscribeCheckpoints over gRPC and capture each checkpoint arrival. Datasets from all regions are merged by checkpoint + digest to detect the leader and followers for each checkpoint.
Of the possible 31 regions, 31 were selected for data collection: Oregon, N. California, Mexico, Columbus, OH, N. Virginia, Montreal, São Paulo, Ireland, Zaragoza, London, Paris, Frankfurt, Zurich, Milan, Stockholm, Cape Town, Tel Aviv, Dubai, Mumbai, Hyderabad, Bangkok, Kuala Lumpur, Singapore, Jakarta, Hong Kong, Taipei, Seoul, Osaka, Tokyo, Melbourne, and Sydney.
Each location probe breaks its processing loop if / when the endpoint response is too-many-requests, a.k.a. HTTP code 429 etc. Also, codes 401 and 403.
At the time of the report generation: 30 of 31 datasets were available from 31 selected regions x 1 endpoint.
One dataset was not available at the time of the report generation: aws-me-central-1.
Additional info about RPC Inspector Pro technology is in the FAQ and documentation
Findings
Summary by Dataset
Summary by Checkpoint
Includes only "complete" checkpoints (checkpoints seen by every probe). The p95 of the values in the column "p95" is: 268 ms.
Details
Per checkpoint, leading endpoint-region vs. every other arrival for the same checkpoint, incl. checkpoints not seen by every probe. Regional "wall clocks" are treated as globally synchronized.