Spire Systems

Spire Cloud requires a stable, high-performing internet connection for an optimal user experience. This article outlines the recommended internet speeds and latency guidelines, as well as how to test latency to the AWS regions used by Spire Cloud without using the ping command as AWS Security Groups blocks ping commands. 

Internet Speed Requirements

For a good Spire Cloud experience, the client’s internet connection should meet or exceed the following requirements:

• Download speed: At least 50 Mbps
• Upload speed: At least 10 Mbps

Higher internet speeds may provide improved performance, particularly when multiple users are accessing Spire Cloud at the same time.

Latency Guidelines

Latency measures the time it takes for data to travel between the client’s location and the Spire Cloud environment. Lower latency generally provides a more responsive experience.

Use the psping utility to test latency to the AWS regions used by Spire Cloud.

Testing Latency

Perform the following steps from a computer at the client’s location.

1. Download the PsTools package from Microsoft Sysinternals.

   Download PsTools from Microsoft Sysinternals

2. Extract the downloaded ZIP file to a location such as the Downloads folder.
3. Open File Explorer and navigate to the folder where you extracted the PsTools files.

4. Click the address bar at the top of the File Explorer window, type cmd, and press Enter.

   This opens a Command Prompt with the current directory set to the PsTools folder.

5. Run the following commands to test latency to the AWS regions:

psping rds.us-east-2.amazonaws.com:443 
psping rds.us-west-2.amazonaws.com:443 
psping rds.ca-central-1.amazonaws.com:443 
psping rds.ca-west-1.amazonaws.com:443

6. Review the results returned by each command. Compare the reported latency with the guidelines in the Latency Guidelines section.

Summary

A reliable Spire Cloud connection should provide at least 50 Mbps download and 10 Mbps upload speeds. For the best user experience, latency should be as low as possible, with latency below 30 ms considered excellent.

If the client’s internet connection does not meet these guidelines, investigate the local network, internet service, and connection to the applicable AWS region before troubleshooting Spire Cloud itself.