Test speed and pings to all DigitalOcean, Linode, AWS, GCP, and Vultr regions
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Jake Jarvis 215f363381
Update README.md
1 year ago
LICENSE.md MIT license 2 years ago
README.md Update README.md 1 year ago
ping.sh add/update regions 1 year ago
screenshot-ping.png actual screenshots 2 years ago
screenshot-speed.png updated speed screenshot 2 years ago
speed.sh add/update regions 1 year ago

README.md

Speed & Ping Tests for Cloud Hosting Providers

Notes

  • Speed tests for each region of each provider (there are over 80) can use up to 100MB of data. Be careful if your ISP caps your data usage!
  • Files are downloaded via HTTP (not HTTPS) to get pure speed without encryption overhead.
  • Tests can always be influenced by outside variables. Run the scripts multiple times if you want to ensure accuracy. Evil throttling ISPs can mess up the results too, of course.
  • If it looks like the script has crashed, the current test is probably just taking a while — especially when testing far-away regions. If you already know that testing other continents is futile, just remove them from the for loops in speed.sh.
  • Thank you to CloudHarmony for providing AWS and GCP endpoints for testing!

Usage

If you trust me (which you shouldn't, please don't trust random people on the internet!) these commands will download and run the scripts automatically:

wget -qO - https://raw.githubusercontent.com/jakejarvis/datacenter-speed-tests/master/ping.sh | bash
wget -qO - https://raw.githubusercontent.com/jakejarvis/datacenter-speed-tests/master/speed.sh | bash

Or, clone the repository and make sure the scripts are executable before running:

git clone https://github.com/jakejarvis/datacenter-speed-tests.git
cd datacenter-speed-tests
chmod +x ping.sh && chmod +x speed.sh
./ping.sh
./speed.sh

Providers & Regions

Scripts will test speed and pings to the following data centers:

DigitalOcean

  • NYC1
  • NYC2
  • NYC3
  • SFO1
  • SFO2
  • SFO3
  • TOR1
  • LON1
  • FRA1
  • AMS2
  • AMS3
  • SGP1
  • BLR1

Linode

  • Newark
  • Atlanta
  • Dallas
  • Fremont
  • London
  • Frankfurt
  • Singapore
  • Tokyo
  • Sydney
  • Toronto
  • Mumbai

Amazon Web Services

  • us-east-1
  • us-east-2
  • us-west-1
  • us-west-2
  • ca-central-1
  • eu-north-1
  • eu-central-1
  • eu-west-1
  • eu-west-2
  • eu-west-3
  • eu-south-1
  • ap-northeast-1
  • ap-northeast-2
  • ap-northeast-3
  • ap-south-1
  • ap-southeast-1
  • ap-southeast-2
  • ap-east-1
  • sa-east-1
  • me-south-1
  • af-south-1

Google Cloud

  • us-east1
  • us-east4
  • us-west1
  • us-west2
  • us-west3
  • us-central1
  • northamerica-northeast1
  • asia-east1
  • asia-east2
  • asia-northeast1
  • asia-northeast2
  • asia-south1
  • asia-southeast1
  • australia-southeast1
  • europe-north1
  • europe-west1
  • europe-west2
  • europe-west3
  • europe-west4
  • europe-west6
  • southamerica-east1

Vultr/Choopa

  • nj-us
  • il-us
  • ga-us
  • fl-us
  • tx-us
  • sjo-ca-us
  • lax-ca-us
  • wa-us
  • tor-ca
  • fra-de
  • ams-nl
  • par-fr
  • lon-gb
  • syd-au
  • sgp
  • hnd-jp
  • sel-kor

Screenshots

speed screenshot ping screenshot


Inspired by https://www.reddit.com/r/webdev/comments/6ylmki/heres_an_easy_way_to_find_the_nearest/