Live data from Hacker News

AWS data center latencies, visualized

benjdd.com

211–220 of 223 posts

Re: AWS data center latencies, visualized

#211

Earlier quoted context omitted.

As a quick workaround, you can set a CSS filter on the whole page: Either use dev tools to put a rule `filter: hue-rotate(60deg);` on the `body` element, or simply run `javascript:void(document.body.style.filter='hue-rotate(60deg)')` from the url bar.

let i = 0; setInterval(() => document.body.style.filter=`hue-rotate(${i++}deg)`, 16); Disco mode! (better to use requestAnimationFrame but I'm lazy atm)

There you go:

  let i = 0;
  function bump() {
      document.body.style.filter=`hue-rotate(${i+=2}deg)`, 16;
      requestAnimationFrame(bump);
  }
  requestAnimationFrame(bump);

Re: AWS data center latencies, visualized

#213

Earlier quoted context omitted.

Low-bandwidth/low-latency people tend to also demand high reliability and consistency. A low-orbit satellite network might be fast but, because sats move to quickly, cannot be consistent in that speed. Sats also won't ever connect data centers other than perhaps for administrative stuff. The bandwidth/reliability/growth potential just isn't there compared to bundles of traditional fiber.

> sats move to quickly, cannot be consistent Satellites in geostationary orbit are a (very common) thing.

Geostationary is so much further than LEO though so worse latency

Re: AWS data center latencies, visualized

#214
post #206

Earlier quoted context omitted.

Doesn't look like this is a ping[0]! Which is good. Rather it is a socket stream connecting over tcp/443. Ping (ICMP) would be a poor metric. [0] https://github.com/mda590/cloudping.co/blob/8918ee8d7e632765...

why 443? are you assuming ssl here? serious question, I'm not sure. But if it is, wouldn't it be hard to disregard the weight of SSL in the metric?

tcp/443 is likely an open port on the target service (Dynamodb based on the domain name). TLS is not involved.

ICMP ECHO would be a bad choice as it is deprioritized by routers[0].

[0] https://archive.nanog.org/sites/default/files/traceroute-201...

Re: AWS data center latencies, visualized

#216
post #206

Earlier quoted context omitted.

Doesn't look like this is a ping[0]! Which is good. Rather it is a socket stream connecting over tcp/443. Ping (ICMP) would be a poor metric. [0] https://github.com/mda590/cloudping.co/blob/8918ee8d7e632765...

why 443? are you assuming ssl here? serious question, I'm not sure. But if it is, wouldn't it be hard to disregard the weight of SSL in the metric?

The script connects to well known 'dynamodb.' + region_name + '.amazonaws.com' server that expects HTTPS

Re: AWS data center latencies, visualized

#217

I have red-green color blindness, which makes it hard/impossible for me to distinguish between the 200ms lines. This affects about 8% of male population btw, maybe you can add a color-blind mode, very nice visualization otherwise!

It's sad that this is the top comment for the post. Many people have stopped posting their crappy work online due to harsh comments like yours. There's no easy reply to your comment. Maybe we should be less critical specially with "Make it fit for my workflow" type comment, and more so if it is built by some random guy in their free time, and not say a project which is asking money.

Oh, calm down. Some people aren’t aware of this, someone pointed it out.

Re: AWS data center latencies, visualized

#218

Earlier quoted context omitted.

How do you know there aren't any cables between Ireland and the main European continent? I'm genuinely curious where this is published.

You can search google for [undersea cable map] but this one is the best: https://www.submarinecablemap.com This will show you everything connected to Ireland: https://www.submarinecablemap.com/country/ireland

There’ll be one to France as of 2026 (as part of this project: https://en.wikipedia.org/wiki/Celtic_Interconnector)

Re: AWS data center latencies, visualized

#219
post #65

Obviously the biggest contribution to latency is distance. But there's also some close-ish regions with poor latency because there's not fiber running directly between them (for example, over the poles) Are there an examples of regions which dramatically violate the triangle equality? (That is, where the A--C latency is much worse than the best A--B + B--C latencies)? Just as a curiosity, could you use that idea to "…

There’s very few and poor cables in the areas between Russia/Mongolia/India.

AFAIK, the latency from Mumbai to southern Russia (not that far in distance) is surprisingly high. Much higher than from e.g. Frankfurt to Moscow. Don’t know if it’s enough to violate the triangle equality between Frankfurt-Moscow-Mumbai.

Re: AWS data center latencies, visualized

#220

Earlier quoted context omitted.

1/2 c in circuit boards (FR-4), 1/3 c in cables, two useful numbers to remember.

Depends on what kind of cable? As twisted pair network cable is at 2/3.

What an embarrassing typo! I was thinking of 0.66, and somehow I thought 0.66 = 1/3 (must've been distracted by the "2" in 1/2). I should've written 0.66 or 2/3.
Post reply on HN