Ping request

[KoKaRoT]

Good evening guys

Could you please be so kind to just give me some feedback on a ping request to the following address?
It is the Heros of the Strom EU server.

I will attach my results to compare and my trace route.

Thank you in advance

IP:
185.60.112.157

 

[websquadza]

You can check our looking glass: https://lg.as328137.net - select your region at the top and you can run ping/trace routes from there.

 

[JohnStarr]

C:\Users\*********>ping -t 185.60.112.157

Pinging 185.60.112.157 with 32 bytes of data:
Reply from 185.60.112.157: bytes=32 time=171ms TTL=244
Reply from 185.60.112.157: bytes=32 time=168ms TTL=244
Reply from 185.60.112.157: bytes=32 time=168ms TTL=244
Reply from 185.60.112.157: bytes=32 time=173ms TTL=244
Reply from 185.60.112.157: bytes=32 time=171ms TTL=244
Reply from 185.60.112.157: bytes=32 time=170ms TTL=244
Reply from 185.60.112.157: bytes=32 time=168ms TTL=244
Reply from 185.60.112.157: bytes=32 time=183ms TTL=244
Reply from 185.60.112.157: bytes=32 time=182ms TTL=244
Reply from 185.60.112.157: bytes=32 time=172ms TTL=244
Reply from 185.60.112.157: bytes=32 time=167ms TTL=244
Reply from 185.60.112.157: bytes=32 time=168ms TTL=244
Reply from 185.60.112.157: bytes=32 time=168ms TTL=244
Reply from 185.60.112.157: bytes=32 time=168ms TTL=244
Reply from 185.60.112.157: bytes=32 time=173ms TTL=244
Reply from 185.60.112.157: bytes=32 time=168ms TTL=244
Reply from 185.60.112.157: bytes=32 time=168ms TTL=244
Reply from 185.60.112.157: bytes=32 time=226ms TTL=244
Reply from 185.60.112.157: bytes=32 time=168ms TTL=244
Reply from 185.60.112.157: bytes=32 time=168ms TTL=244
Reply from 185.60.112.157: bytes=32 time=171ms TTL=244
Reply from 185.60.112.157: bytes=32 time=168ms TTL=244
Reply from 185.60.112.157: bytes=32 time=168ms TTL=244

Ping statistics for 185.60.112.157:
Packets: Sent = 23, Received = 23, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 167ms, Maximum = 226ms, Average = 172ms

Off a 50Mbps fibre line with Vox/Frogfoot.

 

[KoKaRoT]

Thank you John Starr, Its definitely an issue with Home Connect/Metro Fibre

 

[KoKaRoT]

You can check our looking glass: https://lg.as328137.net - select your region at the top and you can run ping/trace routes from there.

Awesome thanks, Do I use this vs my own stats and give the ISP the results?
Or is there more I'm missing?

 

[websquadza]

Awesome thanks, Do I use this vs my own stats and give the ISP the results?
Or is there more I'm missing?

Our looking glass tells you what our path and latency looks like from our JHB/CPT/DBN core (depending on your region). You also have to factor in the latency that your last mile adds.

I see from your traceroute that your first hop is about 6ms- so this is your L2 last mile latency. Will likely be the same for all ISPs (what area and FNO are you?). knowing this, and using the JHB trace on our looking glass, you can compare the two- just add 6ms to account for the last mile latency (ie from JHB core to your home)

 

[KoKaRoT]

Our looking glass tells you what our path and latency looks like from our JHB/CPT/DBN core (depending on your region). You also have to factor in the latency that your last mile adds.

I see from your traceroute that your first hop is about 6ms- so this is your L2 last mile latency. Will likely be the same for all ISPs (what area and FNO are you?). knowing this, and using the JHB trace on our looking glass, you can compare the two- just add 6ms to account for the last mile latency (ie from JHB core to your home)

I am based in South Crest/Alberton and using Metro Fibre.

Thanks for the details. I am just getting fed up with the shoulder-shrugging and "reboot your router" replies.

 

[CrypticZA]

Pinging 185.60.112.157 with 32 bytes of data:
Reply from 185.60.112.157: bytes=32 time=149ms TTL=243
Reply from 185.60.112.157: bytes=32 time=148ms TTL=243
Reply from 185.60.112.157: bytes=32 time=148ms TTL=243
Reply from 185.60.112.157: bytes=32 time=148ms TTL=243

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

CISP + Vumatel CT