Hi AfriMan,
I found the following article on Battle.net's site, so I thought I would follow the instructions and pass them onto you in the hope that you can pass it onto someone who can make head or tail of it. Or, perhaps, someone here in the forums can shed some more light on the differences.
https://us.battle.net/support/en/article/performing-a-traceroute
In the article, they state that the EU Diablo 3 server's IP address is:
213.155.155.233
I did a tracert from home on my Arihost account, and then I also did one from the office (MWEB account). I know that MWEB went to great lengths to ensure that battle.net gaming latency was as good as possible when they first launched their uncapped service, and over the last few nights, I have confirmed that MWEB is having no such issues with Diablo 3. Hopefully, this information (for example why traffic goes via London on MWEB and Amsterdam on Afrihost) is of use in troubleshooting this problem. Note too, that Afrihost never seems to arrive on the same subnet 213.155.x.x as is the case with MWEB.
I have also PMed you this message.
Afrihost
MWEB
I found the following article on Battle.net's site, so I thought I would follow the instructions and pass them onto you in the hope that you can pass it onto someone who can make head or tail of it. Or, perhaps, someone here in the forums can shed some more light on the differences.
https://us.battle.net/support/en/article/performing-a-traceroute
In the article, they state that the EU Diablo 3 server's IP address is:
213.155.155.233
I did a tracert from home on my Arihost account, and then I also did one from the office (MWEB account). I know that MWEB went to great lengths to ensure that battle.net gaming latency was as good as possible when they first launched their uncapped service, and over the last few nights, I have confirmed that MWEB is having no such issues with Diablo 3. Hopefully, this information (for example why traffic goes via London on MWEB and Amsterdam on Afrihost) is of use in troubleshooting this problem. Note too, that Afrihost never seems to arrive on the same subnet 213.155.x.x as is the case with MWEB.
I have also PMed you this message.
Afrihost
Code:
$ tracert 213.155.155.233
Tracing route to 213-155-155-233.customer.teliacarrier.com [213.155.155.233]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 5 ms 5 ms 6 ms 105-236-7-129-esr-lo.mtnbusiness.co.za [105.236.7.129]
3 29 ms 25 ms 16 ms ipc-recieve-rb-1a.za.mtnbusiness.net [41.181.178.53]
4 34 ms 32 ms 16 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.120]
5 38 ms 17 ms 17 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 48 ms 45 ms 17 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 223 ms 190 ms 190 ms xe-4-1-0.edge5.Amsterdam1.Level3.net [212.72.41.89]
8 208 ms 191 ms 191 ms 4.69.162.145
9 211 ms 191 ms 191 ms ae-2-52.edge4.Amsterdam1.Level3.net [4.69.139.170]
10 196 ms 191 ms 191 ms Telia-level3-10g.Amsterdam1.level3.net [4.68.62.98]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.MWEB
Code:
$ tracert 213.155.155.233
Tracing route to 213-155-155-233.customer.teliacarrier.com [213.155.155.233]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms keeper.zoo [192.168.0.1]
2 33 ms 7 ms 8 ms 41-132-8-1.dsl.mweb.co.za [41.132.8.1]
3 11 ms 8 ms 11 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 9 ms 18 ms 10 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 200 ms 203 ms 209 ms 176.67.177.131
6 204 ms 199 ms 199 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.133]
7 197 ms 219 ms 228 ms vl-3601-ve-225.csw2.London1.Level3.net [4.69.166.145]
8 222 ms 259 ms 341 ms ae-2-52.edge5.London1.Level3.net [4.69.139.107]
9 600 ms 615 ms 332 ms ldn-b5-link.telia.net [213.248.91.57]
10 196 ms 196 ms 197 ms ldn-bb2-link.telia.net [80.91.249.181]
11 209 ms 204 ms 220 ms adm-bb2-link.telia.net [213.155.134.173]
12 205 ms 204 ms 205 ms adm-b5-link.telia.net [213.155.132.161]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
I've never been cursed in so many different languages!!
.. Thank You Afriman