Scenario
Round-trip latencies for chained requests getSlot and getBlock(slot) with start-to-start throttling of (at least) 1100 ms for every request.
Also, slot number consistency with block availability and block age. The block propagation comparison is conservative and latency-agnostic.
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: 60 of 62 datasets were available from 31 selected regions x 2 endpoints.
2 datasets were not available at the time of the report generation: A.aws-me-central-1, B.aws-me-central-1.
Additional info about RPC Inspector Pro technology is in the FAQ and documentation
Findings
| Endpoint | Lagging | Unique | Lowest | Arrival Tms | Arrival Region | Highest | Arrival Tms | Arrival Region |
|---|---|---|---|---|---|---|---|---|
| A. public.rpc.Solanavibestation.com | 3,115 | 67 | 419,109,685 | 1,778,530,536,381 | N. Virginia / AWS | 419,109,777 | 1,778,530,573,300 | Jakarta / AWS |
| B. solana-rpc.Publicnode.com | 0 | 23 | 419,109,716 | 1,778,530,536,375 | Frankfurt / AWS | 419,109,788 | 1,778,530,565,022 | Milan / AWS |
We detected 3115 responses whose sendTms, arrivalTms and number were such that we can state the endpoint was lagging in the respective region.
E.g. on arrivalTms=1,778,530,537,654 in Bangkok / AWS, we received number 419,109,716 from B. solana-rpc.Publicnode.com. Afterwards, on sendTms=1,778,530,548,033 we dispatched a request to A. public.rpc.Solanavibestation.com, which returned lower number 419,109,710 at arrivalTms=1,778,530,548,569. Therefore, A. public.rpc.Solanavibestation.com was lagging because it was returning lower number 419,109,710 well after B. solana-rpc.Publicnode.com advanced to 419,109,716.
Summary
Global and continental aggregations by endpoint and method(s) depend on completeness of data in the details.
Details
Latencies exclude one warmup request per endpoint in each region. Additional columns are visible when you scroll to the right. 1 dataset (endpoint-region) is not in the details because its probe received rate limits or other failures during connection setup and warmup.
Errors
Info about errors incl. 429. Up to 4 retained error responses per endpoint, per region. Scenario-derived availability notes may also appear.