League of Legends Gaming on Fibre - Lowest Ping or Lowest Latency

Napalm

Expert Member
Joined
Jun 22, 2006
Messages
2,257
Hi Gents

I'm hoping to get Fibre to the Home soon. I'm just thinking which ISP would be giving me the lowest pings for EU gaming.
What pings are you ladies/guys getting?

League of legends, Diablo and most RPG servers are hosted in EU or US regions. Most of the servers i play on is EU though.

Please do this on your fibre link. (your ISP & package)
click start. Run.
ping 104.160.141.3 -t
I then let it run for 10-20 seconds or so.
Press control+C to stop the ping checks.


I'm on Vox ADSL at the moment, Capped but not shaped. <lowest i get is around 183/184ms. sometimes jumps to 200ms but that could be someone browsing or my phone updating etc>
Reply from 104.160.141.3: bytes=32 time=184ms TTL=55
Reply from 104.160.141.3: bytes=32 time=184ms TTL=55
Reply from 104.160.141.3: bytes=32 time=185ms TTL=55
Reply from 104.160.141.3: bytes=32 time=186ms TTL=55
Reply from 104.160.141.3: bytes=32 time=184ms TTL=55

Please post results below.
 

cavedog

Honorary Master
Joined
Oct 19, 2007
Messages
13,746
The in game latency is different compared to the server ip you posted. To EUW you looking at 185ms or some from JHB, PTA. Much lower from CPT.

If you are on a ISP that uses sacs like Evonet people reported 135ms or to Brazil servers.
 

Slinetpixel

Active Member
Joined
May 10, 2016
Messages
76
PTA East 100/50 Openserve + CISP

Code:
ping 104.160.141.3
PING 104.160.141.3 (104.160.141.3) 56(84) bytes of data.
64 bytes from 104.160.141.3: icmp_seq=1 ttl=54 time=168 ms
64 bytes from 104.160.141.3: icmp_seq=2 ttl=54 time=167 ms
64 bytes from 104.160.141.3: icmp_seq=3 ttl=54 time=167 ms
64 bytes from 104.160.141.3: icmp_seq=4 ttl=54 time=168 ms
64 bytes from 104.160.141.3: icmp_seq=5 ttl=54 time=167 ms
64 bytes from 104.160.141.3: icmp_seq=6 ttl=54 time=167 ms
64 bytes from 104.160.141.3: icmp_seq=7 ttl=54 time=167 ms
64 bytes from 104.160.141.3: icmp_seq=8 ttl=54 time=167 ms
64 bytes from 104.160.141.3: icmp_seq=9 ttl=54 time=167 ms
64 bytes from 104.160.141.3: icmp_seq=10 ttl=54 time=167 ms
64 bytes from 104.160.141.3: icmp_seq=11 ttl=54 time=167 ms
64 bytes from 104.160.141.3: icmp_seq=12 ttl=54 time=167 ms
64 bytes from 104.160.141.3: icmp_seq=13 ttl=54 time=167 ms
64 bytes from 104.160.141.3: icmp_seq=14 ttl=54 time=167 ms
64 bytes from 104.160.141.3: icmp_seq=15 ttl=54 time=167 ms
^C
--- 104.160.141.3 ping statistics ---
16 packets transmitted, 15 received, 6% packet loss, time 15021ms
rtt min/avg/max/mdev = 167.462/167.684/168.156/0.555 ms
 

zolly

Expert Member
Joined
Sep 1, 2005
Messages
2,806
I'm on Vox ADSL at the moment, Capped but not shaped. <lowest i get is around 183/184ms. sometimes jumps to 200ms but that could be someone browsing or my phone updating etc>
Reply from 104.160.141.3: bytes=32 time=184ms TTL=55
Reply from 104.160.141.3: bytes=32 time=184ms TTL=55
Reply from 104.160.141.3: bytes=32 time=185ms TTL=55
Reply from 104.160.141.3: bytes=32 time=186ms TTL=55
Reply from 104.160.141.3: bytes=32 time=184ms TTL=55

Please post results below.
Location? When I was still on ADSL I was able to get about 170-180 on Crystal Web in Cape Town, back when they were still decent. Got about 180 when I moved to Vox.

On Cool Ideas in Cape Town I get approximately 155-161 in game for League of Legends and Apex.
 

cavedog

Honorary Master
Joined
Oct 19, 2007
Messages
13,746
Supersonic on Openserve


Pinging 104.160.141.3 with 32 bytes of data:
Reply from 104.160.141.3: bytes=32 time=174ms TTL=52
Reply from 104.160.141.3: bytes=32 time=174ms TTL=52
Reply from 104.160.141.3: bytes=32 time=174ms TTL=52
Reply from 104.160.141.3: bytes=32 time=174ms TTL=52
Reply from 104.160.141.3: bytes=32 time=174ms TTL=52
Reply from 104.160.141.3: bytes=32 time=174ms TTL=52
Reply from 104.160.141.3: bytes=32 time=174ms TTL=52
Reply from 104.160.141.3: bytes=32 time=174ms TTL=52
Reply from 104.160.141.3: bytes=32 time=174ms TTL=52
Reply from 104.160.141.3: bytes=32 time=174ms TTL=52
Reply from 104.160.141.3: bytes=32 time=175ms TTL=52
Reply from 104.160.141.3: bytes=32 time=174ms TTL=52
Reply from 104.160.141.3: bytes=32 time=175ms TTL=52
Reply from 104.160.141.3: bytes=32 time=174ms TTL=52
Reply from 104.160.141.3: bytes=32 time=174ms TTL=52
Reply from 104.160.141.3: bytes=32 time=174ms TTL=52
Reply from 104.160.141.3: bytes=32 time=181ms TTL=52
Reply from 104.160.141.3: bytes=32 time=174ms TTL=52
Reply from 104.160.141.3: bytes=32 time=175ms TTL=52
Reply from 104.160.141.3: bytes=32 time=174ms TTL=52
Reply from 104.160.141.3: bytes=32 time=174ms TTL=52
Reply from 104.160.141.3: bytes=32 time=188ms TTL=52
Reply from 104.160.141.3: bytes=32 time=174ms TTL=52
 

blunt

Expert Member
Joined
May 1, 2006
Messages
2,327
CISP on MTN FTTH, Cape Town

PING 104.160.141.3 (104.160.141.3): 56 data bytes
64 bytes from 104.160.141.3: icmp_seq=0 ttl=56 time=150.008 ms
64 bytes from 104.160.141.3: icmp_seq=1 ttl=56 time=151.903 ms
64 bytes from 104.160.141.3: icmp_seq=2 ttl=56 time=149.287 ms
64 bytes from 104.160.141.3: icmp_seq=3 ttl=56 time=149.104 ms
64 bytes from 104.160.141.3: icmp_seq=4 ttl=56 time=150.167 ms
64 bytes from 104.160.141.3: icmp_seq=5 ttl=56 time=150.034 ms
64 bytes from 104.160.141.3: icmp_seq=6 ttl=56 time=150.113 ms
64 bytes from 104.160.141.3: icmp_seq=7 ttl=56 time=149.928 ms
64 bytes from 104.160.141.3: icmp_seq=8 ttl=56 time=149.980 ms
64 bytes from 104.160.141.3: icmp_seq=9 ttl=56 time=149.866 ms
64 bytes from 104.160.141.3: icmp_seq=10 ttl=56 time=149.573 ms
64 bytes from 104.160.141.3: icmp_seq=11 ttl=56 time=150.289 ms
64 bytes from 104.160.141.3: icmp_seq=12 ttl=56 time=150.770 ms
64 bytes from 104.160.141.3: icmp_seq=13 ttl=56 time=149.941 ms
64 bytes from 104.160.141.3: icmp_seq=14 ttl=56 time=150.326 ms
64 bytes from 104.160.141.3: icmp_seq=15 ttl=56 time=149.259 ms
64 bytes from 104.160.141.3: icmp_seq=16 ttl=56 time=149.457 ms
64 bytes from 104.160.141.3: icmp_seq=17 ttl=56 time=149.321 ms

--- 104.160.141.3 ping statistics ---
18 packets transmitted, 18 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 149.104/149.963/151.903/0.634 ms
 

Hype

Well-Known Member
Joined
Jan 31, 2005
Messages
156
CISP - Vumatel Trenched - JHB

Reply from 104.160.141.3: bytes=32 time=164ms TTL=55
Reply from 104.160.141.3: bytes=32 time=164ms TTL=55
Reply from 104.160.141.3: bytes=32 time=164ms TTL=55
Reply from 104.160.141.3: bytes=32 time=164ms TTL=55
Reply from 104.160.141.3: bytes=32 time=164ms TTL=55
Reply from 104.160.141.3: bytes=32 time=164ms TTL=55
Reply from 104.160.141.3: bytes=32 time=164ms TTL=55
Reply from 104.160.141.3: bytes=32 time=164ms TTL=55
Reply from 104.160.141.3: bytes=32 time=164ms TTL=55
Reply from 104.160.141.3: bytes=32 time=164ms TTL=55
Reply from 104.160.141.3: bytes=32 time=164ms TTL=55
Reply from 104.160.141.3: bytes=32 time=165ms TTL=55
Reply from 104.160.141.3: bytes=32 time=164ms TTL=55
Reply from 104.160.141.3: bytes=32 time=164ms TTL=55
Reply from 104.160.141.3: bytes=32 time=164ms TTL=55
Reply from 104.160.141.3: bytes=32 time=164ms TTL=55
Reply from 104.160.141.3: bytes=32 time=164ms TTL=55
Reply from 104.160.141.3: bytes=32 time=164ms TTL=55
Reply from 104.160.141.3: bytes=32 time=164ms TTL=55
Reply from 104.160.141.3: bytes=32 time=164ms TTL=55
Reply from 104.160.141.3: bytes=32 time=164ms TTL=55

Ping statistics for 104.160.141.3:
Packets: Sent = 68, Received = 68, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 164ms, Maximum = 168ms, Average = 164ms
 

Lope

Well-Known Member
Joined
Apr 19, 2007
Messages
468
Webafrica 20Mbps Uncapped fiber ping to eu.battle.net ... Overwatch is unplayable. Much worse than capped 4Mbps ADSL.
Webafrica FTL

Code:
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=65 ttl=52 time=373 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=66 ttl=52 time=325 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=67 ttl=52 time=561 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=68 ttl=52 time=1002 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=69 ttl=52 time=153 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=70 ttl=52 time=1016 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=71 ttl=52 time=476 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=73 ttl=52 time=510 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=75 ttl=52 time=1026 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=76 ttl=52 time=1005 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=77 ttl=52 time=584 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=79 ttl=52 time=513 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=80 ttl=52 time=205 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=81 ttl=52 time=652 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=82 ttl=52 time=677 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=83 ttl=52 time=732 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=84 ttl=52 time=216 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=85 ttl=52 time=268 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=86 ttl=52 time=152 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=87 ttl=52 time=199 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=88 ttl=52 time=266 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=89 ttl=52 time=387 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=90 ttl=52 time=308 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=91 ttl=52 time=390 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=92 ttl=52 time=396 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=93 ttl=52 time=1034 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=94 ttl=52 time=821 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=95 ttl=52 time=434 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=96 ttl=52 time=486 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=97 ttl=52 time=482 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=98 ttl=52 time=152 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=99 ttl=52 time=434 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=100 ttl=52 time=490 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=101 ttl=52 time=153 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=102 ttl=52 time=1027 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=103 ttl=52 time=603 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=104 ttl=52 time=1016 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=105 ttl=52 time=1003 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=106 ttl=52 time=1001 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=108 ttl=52 time=154 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=109 ttl=52 time=270 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=110 ttl=52 time=207 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=111 ttl=52 time=204 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=112 ttl=52 time=836 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=113 ttl=52 time=302 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=114 ttl=52 time=374 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=115 ttl=52 time=860 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=116 ttl=52 time=915 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=117 ttl=52 time=909 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=118 ttl=52 time=372 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=119 ttl=52 time=175 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=120 ttl=52 time=152 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=121 ttl=52 time=944 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=122 ttl=52 time=511 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=123 ttl=52 time=1025 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=124 ttl=52 time=1002 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=125 ttl=52 time=1003 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=126 ttl=52 time=1002 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=127 ttl=52 time=373 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=129 ttl=52 time=152 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=130 ttl=52 time=312 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=131 ttl=52 time=170 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=132 ttl=52 time=612 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=133 ttl=52 time=268 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=134 ttl=52 time=242 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=135 ttl=52 time=308 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=136 ttl=52 time=802 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=137 ttl=52 time=1016 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=138 ttl=52 time=841 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=139 ttl=52 time=293 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=140 ttl=52 time=528 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=141 ttl=52 time=156 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=142 ttl=52 time=1021 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=143 ttl=52 time=1001 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=144 ttl=52 time=475 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=145 ttl=52 time=206 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=146 ttl=52 time=481 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=147 ttl=52 time=1028 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=148 ttl=52 time=509 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=149 ttl=52 time=476 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=150 ttl=52 time=579 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=151 ttl=52 time=506 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=153 ttl=52 time=637 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=154 ttl=52 time=816 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=155 ttl=52 time=1008 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=156 ttl=52 time=1002 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=157 ttl=52 time=182 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=158 ttl=52 time=202 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=159 ttl=52 time=1029 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=160 ttl=52 time=898 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=161 ttl=52 time=269 ms
 

cantankerous

Active Member
Joined
Oct 23, 2018
Messages
35
Websquad 1000/100 - Vumatel Trenched - JHB (Over WiFi, sorry, too lazy to get a cord out)

Code:
PING 104.160.141.3 (104.160.141.3): 56 data bytes
64 bytes from 104.160.141.3: icmp_seq=0 ttl=52 time=171.682 ms
64 bytes from 104.160.141.3: icmp_seq=1 ttl=52 time=172.086 ms
64 bytes from 104.160.141.3: icmp_seq=2 ttl=52 time=171.478 ms
64 bytes from 104.160.141.3: icmp_seq=3 ttl=52 time=171.720 ms
64 bytes from 104.160.141.3: icmp_seq=4 ttl=52 time=172.235 ms
64 bytes from 104.160.141.3: icmp_seq=5 ttl=52 time=172.503 ms
64 bytes from 104.160.141.3: icmp_seq=6 ttl=52 time=171.425 ms
64 bytes from 104.160.141.3: icmp_seq=7 ttl=52 time=171.954 ms
64 bytes from 104.160.141.3: icmp_seq=8 ttl=52 time=172.489 ms
64 bytes from 104.160.141.3: icmp_seq=9 ttl=52 time=172.081 ms
64 bytes from 104.160.141.3: icmp_seq=10 ttl=52 time=171.411 ms
64 bytes from 104.160.141.3: icmp_seq=11 ttl=52 time=171.402 ms
64 bytes from 104.160.141.3: icmp_seq=12 ttl=52 time=171.940 ms
64 bytes from 104.160.141.3: icmp_seq=13 ttl=52 time=172.078 ms
64 bytes from 104.160.141.3: icmp_seq=14 ttl=52 time=173.486 ms
 

Napalm

Expert Member
Joined
Jun 22, 2006
Messages
2,257
At work(CPT) on Vox 200mbit Fibre.

ping 104.160.141.3 -t
Pinging 104.160.141.3 with 32 bytes of data:
Reply from 104.160.141.3: bytes=32 time=168ms TTL=44
Reply from 104.160.141.3: bytes=32 time=168ms TTL=44
Reply from 104.160.141.3: bytes=32 time=168ms TTL=44
Reply from 104.160.141.3: bytes=32 time=168ms TTL=44
Reply from 104.160.141.3: bytes=32 time=168ms TTL=44
Reply from 104.160.141.3: bytes=32 time=168ms TTL=44
Reply from 104.160.141.3: bytes=32 time=168ms TTL=44
Ping statistics for 104.160.141.3:
Packets: Sent = 7, Received = 7, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 168ms, Maximum = 168ms, Average = 168ms
Control-C
 

zolly

Expert Member
Joined
Sep 1, 2005
Messages
2,806
At work(CPT) on Vox 200mbit Fibre.

ping 104.160.141.3 -t
Pinging 104.160.141.3 with 32 bytes of data:
Reply from 104.160.141.3: bytes=32 time=168ms TTL=44
Reply from 104.160.141.3: bytes=32 time=168ms TTL=44
Reply from 104.160.141.3: bytes=32 time=168ms TTL=44
Reply from 104.160.141.3: bytes=32 time=168ms TTL=44
Reply from 104.160.141.3: bytes=32 time=168ms TTL=44
Reply from 104.160.141.3: bytes=32 time=168ms TTL=44
Reply from 104.160.141.3: bytes=32 time=168ms TTL=44
Ping statistics for 104.160.141.3:
Packets: Sent = 7, Received = 7, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 168ms, Maximum = 168ms, Average = 168ms
Control-C
For Cape Town that's pretty poop. My work gets fibre services directly from Seacom and here's what we get to the same IP:

Pinging 104.160.141.3 with 32 bytes of data:
Reply from 104.160.141.3: bytes=32 time=151ms TTL=57
Reply from 104.160.141.3: bytes=32 time=151ms TTL=57
Reply from 104.160.141.3: bytes=32 time=151ms TTL=57
Reply from 104.160.141.3: bytes=32 time=152ms TTL=57

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

At home it's only marginally more.
 

sybawoods

Expert Member
Joined
Aug 4, 2003
Messages
1,145
CISP, Octotel, 200/200

Pinging 104.160.141.3 with 32 bytes of data:
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
 

Napalm

Expert Member
Joined
Jun 22, 2006
Messages
2,257
Is this what you would see ingame too? (i'm in CPT)
CISP, Octotel, 200/200

Pinging 104.160.141.3 with 32 bytes of data:
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
Reply from 104.160.141.3: bytes=32 time=147ms TTL=57
 

cavedog

Honorary Master
Joined
Oct 19, 2007
Messages
13,746
Is this what you would see ingame too? (i'm in CPT)
In game will be higher. Also EUW make use of different server locations as far as I know. Some games I get 177ms from PTA and then next game it's 193ms then 185ms so I think it depends.
 

Napalm

Expert Member
Joined
Jun 22, 2006
Messages
2,257
thats the pings i currently get..

If i ping that IP. that is what i get ingame +- (maybe 1ms or 2ms here and there)

Ingame i normally get around the 183ms to 190ms

C:\Users\Haz>ping 104.160.141.3

Pinging 104.160.141.3 with 32 bytes of data:
Reply from 104.160.141.3: bytes=32 time=181ms TTL=51
Reply from 104.160.141.3: bytes=32 time=173ms TTL=51
Reply from 104.160.141.3: bytes=32 time=175ms TTL=51
Reply from 104.160.141.3: bytes=32 time=184ms TTL=51
 
Top