Skip to main content
These are the numbers in the latency table on the Limits page. You can measure every latency row yourself with one script that uses the public API, the archil CLI, and fio. Run it in the same cloud region as the disk, since a cross-region round trip is larger than most of these figures. It needs curl, jq, fio, journalctl, the archil CLI, and an API key in ARCHIL_API_KEY. Set API to your region’s control plane endpoint and REGION to match, then run it as root with sudo -E bash latency.sh. It takes about two minutes, creates disks named latency-test-*, and deletes them when it finishes.
latency.sh
Our run, from a c7gn.2xlarge in AWS us-east-1 on October 27, 2026:
  • Create and delete leave out the TLS handshake, about 10 ms on a new connection.
  • mount ms, wall includes starting the CLI. The client log line doesn’t.
  • Checkpoint and branch are CLI wall times, so they include starting the CLI, and branch also opens a new TLS connection.
  • The read test mounts with --read-ahead 0. With the default, random reads also pull in neighboring blocks, so about a third of them hit the client cache.