It looks like this tool reports the mean time for a network roundtrip, whereas gcping.com reports the one-way latency. That's a bit confusing..

I have no strong opinion what is better, but it would be nice to mention this difference. Alternatively, the tool and website could align their measurement methods.

Can we move the stylesheets and js code into separate files (.css and .js) instead of having everything in index.html? I can make a PR if this makes sense. It will make future development a bit easier.

After 155e434, we'll need to be aware of how clients cache assets. An asset bundler would help with this and open the door to more client-side options (TypeScript, wider browser support, SASS, etc). Parcel is a good option: https://parceljs.org/docs/.

Terraform fails when re-issuing the cert due to destroying and recreating the SSL cert while it is being used by the Load Balancer configuration.

Currently, -top only returns the region name. It would be great if we can return a zone name from gcping. Then, the user can create a VM in the closest region via:

gcloud compute instance create -zone $(gcping -top) vm

@imjasonh, this was your initial idea. Did you avoid implementing it for some reason?

Found a bug in the PR Close Github Action workflow where the staged Cloud Run service is not automatically deleted if the PR is merged. In case the PR is closed without a merge, then the staged Cloud Run services are deleted without issues.

I think we could get the exec time down for gcping, also make it seem a bit more responsive if we used service workers for the requests?

https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API/Using_Service_Workers

https://cloud.google.com/blog/topics/sustainability/sharing-carbon-free-energy-percentage-for-google-cloud-regions

https://github.com/GoogleCloudPlatform/region-carbon-info/blob/main/data/yearly/2019.csv

Hello,

According to the release note (link here) Paris is a new available region in GCP.

HTST max-age is currently set to 3,600.

However, according to https://hstspreload.org/, 2 years is recommended and 1 year is required as a minimum.

Hello,
please introduce release tags and versions to support stable usage, development of a homebrew formula or similiar stuff.

What do you think about that?

As in the screenshot, it'd be helpful if the table header remains visible when you scroll down.

Context: #69 (comment).

https://github.com/network-quality/server/blob/main/SERVER_SPEC.md

network-quality has posted both a server as well as a client. It could be interesting to alter our backends to use this server (or at least implement its api) as it would enable more interesting latency and network-under-load testing. The server currently should support ping frames (and has a get endpoint) that can be leveraged by the current frontend.

Hello there,

I cannot download the windows compiled binary. Its redirecting to an error.

https://storage.googleapis.com/gcping-release/gcping_windows_amd64_latest

Thanks.

It's still focused on the CLI tool and not both the CLI and the website.

I don't have permission to update it myself, or else I would 😄

Cf. https://www.terraform.io/docs/language/settings/backends/gcs.html

This will make it easier to collaborate on deployments.

It seems fitting that the CLI and the associated web app should live together in this repo.

https://github.com/imjasonh/gcping

/cc @imjasonh @crwilcox @orthros @saranshdhingra

Maybe add min, max and mean besides the current median measurement?

Tracking issue for testing in ping.

gcping cli is giving errors even though the latency is calculated:

~ ./gcping
 1.  [global]                   19.290805ms   (10 errors)
 2.  [northamerica-northeast1]  29.315077ms   (10 errors)
 3.  [northamerica-northeast2]  37.393744ms   (10 errors)
 4.  [us-east4]                 43.906334ms   (10 errors)
 5.  [us-east1]                 57.958502ms   (10 errors)
 6.  [us-central1]              61.14016ms    (10 errors)
 7.  [us-west3]                 79.048424ms   (10 errors)
 8.  [us-west1]                 91.947432ms   (10 errors)
 9.  [us-west4]                 97.665239ms   (10 errors)
10.  [us-west2]                 100.457459ms  (10 errors)
11.  [europe-west2]             108.615476ms  (10 errors)
12.  [europe-west1]             114.749269ms  (10 errors)
13.  [europe-west4]             116.063112ms  (10 errors)
14.  [europe-west3]             117.671764ms  (10 errors)
15.  [europe-west6]             124.095288ms  (10 errors)
16.  [europe-north1]            147.881739ms  (10 errors)
17.  [southamerica-east1]       155.535941ms  (10 errors)
18.  [europe-central2]          156.961643ms  (10 errors)
19.  [asia-northeast1]          181.900837ms  (10 errors)
20.  [asia-northeast2]          195.192893ms  (10 errors)
21.  [asia-northeast3]          203.282024ms  (10 errors)
22.  [asia-east1]               209.312694ms  (10 errors)
23.  [asia-east2]               219.646245ms  (10 errors)
24.  [australia-southeast1]     227.270432ms  (10 errors)
25.  [asia-southeast1]          243.766738ms  (10 errors)
26.  [asia-southeast2]          253.509767ms  (10 errors)
27.  [asia-south1]              306.502457ms  (10 errors)
28.  [asia-south2]              409.837682ms  (10 errors)
29.  [australia-southeast2]     674.204148ms  (10 errors) 

There's a web API to get the exact duration for each http request, which is more accurate than using Date and you can remove DNS lookup times.

https://developer.mozilla.org/en-US/docs/Web/API/Resource_Timing_API/Using_the_Resource_Timing_API

It's missing the new GCP region Turin (europe-west12)

Now that #32 has been merged, there are two separate configuration files:

1. one for the CLI
2. one for the webapp (also one with associated descriptions).

Instead, there should be one source of data for both the CLI and the webapp.

The HTST header is present for API calls but is not when you access https://gcping.com/.

It needs to be present at the top domain level to get included in the preload list.

I ran your GCPing.com tool today for the first time to see what my latency would be like to Dallas (US-SOUTH1) and noticed it hasn't been included in your list yet. Can you please add this region when you have a chance? Thank you!

Currently, terraform can fail due to a misconfig of addrs. It would be better if this could be added to our terraform.

sudo sysctl -w net.ipv6.conf.all.disable_ipv6=1 net.ipv6.conf.default.disable_ipv6=1 net.ipv6.conf.lo.disable_ipv6=1 > /dev/null
export APIS="googleapis.com www.googleapis.com storage.googleapis.com iam.googleapis.com container.googleapis.com cloudresourcemanager.googleapis.com run.googleapis.com iam.googleapis.com asia-east2-run.googleapis.com southamerica-east1.googleapis.com asia-south1-run.googleapis.com europe-west2-run.googleapis.com australia-southeast2-run.googleapis.com europe-north1-run.googleapis.com europe-west3-run.googleapis.com southamerica-east1-run.googleapis.com asia-southeast1-run.googleapis.com asia-northeast1-run.googleapis.com us-west3-run.googleapis.com us-central1-run.googleapis.com asia-northest2-run.googleapis.com us-east4-run.googleapis.com australia-southeast1-run.googleapis.com us-east4-run.googleapis.com europe-west3-run.googleapis.com"
for name in $APIS
do
  ipv4=$(getent ahostsv4 "$name" | head -n 1 | awk '{ print $1 }')
  grep -q "$name" /etc/hosts || ([ -n "$ipv4" ] && sudo sh -c "echo '$ipv4 $name' >> /etc/hosts")
done

Repro:

terraform plan \
    --var="image=gcr.io/gcping-devrel/ping-b5e9c300f5e9cdafa118e623a88e6b97@sha256:14ae944d9449281f08e2dfb4abac70ec43429f7fcb3e47dba3ad750a7842b53a" \
    --var='domain=gcping.com' \
    --var='project=gcping-devrel'

Hi, I know this tool was made to benchmark HTTP request latency but I'd like to have the same feature but with ICMP or TCP requests. Hosting a VPN server or such thing on GCP is really different than hosting a web server and it doesn't work the same way. Is it already possible to benchmark latency with something else than HTTP?

Thanks

GCPing is broken as the project associated with the bucket was deleted:

curl https://storage.googleapis.com/gcping-release/gcping_linux_amd64_0.0.3 > gcping && chmod +x gcping

./gcping: line 1: ProjectNotFoundThe requested project was not found.

The requested project was not found.