I just tried IS teamspeak server which is hosted in jhb and also get 0 loss
Edit - Theory works for TS but not CS in my case. Still 30% loss to JHB servers.
Last edited:
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: Do you think you could pass a driver's licence test without any preparation?
Afrihost CAPPED ADSL Feedback (MTN)
- Thread starter eddief1
- Start date
- Status
I just tried IS teamspeak server which is hosted in jhb and also get 0 loss
Edit - Theory works for TS but not CS in my case. Still 30% loss to JHB servers.
CPT intox server. 10 - 20% loss.
Ping and tracert tests to that server.
Pinging 197.85.190.43 with 32 bytes of data:
Reply from 197.85.190.43: bytes=32 time=21ms TTL=51
Reply from 197.85.190.43: bytes=32 time=20ms TTL=51
Reply from 197.85.190.43: bytes=32 time=17ms TTL=51
Reply from 197.85.190.43: bytes=32 time=19ms TTL=51
Reply from 197.85.190.43: bytes=32 time=18ms TTL=51
Reply from 197.85.190.43: bytes=32 time=19ms TTL=51
Reply from 197.85.190.43: bytes=32 time=18ms TTL=51
Reply from 197.85.190.43: bytes=32 time=18ms TTL=51
Reply from 197.85.190.43: bytes=32 time=18ms TTL=51
Reply from 197.85.190.43: bytes=32 time=18ms TTL=51
Request timed out.
Reply from 197.85.190.43: bytes=32 time=17ms TTL=51
Reply from 197.85.190.43: bytes=32 time=18ms TTL=51
Reply from 197.85.190.43: bytes=32 time=19ms TTL=51
Reply from 197.85.190.43: bytes=32 time=18ms TTL=51
Reply from 197.85.190.43: bytes=32 time=19ms TTL=51
Reply from 197.85.190.43: bytes=32 time=19ms TTL=51
Ping statistics for 197.85.190.43:
Packets: Sent = 17, Received = 16, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 21ms, Average = 18ms
Tracing route to intoxicated.co.za [197.85.190.43]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 8 ms 8 ms 8 ms 105-236-14-193-esr-lo.mtnbusiness.co.za [105.236.14.193]
3 51 ms 22 ms 9 ms 41.181.51.182
4 10 ms 9 ms 9 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 11 ms 11 ms 10 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 10 ms 9 ms 9 ms 196.44.31.106
7 70 ms 9 ms 10 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 17 ms 16 ms 17 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 21 ms * 21 ms tengig-0-7-0-3-cpt-p-2.mweb.co.za [197.84.7.2]
10 19 ms 18 ms 18 ms vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254]
11 18 ms 18 ms 17 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
12 19 ms 18 ms 18 ms 197-85-139-78.cpt.mweb.co.za [197.85.139.78]
13 18 ms 18 ms 18 ms intoxicated.co.za [197.85.190.43]
Hope this helps.
My routes to that server is erratic: I should not get a reply on 2nd hop, but sometimes do?
C:\Windows\system32>tracert -d -w 500 197.85.190.43
Tracing route to 197.85.190.43 over a maximum of 30 hops
1 1 ms <1 ms <1 ms 192.168.10.1
2 * * * Request timed out.
3 * 32 ms 138 ms 41.181.51.181
4 33 ms 34 ms 30 ms 41.181.51.182
5 35 ms 34 ms 36 ms 41.181.198.188
6 35 ms 34 ms 34 ms 196.44.18.8
7 34 ms 34 ms 35 ms 196.44.31.106
8 34 ms 34 ms 37 ms 196.44.0.121
9 * * 58 ms 196.28.178.141
10 46 ms 48 ms 43 ms 197.84.7.2
11 41 ms 43 ms 41 ms 197.84.5.254
12 42 ms 41 ms 42 ms 196.28.178.70
13 45 ms 42 ms 44 ms 197.85.139.78
14 42 ms 42 ms * 197.85.190.43
15 43 ms 43 ms 43 ms 197.85.190.43
Trace complete.
C:\Windows\system32>tracert -d -w 500 197.85.190.43
Tracing route to 197.85.190.43 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.10.1
2 * * * Request timed out.
3 * 142 ms 108 ms 41.181.51.181
4 43 ms 34 ms 35 ms 41.181.51.182
5 35 ms 37 ms 34 ms 41.181.198.188
6 36 ms 34 ms 35 ms 196.44.18.8
7 * * * Request timed out.
8 39 ms 36 ms 101 ms 196.44.0.121
9 41 ms 42 ms 38 ms 196.28.178.141
10 79 ms 36 ms 36 ms 41.181.198.188
11 * 42 ms 41 ms 197.84.5.254
12 * 45 ms 43 ms 196.28.178.70
13 43 ms 41 ms 45 ms 197.85.139.78
14 42 ms 95 ms 39 ms 41.181.51.181
15 42 ms 41 ms 42 ms 197.85.190.43
Trace complete.
C:\Windows\system32>tracert -d -w 500 197.85.190.43
Tracing route to 197.85.190.43 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.10.1
2 * 393 ms 2 ms 41.181.198.188
3 * 26 ms 6 ms 196.44.31.106
4 36 ms 31 ms 14 ms 197.84.7.2
5 34 ms 2 ms * 197.84.5.254
6 36 ms 33 ms 35 ms 196.44.18.8
7 35 ms 34 ms 33 ms 196.44.31.106
8 * 64 ms 34 ms 196.44.0.121
9 43 ms 34 ms 5 ms 196.28.178.141
10 44 ms 26 ms 17 ms 197.84.7.2
11 * 361 ms 16 ms 41.181.51.181
12 42 ms 42 ms * 196.28.178.70
13 33 ms 34 ms * 196.28.178.141
14 39 ms 42 ms 289 ms 41.181.51.181
15 40 ms 44 ms 42 ms 197.85.190.43
Trace complete.
C:\Windows\system32>
C:\Windows\system32>tracert -d -w 500 197.85.190.43
Tracing route to 197.85.190.43 over a maximum of 30 hops
1 1 ms <1 ms <1 ms 192.168.10.1
2 * * * Request timed out.
3 * 32 ms 138 ms 41.181.51.181
4 33 ms 34 ms 30 ms 41.181.51.182
5 35 ms 34 ms 36 ms 41.181.198.188
6 35 ms 34 ms 34 ms 196.44.18.8
7 34 ms 34 ms 35 ms 196.44.31.106
8 34 ms 34 ms 37 ms 196.44.0.121
9 * * 58 ms 196.28.178.141
10 46 ms 48 ms 43 ms 197.84.7.2
11 41 ms 43 ms 41 ms 197.84.5.254
12 42 ms 41 ms 42 ms 196.28.178.70
13 45 ms 42 ms 44 ms 197.85.139.78
14 42 ms 42 ms * 197.85.190.43
15 43 ms 43 ms 43 ms 197.85.190.43
Trace complete.
C:\Windows\system32>tracert -d -w 500 197.85.190.43
Tracing route to 197.85.190.43 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.10.1
2 * * * Request timed out.
3 * 142 ms 108 ms 41.181.51.181
4 43 ms 34 ms 35 ms 41.181.51.182
5 35 ms 37 ms 34 ms 41.181.198.188
6 36 ms 34 ms 35 ms 196.44.18.8
7 * * * Request timed out.
8 39 ms 36 ms 101 ms 196.44.0.121
9 41 ms 42 ms 38 ms 196.28.178.141
10 79 ms 36 ms 36 ms 41.181.198.188
11 * 42 ms 41 ms 197.84.5.254
12 * 45 ms 43 ms 196.28.178.70
13 43 ms 41 ms 45 ms 197.85.139.78
14 42 ms 95 ms 39 ms 41.181.51.181
15 42 ms 41 ms 42 ms 197.85.190.43
Trace complete.
C:\Windows\system32>tracert -d -w 500 197.85.190.43
Tracing route to 197.85.190.43 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.10.1
2 * 393 ms 2 ms 41.181.198.188
3 * 26 ms 6 ms 196.44.31.106
4 36 ms 31 ms 14 ms 197.84.7.2
5 34 ms 2 ms * 197.84.5.254
6 36 ms 33 ms 35 ms 196.44.18.8
7 35 ms 34 ms 33 ms 196.44.31.106
8 * 64 ms 34 ms 196.44.0.121
9 43 ms 34 ms 5 ms 196.28.178.141
10 44 ms 26 ms 17 ms 197.84.7.2
11 * 361 ms 16 ms 41.181.51.181
12 42 ms 42 ms * 196.28.178.70
13 33 ms 34 ms * 196.28.178.141
14 39 ms 42 ms 289 ms 41.181.51.181
15 40 ms 44 ms 42 ms 197.85.190.43
Trace complete.
C:\Windows\system32>
Last edited:
So i see i also have 30% odd packet loss again.
So i ran a pathping and here are the results. Issue seems to be at the router by 105.236.240.129.
C:\Users\L3vi>pathping -n www.afrihost.co.za
Tracing route to www.afrihost.co.za [197.242.144.102]
over a maximum of 30 hops:
0 192.168.0.3
1 192.168.0.1
2 105.236.240.129
3 41.181.53.214
4 41.181.198.188
5 196.44.18.8
6 196.44.31.66
7 196.44.31.255
8 196.44.31.99
9 196.31.220.6
10 196.31.220.23
11 196.31.63.206
12 196.30.42.133
13 197.242.144.102
Computing statistics for 325 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 192.168.0.3
18/ 100 = 18% |
1 0ms 18/ 100 = 18% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 22ms 51/ 100 = 51% 33/ 100 = 33% 105.236.240.129
0/ 100 = 0% |
3 29ms 19/ 100 = 19% 1/ 100 = 1% 41.181.53.214
0/ 100 = 0% |
4 34ms 18/ 100 = 18% 0/ 100 = 0% 41.181.198.188
0/ 100 = 0% |
5 26ms 18/ 100 = 18% 0/ 100 = 0% 196.44.18.8
0/ 100 = 0% |
6 49ms 19/ 100 = 19% 1/ 100 = 1% 196.44.31.66
0/ 100 = 0% |
7 53ms 19/ 100 = 19% 1/ 100 = 1% 196.44.31.255
0/ 100 = 0% |
8 52ms 18/ 100 = 18% 0/ 100 = 0% 196.44.31.99
0/ 100 = 0% |
9 56ms 19/ 100 = 19% 1/ 100 = 1% 196.31.220.6
0/ 100 = 0% |
10 51ms 19/ 100 = 19% 1/ 100 = 1% 196.31.220.23
0/ 100 = 0% |
11 53ms 18/ 100 = 18% 0/ 100 = 0% 196.31.63.206
0/ 100 = 0% |
12 49ms 21/ 100 = 21% 3/ 100 = 3% 196.30.42.133
0/ 100 = 0% |
13 48ms 18/ 100 = 18% 0/ 100 = 0% 197.242.144.102
Trace complete.
C:\Users\L3vi>
Hope this helps.
So i ran a pathping and here are the results. Issue seems to be at the router by 105.236.240.129.
C:\Users\L3vi>pathping -n www.afrihost.co.za
Tracing route to www.afrihost.co.za [197.242.144.102]
over a maximum of 30 hops:
0 192.168.0.3
1 192.168.0.1
2 105.236.240.129
3 41.181.53.214
4 41.181.198.188
5 196.44.18.8
6 196.44.31.66
7 196.44.31.255
8 196.44.31.99
9 196.31.220.6
10 196.31.220.23
11 196.31.63.206
12 196.30.42.133
13 197.242.144.102
Computing statistics for 325 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 192.168.0.3
18/ 100 = 18% |
1 0ms 18/ 100 = 18% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 22ms 51/ 100 = 51% 33/ 100 = 33% 105.236.240.129
0/ 100 = 0% |
3 29ms 19/ 100 = 19% 1/ 100 = 1% 41.181.53.214
0/ 100 = 0% |
4 34ms 18/ 100 = 18% 0/ 100 = 0% 41.181.198.188
0/ 100 = 0% |
5 26ms 18/ 100 = 18% 0/ 100 = 0% 196.44.18.8
0/ 100 = 0% |
6 49ms 19/ 100 = 19% 1/ 100 = 1% 196.44.31.66
0/ 100 = 0% |
7 53ms 19/ 100 = 19% 1/ 100 = 1% 196.44.31.255
0/ 100 = 0% |
8 52ms 18/ 100 = 18% 0/ 100 = 0% 196.44.31.99
0/ 100 = 0% |
9 56ms 19/ 100 = 19% 1/ 100 = 1% 196.31.220.6
0/ 100 = 0% |
10 51ms 19/ 100 = 19% 1/ 100 = 1% 196.31.220.23
0/ 100 = 0% |
11 53ms 18/ 100 = 18% 0/ 100 = 0% 196.31.63.206
0/ 100 = 0% |
12 49ms 21/ 100 = 21% 3/ 100 = 3% 196.30.42.133
0/ 100 = 0% |
13 48ms 18/ 100 = 18% 0/ 100 = 0% 197.242.144.102
Trace complete.
C:\Users\L3vi>
Hope this helps.
I've noticed all my loss is occuring on the mweb network. I've run multiple tracerts to that intox server and the loss occurs on the mweb network. The matchmaking servers (all of them) are servers hosted by mweb where I also get loss.
When I switch to my telkom account I get the same ping to my rented mumble server (hosted in CPT) that I get to the wage (hosted in JHB) one. You guessed it, the latency is introduced at mweb's network. Where ping goes from 10 to 35.
Something is jacked up with mweb.
Tracert results:
Tracing route to intoxicated.co.za [197.85.190.43]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 8 ms 8 ms 8 ms 105-236-14-193-esr-lo.mtnbusiness.co.za [105.236.14.193]
3 35 ms 9 ms 9 ms 41.181.51.182
4 13 ms 12 ms 14 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 10 ms 9 ms 10 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 9 ms 10 ms 10 ms 196.44.31.106
7 10 ms 10 ms 9 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 17 ms 16 ms 17 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 22 ms 20 ms 21 ms tengig-0-7-0-3-cpt-p-2.mweb.co.za [197.84.7.2]
10 18 ms 18 ms 18 ms vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254]
11 19 ms 17 ms * vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
12 19 ms 17 ms 17 ms 197-85-139-78.cpt.mweb.co.za [197.85.139.78]
13 26 ms 26 ms 26 ms intoxicated.co.za [197.85.190.43]
Trace complete.
Tracing route to intoxicated.co.za [197.85.190.43]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 8 ms 8 ms 8 ms 105-236-14-193-esr-lo.mtnbusiness.co.za [105.236.14.193]
3 9 ms 9 ms 9 ms 41.181.51.182
4 10 ms 11 ms 9 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 10 ms 10 ms 10 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 9 ms 10 ms 9 ms 196.44.31.106
7 10 ms 10 ms 10 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 18 ms 17 ms 17 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 22 ms 20 ms 18 ms tengig-0-7-0-3-cpt-p-2.mweb.co.za [197.84.7.2]
10 18 ms 18 ms 18 ms vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254]
11 19 ms 20 ms 18 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
12 18 ms * 18 ms 197-85-139-78.cpt.mweb.co.za [197.85.139.78]
13 18 ms 18 ms 20 ms intoxicated.co.za [197.85.190.43]
Trace complete.
Tracing route to intoxicated.co.za [197.85.190.43]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 8 ms 8 ms 8 ms 105-236-14-193-esr-lo.mtnbusiness.co.za [105.236.14.193]
3 26 ms 9 ms 9 ms 41.181.51.182
4 13 ms 13 ms 12 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 14 ms 13 ms 12 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 10 ms 10 ms 10 ms 196.44.31.106
7 10 ms 9 ms 10 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 17 ms 16 ms 16 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 20 ms * 18 ms tengig-0-7-0-3-cpt-p-2.mweb.co.za [197.84.7.2]
10 17 ms 18 ms 18 ms vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254]
11 * 19 ms 18 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
12 18 ms 17 ms 18 ms 197-85-139-78.cpt.mweb.co.za [197.85.139.78]
13 19 ms 19 ms 19 ms intoxicated.co.za [197.85.190.43]
Trace complete.
Tracing route to intoxicated.co.za [197.85.190.43]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 8 ms 8 ms 8 ms 105-236-14-193-esr-lo.mtnbusiness.co.za [105.236.14.193]
3 9 ms 9 ms 121 ms 41.181.51.182
4 11 ms 11 ms 11 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 14 ms 15 ms 16 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 48 ms 10 ms 10 ms 196.44.31.106
7 10 ms 9 ms 10 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 17 ms 16 ms 17 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 24 ms 21 ms 20 ms tengig-0-7-0-3-cpt-p-2.mweb.co.za [197.84.7.2]
10 18 ms 18 ms 17 ms vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254]
11 18 ms 18 ms 18 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
12 18 ms 17 ms 18 ms 197-85-139-78.cpt.mweb.co.za [197.85.139.78]
13 19 ms 18 ms 18 ms intoxicated.co.za [197.85.190.43]
Trace complete.
Tracing route to intoxicated.co.za [197.85.190.43]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 8 ms 8 ms 8 ms 105-236-14-193-esr-lo.mtnbusiness.co.za [105.236.14.193]
3 51 ms 22 ms 9 ms 41.181.51.182
4 10 ms 9 ms 9 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 11 ms 11 ms 10 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 10 ms 9 ms 9 ms 196.44.31.106
7 70 ms 9 ms 10 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 17 ms 16 ms 17 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 21 ms * 21 ms tengig-0-7-0-3-cpt-p-2.mweb.co.za [197.84.7.2]
10 19 ms 18 ms 18 ms vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254]
11 18 ms 18 ms 17 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
12 19 ms 18 ms 18 ms 197-85-139-78.cpt.mweb.co.za [197.85.139.78]
13 18 ms 18 ms 18 ms intoxicated.co.za [197.85.190.43]
*EDIT if you want the tracert to my mumble server pm me please. Don't want to hand it out
When I switch to my telkom account I get the same ping to my rented mumble server (hosted in CPT) that I get to the wage (hosted in JHB) one. You guessed it, the latency is introduced at mweb's network. Where ping goes from 10 to 35.
Something is jacked up with mweb.
Tracert results:
Tracing route to intoxicated.co.za [197.85.190.43]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 8 ms 8 ms 8 ms 105-236-14-193-esr-lo.mtnbusiness.co.za [105.236.14.193]
3 35 ms 9 ms 9 ms 41.181.51.182
4 13 ms 12 ms 14 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 10 ms 9 ms 10 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 9 ms 10 ms 10 ms 196.44.31.106
7 10 ms 10 ms 9 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 17 ms 16 ms 17 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 22 ms 20 ms 21 ms tengig-0-7-0-3-cpt-p-2.mweb.co.za [197.84.7.2]
10 18 ms 18 ms 18 ms vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254]
11 19 ms 17 ms * vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
12 19 ms 17 ms 17 ms 197-85-139-78.cpt.mweb.co.za [197.85.139.78]
13 26 ms 26 ms 26 ms intoxicated.co.za [197.85.190.43]
Trace complete.
Tracing route to intoxicated.co.za [197.85.190.43]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 8 ms 8 ms 8 ms 105-236-14-193-esr-lo.mtnbusiness.co.za [105.236.14.193]
3 9 ms 9 ms 9 ms 41.181.51.182
4 10 ms 11 ms 9 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 10 ms 10 ms 10 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 9 ms 10 ms 9 ms 196.44.31.106
7 10 ms 10 ms 10 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 18 ms 17 ms 17 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 22 ms 20 ms 18 ms tengig-0-7-0-3-cpt-p-2.mweb.co.za [197.84.7.2]
10 18 ms 18 ms 18 ms vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254]
11 19 ms 20 ms 18 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
12 18 ms * 18 ms 197-85-139-78.cpt.mweb.co.za [197.85.139.78]
13 18 ms 18 ms 20 ms intoxicated.co.za [197.85.190.43]
Trace complete.
Tracing route to intoxicated.co.za [197.85.190.43]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 8 ms 8 ms 8 ms 105-236-14-193-esr-lo.mtnbusiness.co.za [105.236.14.193]
3 26 ms 9 ms 9 ms 41.181.51.182
4 13 ms 13 ms 12 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 14 ms 13 ms 12 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 10 ms 10 ms 10 ms 196.44.31.106
7 10 ms 9 ms 10 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 17 ms 16 ms 16 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 20 ms * 18 ms tengig-0-7-0-3-cpt-p-2.mweb.co.za [197.84.7.2]
10 17 ms 18 ms 18 ms vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254]
11 * 19 ms 18 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
12 18 ms 17 ms 18 ms 197-85-139-78.cpt.mweb.co.za [197.85.139.78]
13 19 ms 19 ms 19 ms intoxicated.co.za [197.85.190.43]
Trace complete.
Tracing route to intoxicated.co.za [197.85.190.43]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 8 ms 8 ms 8 ms 105-236-14-193-esr-lo.mtnbusiness.co.za [105.236.14.193]
3 9 ms 9 ms 121 ms 41.181.51.182
4 11 ms 11 ms 11 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 14 ms 15 ms 16 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 48 ms 10 ms 10 ms 196.44.31.106
7 10 ms 9 ms 10 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 17 ms 16 ms 17 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 24 ms 21 ms 20 ms tengig-0-7-0-3-cpt-p-2.mweb.co.za [197.84.7.2]
10 18 ms 18 ms 17 ms vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254]
11 18 ms 18 ms 18 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
12 18 ms 17 ms 18 ms 197-85-139-78.cpt.mweb.co.za [197.85.139.78]
13 19 ms 18 ms 18 ms intoxicated.co.za [197.85.190.43]
Trace complete.
Tracing route to intoxicated.co.za [197.85.190.43]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 8 ms 8 ms 8 ms 105-236-14-193-esr-lo.mtnbusiness.co.za [105.236.14.193]
3 51 ms 22 ms 9 ms 41.181.51.182
4 10 ms 9 ms 9 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 11 ms 11 ms 10 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 10 ms 9 ms 9 ms 196.44.31.106
7 70 ms 9 ms 10 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 17 ms 16 ms 17 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 21 ms * 21 ms tengig-0-7-0-3-cpt-p-2.mweb.co.za [197.84.7.2]
10 19 ms 18 ms 18 ms vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254]
11 18 ms 18 ms 17 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
12 19 ms 18 ms 18 ms 197-85-139-78.cpt.mweb.co.za [197.85.139.78]
13 18 ms 18 ms 18 ms intoxicated.co.za [197.85.190.43]
*EDIT if you want the tracert to my mumble server pm me please. Don't want to hand it out
Last edited:
medicnick83
Paramedic
I'm also having issues this morning and I just turned my router on (been off for 2 days) and Steam is downloading some updates and it's coming in at 1.5KB/s.
Blizzard can't update, neither can Mech Warrior Online.
Torrents are dead at 2KB/s downloads.
I need to a do Windows updates and they are failing.
Blizzard can't update, neither can Mech Warrior Online.
Torrents are dead at 2KB/s downloads.
I need to a do Windows updates and they are failing.
Yeah i am STILL have slow NZBs. Will be testing out Crystal Web's offerings tonight. Reviews are looking positive for the ISP. If all goes to plan I'll probably just switch because this is annoying.
- Joined
- Oct 9, 2014
- Messages
- 7,265
- Reaction score
- 6
That's definitely not right. What sort of speeds are you getting on speedtest.net?
Could you send me a PM with your account details so that I can look into this from my side. -E
- Joined
- Oct 9, 2014
- Messages
- 7,265
- Reaction score
- 6
Thanks to everyone for posting the traceroutes last night to your gaming servers! Really appreciated.
We're checking if the peering link with Mweb could possibly be the cause of the packet loss and latency spikes, that definitely could be causing the various head-aches.
We're checking if the peering link with Mweb could possibly be the cause of the packet loss and latency spikes, that definitely could be causing the various head-aches.
nevadayz
Expert Member
Hi guys,
ive been trying out the 2mb capped accounts, and have been getting some terrible speeds with torrents, popcorn time specifically, any feedback/advice?
Normally get speeds of about 200-220kb/s peak, but with the torrents its can drop below 100kb/s.
Works perfectly with my other isp accounts.
ive been trying out the 2mb capped accounts, and have been getting some terrible speeds with torrents, popcorn time specifically, any feedback/advice?
Normally get speeds of about 200-220kb/s peak, but with the torrents its can drop below 100kb/s.
Works perfectly with my other isp accounts.
- Joined
- Oct 9, 2014
- Messages
- 7,265
- Reaction score
- 6
Morning!
That's very strange, did you notice any other drops in speed or increases in latency with your Afrihost connection?
Would you mind sending me a PM with the account details so that I can look into this for you.
With my traceroutes I noted that the two servers: 197.84.7.2 and 196.28.178.70 popped up with loss.
These aren't however near the edge of the MWEB network so I'm not sure if it's peering related. I don't know how ISP's communicate so are you going to make MWEB aware of these servers or should I try and get in contact with someone? Or are one set of traceroute results not conclusive enough to warrant this?
I can't even stream a file from Google Drive this afternoon and 3pm on a Thursday afternoon is hardly peak time, especially for a server farm as large as Google Drive.
Pretty damn annoying as I store all of my business files, reference works, drawings, videos etc (Not Client Data or Financials) on Google drive.
Any known issues in Cape Town?
Pretty damn annoying as I store all of my business files, reference works, drawings, videos etc (Not Client Data or Financials) on Google drive.
Any known issues in Cape Town?
As has latency:
Tracing route to docs.google.com [216.58.208.238]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms www.routerlogin.com [192.168.0.200]
2 * * * Request timed out.
3 149 ms 128 ms 125 ms 41.181.53.213
4 78 ms 82 ms 82 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
5 72 ms 76 ms 74 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
6 38 ms 33 ms 29 ms compj-cpt-1.mtnns.net [196.44.18.2]
7 158 ms 156 ms 160 ms ls-cr-2--tb-cr-1.uk-b.mtnns.net [196.44.31.113]
8 164 ms 168 ms 164 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net [209.212.111.187]
9 182 ms 157 ms 157 ms google-peering-ls-pr-2.uk.mtnns.net [209.212.99.13]
10 164 ms 165 ms 156 ms 209.85.255.78
11 154 ms 155 ms 153 ms 209.85.245.2
12 170 ms 168 ms 202 ms 209.85.242.79
13 214 ms 207 ms 212 ms 209.85.245.80
14 163 ms 161 ms 165 ms 209.85.143.243
15 162 ms 161 ms 160 ms par10s22-in-f14.1e100.net [216.58.208.238]
Trace complete.
Tracing route to docs.google.com [216.58.208.238]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms www.routerlogin.com [192.168.0.200]
2 * * * Request timed out.
3 149 ms 128 ms 125 ms 41.181.53.213
4 78 ms 82 ms 82 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
5 72 ms 76 ms 74 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
6 38 ms 33 ms 29 ms compj-cpt-1.mtnns.net [196.44.18.2]
7 158 ms 156 ms 160 ms ls-cr-2--tb-cr-1.uk-b.mtnns.net [196.44.31.113]
8 164 ms 168 ms 164 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net [209.212.111.187]
9 182 ms 157 ms 157 ms google-peering-ls-pr-2.uk.mtnns.net [209.212.99.13]
10 164 ms 165 ms 156 ms 209.85.255.78
11 154 ms 155 ms 153 ms 209.85.245.2
12 170 ms 168 ms 202 ms 209.85.242.79
13 214 ms 207 ms 212 ms 209.85.245.80
14 163 ms 161 ms 165 ms 209.85.143.243
15 162 ms 161 ms 160 ms par10s22-in-f14.1e100.net [216.58.208.238]
Trace complete.
Afrigenie are you guys making any progress on this? 
*EDIT Getting "UDP packets cannot be sent to or received from the server. Switching to TCP mode." from my mumble server. Having udp issues might also explain why getting loss in games but not so much in ping and tracert. Anyone know how to ping using UDP?
*EDIT Getting "UDP packets cannot be sent to or received from the server. Switching to TCP mode." from my mumble server. Having udp issues might also explain why getting loss in games but not so much in ping and tracert. Anyone know how to ping using UDP?
Last edited:
Afrigenie are you guys making any progress on this?
*EDIT Getting "UDP packets cannot be sent to or received from the server. Switching to TCP mode." from my mumble server. Having udp issues might also explain why getting loss in games but not so much in ping and tracert. Anyone know how to ping using UDP?
Things should mostly be resolved, we're looking much better than what we did this time yesterday
Please test a bit later tonight and let me know if you're still having any issues.
Things should mostly be resolved, we're looking much better than what we did this time yesterday
Please test a bit later tonight and let me know if you're still having any issues.
Nothing has changed at all. Got 10% packet loss on TS as we speak....
+1
Got 8% on mumble. CPT hosted.
*EDIT Still got loss in game.
The ping is because it's a GOTV relay. I'm trying to watch ESL One Katowice.
Last edited:
- Status