please help check latency and route for different ISP's

F

flenters

Well-Known Member
Joined
Oct 14, 2005
Messages
341
Reaction score
15
Hi All,

If at all possible i would like to gather some information around routing and latency to - > 185.40.64.65

If you can do a normal ping and tracert and post the results with your ISP that would be great.

This is to -> prod.euw1.lol.riotgames.com I am trying to decide on a new fibre ISP and this will help me in my decision.

Thanks
 
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.101.11 - 0 | 47 | 47 | 0 | 0 | 0 | 0 |
| 41.78.7.1 - 0 | 47 | 47 | 2 | 3 | 22 | 2 |
| 129-205-163-229.dynamic.macrolan.co.za - 0 | 47 | 47 | 2 | 4 | 37 | 14 |
| ae0.2330.rtr1-c10d13-tc2.macrolan.co.za - 0 | 47 | 47 | 1 | 1 | 16 | 1 |
| 105.22.42.217 - 0 | 47 | 47 | 1 | 2 | 51 | 1 |
| ce-0-2-0-0.cr-01-jnb.za.seacomnet.com - 0 | 47 | 47 | 161 | 164 | 168 | 166 |
| xe-0-0-0-9.cr-01-cpt.za.seacomnet.com - 0 | 47 | 47 | 161 | 162 | 164 | 164 |
| xe-0-1-0-4.cr-01-lhr.uk.seacomnet.com - 0 | 47 | 47 | 156 | 158 | 160 | 158 |
| ae-3-0.pp-01-lhr.uk.seacomnet.com - 0 | 47 | 47 | 156 | 157 | 181 | 159 |, 163
| linx-j.riotdirect.net - 0 | 47 | 47 | 169 | 169 | 170 | 170 |
| 104.160.144.52 - 0 | 47 | 47 | 157 | 157 | 157 | 157 |
| ae-32.br01.ams02.riotdirect.net - 37 | 19 | 12 | 0 | 164 | 166 | 164 |
| 104.160.141.101 - 0 | 47 | 47 | 167 | 167 | 178 | 167 |
| 104.160.141.105 - 0 | 47 | 47 | 164 | 164 | 167 | 167 |
| 185.40.64.65 - 0 | 47 | 47 | 163 | 163 | 164 | 164 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Seacom JHB Vumatel, 163ms via PING. Best is 171ms in game.
 
i dont think we will see anything better than 160ms, anyone from cool ideas want to run the same test?
 
traceroute to 185.40.64.65 (185.40.64.65), 64 hops max, 52 byte packets
1 gateway.ibox.za.net (10.23.23.1) 0.613 ms 0.346 ms 0.322 ms
2 * * *
3 cpt-rx2.ip.adsl.co.za (169.1.5.82) 4.663 ms 5.504 ms 3.757 ms
4 cpt-net1.ip.adsl.co.za (169.1.5.128) 4.207 ms 4.118 ms 3.084 ms
5 196.25.26.65 (196.25.26.65) 5.451 ms 6.536 ms 3.503 ms
6 10.189.30.10 (10.189.30.10) 169.393 ms 166.008 ms 163.491 ms
7 pr02.fra02.riotdirect.net (80.81.193.162) 165.093 ms 170.199 ms 167.075 ms
8 * * *
9 * * *
10 104.160.141.103 (104.160.141.103) 172.177 ms 173.872 ms 171.122 ms
11 104.160.141.107 (104.160.141.107) 176.485 ms 176.880 ms 173.652 ms
12 185.40.64.65 (185.40.64.65) 172.666 ms 173.611 ms 174.169 ms

AH Fibre, Openserve, CPT

Home Connect usually have great pings, maybe someone on them can do a traceroute for you.
 
CrypticZA said:
Cool Ideas is being DDoSed again so we can't do this for you :)
Click to expand...
hahaahh looks like evey ISP has there own problems. I am currently on evonet/ crystal web and they have some serious routing issues. averaging around 240ms via WACS hence the reason i would like to move to another ISP
 
flenters said:
hahaahh looks like evey ISP has there own problems. I am currently on evonet/ crystal web and they have some serious routing issues. averaging around 240ms via WACS hence the reason i would like to move to another ISP
Click to expand...
WebSquad and Cool Ideas pings are very similar from what i have tested, in Overwatch they get more or less the exact same pings since they both use either Cogent or HE (correct me if i am wrong).
 
Websquad 100/100 from CPT.
Code: 
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                              router.lan -    0 |  103 |  103 |    0 |    0 |    0 |    0 |
|          as-vuma.cp-gwf-02.za.ws.net.za -    0 |  103 |  103 |    2 |    4 |   62 |   13 |
|                         160.119.233.129 -    0 |  103 |  103 |    2 |    3 |   30 |    2 |
|             core.as-01.cp1.za.ws.net.za -    0 |  103 |  103 |    1 |    1 |    2 |    1 |
|             core.cr-01.cp1.za.ws.net.za -    0 |  103 |  103 |    1 |    1 |    2 |    1 |
|        core.pe-xe-ip01.cp1.za.ws.net.za -    0 |  103 |  103 |    1 |    1 |    6 |    1 |
|                           197.157.79.33 -    0 |  103 |  103 |  146 |  148 |  193 |  150 |
|        cr1-gwf-esr1-gi0-0-3.wolcomm.net -    0 |  103 |  103 |  150 |  150 |  152 |  150 |
|        agr2-gwf-cr1-gi0-0-0.wolcomm.net -    0 |  103 |  103 |  150 |  150 |  185 |  150 |
|                   No response from host -  100 |   21 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   21 |    0 |    0 |    0 |    0 |    0 |
|                          197.157.77.131 -    0 |  103 |  103 |  150 |  150 |  151 |  150 |
|          riotgames.no-dns-yet.lonap.net -    0 |  103 |  103 |  146 |  146 |  147 |  146 |
|                          104.160.144.52 -    0 |  103 |  103 |  146 |  146 |  147 |  146 |
|         ae-32.br01.ams02.riotdirect.net -    0 |  103 |  103 |  151 |  151 |  153 |  152 |
|                         104.160.141.101 -    0 |  103 |  103 |  151 |  151 |  156 |  151 |
|                         104.160.141.105 -    0 |  103 |  103 |  151 |  151 |  155 |  151 |
|                            185.40.64.65 -    0 |  103 |  103 |  151 |  151 |  155 |  151 |
|________________________________________________|______|______|______|______|______|______|
 
Packetsky via Vumatel in JHB
Pinging prod.euw1.lol.riotgames.com [185.40.64.65] with 32 bytes of data:
Reply from 185.40.64.65: bytes=32 time=165ms TTL=239
Reply from 185.40.64.65: bytes=32 time=164ms TTL=239
Reply from 185.40.64.65: bytes=32 time=164ms TTL=239
Reply from 185.40.64.65: bytes=32 time=165ms TTL=239

Tracing route to prod.euw1.lol.riotgames.com [185.40.64.65]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 2 ms 2 ms 3 ms 102.141.240.129
3 5 ms 2 ms 2 ms vumaservices33.packetsky.net [169.239.179.33]
4 * * * Request timed out.
5 * * * Request timed out.
6 4 ms 7 ms 2 ms 154.117.141.1
7 * * * Request timed out.
8 161 ms 158 ms 159 ms ce-0-2-0-0.cr-02-jnb.za.seacomnet.com [105.16.28.2]
9 158 ms 158 ms 157 ms xe-0-0-0-8.cr-02-cpt.za.seacomnet.com [105.16.9.182]
10 162 ms 157 ms 158 ms xe-0-1-0-1.cr-02-lhr.uk.seacomnet.com [105.16.10.202]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 164 ms 165 ms 166 ms 185.40.64.65

Trace complete.
 
Code: 
Microsoft Windows [Version 10.0.18363.535]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Users   >ping 185.40.64.65

Pinging 185.40.64.65 with 32 bytes of data:
Reply from 185.40.64.65: bytes=32 time=188ms TTL=242
Reply from 185.40.64.65: bytes=32 time=187ms TTL=242
Reply from 185.40.64.65: bytes=32 time=187ms TTL=242
Reply from 185.40.64.65: bytes=32 time=187ms TTL=242

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

C:\Users   >tracert 185.40.64.65

Tracing route to 185.40.64.65 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms   [10.0.0.2]
  2     *        *        *     Request timed out.
  3     7 ms    14 ms     4 ms  105-187-235-17.telkomsa.net [105.187.235.17]
  4     5 ms     3 ms     3 ms  105-187-235-18.telkomsa.net [105.187.235.18]
  5     4 ms     3 ms     3 ms  ipc-aggr-1.north.telkomsa.net [105.224.0.13]
  6     5 ms     5 ms     5 ms  105-187-234-97.telkomsa.net [105.187.234.97]
  7     5 ms     5 ms    22 ms  196.25.179.245
  8   182 ms   182 ms   182 ms  10.189.30.10
  9   181 ms     *        *     pr02.fra02.riotdirect.net [80.81.193.162]
10     *        *        *     Request timed out.
11     *        *        *     Request timed out.
12   187 ms   187 ms   187 ms  104.160.141.103
13   188 ms   187 ms   187 ms  104.160.141.107
14   187 ms   187 ms   187 ms  185.40.64.65

Trace complete.

ASP: OS 10/5 fibre PTA East
ISP: Telkom
 
flenters said:
Hi All,

If at all possible i would like to gather some information around routing and latency to - > 185.40.64.65

If you can do a normal ping and tracert and post the results with your ISP that would be great.

This is to -> prod.euw1.lol.riotgames.com I am trying to decide on a new fibre ISP and this will help me in my decision.

Thanks
Click to expand...
Cool Ideas on Vumatel in Cape Town, Northern Suburbs

758178
758172
 
Last edited:
thank you everyone looks like cool ideas is the winner do we know what provider they use for international bandwidth, seacom, wacs, safe ...etc
 
Mind the Speed/Frogfoot from Cape Town:

PING 185.40.64.65 (185.40.64.65): 56 data bytes
64 bytes from 185.40.64.65: icmp_seq=0 ttl=245 time=149.631 ms
64 bytes from 185.40.64.65: icmp_seq=1 ttl=245 time=148.557 ms
64 bytes from 185.40.64.65: icmp_seq=2 ttl=245 time=148.621 ms
64 bytes from 185.40.64.65: icmp_seq=3 ttl=245 time=148.286 ms
64 bytes from 185.40.64.65: icmp_seq=4 ttl=245 time=148.350 ms
64 bytes from 185.40.64.65: icmp_seq=5 ttl=245 time=148.464 ms
64 bytes from 185.40.64.65: icmp_seq=6 ttl=245 time=148.538 ms
64 bytes from 185.40.64.65: icmp_seq=7 ttl=245 time=148.433 ms
64 bytes from 185.40.64.65: icmp_seq=8 ttl=245 time=148.503 ms
64 bytes from 185.40.64.65: icmp_seq=9 ttl=245 time=148.374 ms

--- 185.40.64.65 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 148.286/148.576/149.631/0.365 ms

traceroute to 185.40.64.65 (185.40.64.65), 64 hops max, 72 byte packets
1 securitygateway (10.0.1.1) 0.653 ms 0.308 ms 0.241 ms
2 129.205.55.1 (129.205.55.1) 2.642 ms 2.148 ms 1.970 ms
3 4-68-148-197.as37497.za.net (197.148.68.4) 2.667 ms 2.018 ms 1.957 ms
4 14-71-148-197.as37497.za.net (197.148.71.14) 142.579 ms 142.822 ms 142.407 ms
5 37-66-148-197.as37497.za.net (197.148.66.37) 142.257 ms 142.614 ms 142.516 ms
6 linx-j.riotdirect.net (195.66.226.186) 143.003 ms 142.847 ms 142.994 ms
7 104.160.144.54 (104.160.144.54) 143.046 ms 142.832 ms 142.973 ms
8 ae-32.br01.ams02.riotdirect.net (104.160.159.49) 148.571 ms 148.542 ms 148.354 ms
9 104.160.141.101 (104.160.141.101) 148.617 ms 148.644 ms 148.425 ms
10 104.160.141.105 (104.160.141.105) 148.553 ms 149.775 ms 148.439 ms
11 185.40.64.65 (185.40.64.65) 148.339 ms 148.728 ms 148.394 ms
 
flenters said:
thank you everyone looks like cool ideas is the winner do we know what provider they use for international bandwidth, seacom, wacs, safe ...etc
Click to expand...
We use WACS to London.
 
smc said:
Mind the Speed/Frogfoot from Cape Town:

traceroute to 185.40.64.65 (185.40.64.65), 64 hops max, 72 byte packets
1 securitygateway (10.0.1.1) 0.653 ms 0.308 ms 0.241 ms
2 129.205.55.1 (129.205.55.1) 2.642 ms 2.148 ms 1.970 ms
3 4-68-148-197.as37497.za.net (197.148.68.4) 2.667 ms 2.018 ms 1.957 ms
4 14-71-148-197.as37497.za.net (197.148.71.14) 142.579 ms 142.822 ms 142.407 ms
5 37-66-148-197.as37497.za.net (197.148.66.37) 142.257 ms 142.614 ms 142.516 ms
6 linx-j.riotdirect.net (195.66.226.186) 143.003 ms 142.847 ms 142.994 ms
7 104.160.144.54 (104.160.144.54) 143.046 ms 142.832 ms 142.973 ms
8 ae-32.br01.ams02.riotdirect.net (104.160.159.49) 148.571 ms 148.542 ms 148.354 ms
9 104.160.141.101 (104.160.141.101) 148.617 ms 148.644 ms 148.425 ms
10 104.160.141.105 (104.160.141.105) 148.553 ms 149.775 ms 148.439 ms
11 185.40.64.65 (185.40.64.65) 148.339 ms 148.728 ms 148.394 ms
Click to expand...
Hold up, they are using a free domain name for reverse lookup?
 
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.88.1 - 0 | 314 | 314 | 0 | 2 | 69 | 3 |
| 10.0.1.17 - 1 | 305 | 304 | 3 | 6 | 158 | 6 |
| 45.195.4.37 - 1 | 305 | 304 | 4 | 9 | 157 | 9 |
| 154.72.43.74 - 1 | 305 | 304 | 4 | 11 | 150 | 9 |
| 154.66.247.201 - 0 | 314 | 314 | 160 | 164 | 218 | 164 |
|bb-ldn02-r01.xe.9.2.0-bb-ldn01-r01.xe.4.1.0.wiocc.net - 0 | 314 | 314 | 159 | 163 | 227 | 162 |
| 154.66.247.148 - 0 | 314 | 314 | 160 | 164 | 224 | 164 |
| 154.66.247.144 - 0 | 314 | 314 | 160 | 166 | 232 | 164 |
|bb-ldn02-r01.xe.3.0.0-bb-ldn01-r01.xe.2.0.0.wiocc.net - 0 | 314 | 314 | 159 | 165 | 223 | 163 |
| linx-j.riotdirect.net - 0 | 314 | 314 | 160 | 164 | 242 | 165 |
| 104.160.144.52 - 0 | 314 | 314 | 160 | 164 | 211 | 163 |
| ae-32.br01.ams02.riotdirect.net - 0 | 314 | 314 | 165 | 169 | 206 | 168 |
| 104.160.141.101 - 0 | 314 | 314 | 165 | 170 | 241 | 176 |
| 104.160.141.105 - 0 | 314 | 314 | 165 | 169 | 228 | 170 |
| 185.40.64.65 - 0 | 314 | 314 | 165 | 169 | 210 | 167 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X