Quote Originally Posted by Polymachos View Post
The 45 ms have been there for ages; I am attached to an old ADSL line that can do 16 Mbit at best, the long ping is probably linked to that. The government is promising 'broadband everywhere' all the time - whatever they mean with that, they called 2 Mbit 'broadband' in the years after 2000, and currently they think it is broadband if you can get a LTE connection, or an updated tv cable (which has still this old copper lying in the ground, as had been for 30 years, and has to be shared with all neighbours in the street).
Ouch.... and here I thought Germany was so ahead of the game when it comes to internet connections. Cable will always be shared, but DOCSIS protocols with multiple frequencies used largely overcome that, when I still had cable it was on DOCSIS 3.0, and I know there is a EuroDOCSIS standard that is pretty similar, just slightly different frequency values.

Meanwhile, I am happy with my 1 Gbps fiberoptic connection:

C:\Windows\system32>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=3ms TTL=54
Reply from 8.8.8.8: bytes=32 time=3ms TTL=54
Reply from 8.8.8.8: bytes=32 time=3ms TTL=54
Reply from 8.8.8.8: bytes=32 time=3ms TTL=54

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 3ms, Average = 3ms

I'm pretty sure that wherever my fiber hits a headend, its a datacenter with Google DNS presence. I know their "8.8.8.8" in reality is several thousands of servers spread all over the globe, and a few of them are quie close near me.



C:\Windows\system32>ping gls.lotro.com

Pinging gls.lotro.com [198.252.160.30] with 32 bytes of data:
Reply from 198.252.160.30: bytes=32 time=67ms TTL=232
Reply from 198.252.160.30: bytes=32 time=67ms TTL=232
Reply from 198.252.160.30: bytes=32 time=67ms TTL=232
Reply from 198.252.160.30: bytes=32 time=67ms TTL=232

Ping statistics for 198.252.160.30:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 67ms, Maximum = 67ms, Average = 67ms


Lotro @ 67ms is pretty solid, considering I am 4,000+ km+ or 2,500+ miles away from the SSG Datacenter.

One thing to note: When you do trace routes, you may notice that hops in between lose packets or respond slower. This is done deliberately. Major backbone providers with core routers often put ICMP responses to the lowest possible priority, in order to stave off major DDOS attacks against their network.... but they pass through ICMP requests with normal priority. So a ping directly to gls.lotro.com is a lot better to figure out what your speed is to the datacenter instead of relying on the nodes/hops in between. Just a thought