Do you see any issues on these trace routes?

[ronnie_94]

 

[MickeyD]

Yes. Looks like Mweb have a problem on their network...

 

[ronnie_94]

Mweb insists 100% that they do not see any issues with my trace routes, even though these numbers are 100% higher than what they normally are.

Yes. Looks like Mweb have a problem on their network...

 

[MickeyD]

Mweb insists 100% that they do not see any issues with my trace routes

On the first test, hop 9 is purely on MWeb's network and 118ms for a local link is extremely poor.

On the second test, hops 3,7,8,9,12 are all on MWeb's links and they are all shocking.

It is either their own network or their link provider's network that is at fault.

 

[MickeyD]

Here is a test from my Telkom account:

Tracing route to mweb.co.za [196.2.63.110] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 20 ms 19 ms 19 ms wbs-ip-hsll-2-gi4-0-0-vl102.telkom-ipnet.co.za [105.226.0.21]
4 22 ms 19 ms 19 ms ipc-2-up.south.dsl.telkomsa.net [105.226.0.22]
5 21 ms 20 ms 20 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
6 19 ms 18 ms 20 ms blv-pr-01-be200-vl1.net.telkomsa.net [105.226.0.53]
7 20 ms 29 ms 19 ms ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
8 20 ms 20 ms 22 ms ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
9 20 ms 20 ms 20 ms optinet.ct1.napafrica.net [196.10.140.15]
10 23 ms 23 ms 24 ms te0-0-0-1.cpt-p-2.optinet.net [197.84.7.34]
11 21 ms 20 ms 26 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
12 20 ms 20 ms 20 ms 196.28.178.66
13 20 ms 20 ms 20 ms cte-core-sw2.vwol.net [196.41.144.35]
14 20 ms 21 ms 21 ms www.mweb.co.za [196.2.63.110]

Trace complete.

 

[ronnie_94]

Here is a trace route to telkom.

Tracing route to www.telkomsa.net [196.25.211.40]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms dsldevice.lan [192.168.1.254]
2 * * * Request timed out.
3 38 ms 39 ms 58 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 40 ms 58 ms 36 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 34 ms 26 ms 72 ms 41.162.84.192
6 92 ms 135 ms 96 ms 172.18.1.162
7 29 ms 29 ms 30 ms 41.160.2.69
8 41 ms 29 ms 30 ms rrba-ip-lir-1-gig-0-0-0-102.telkom-ipnet.co.za [196.43.25.137]
9 30 ms 29 ms 30 ms rndf-ip-hsll-2-gig-6-0-0.telkom-ipnet.co.za [196.43.52.162]
10 49 ms 48 ms 67 ms telkom-internet-gw.telkom-ipnet.co.za [165.165.216.222]
11 49 ms 63 ms 52 ms www.telkomsa.net [196.25.211.40]

On the first test, hop 9 is purely on MWeb's network and 118ms for a local link is extremely poor.

On the second test, hops 3,7,8,9,12 are all on MWeb's links and they are all shocking.

It is either their own network or their link provider's network that is at fault.

 

[krustyrsa]

Here is a trace route to telkom.

Tracing route to www.telkomsa.net [196.25.211.40]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms dsldevice.lan [192.168.1.254]
2 * * * Request timed out.
3 38 ms 39 ms 58 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 40 ms 58 ms 36 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 34 ms 26 ms 72 ms 41.162.84.192
6 92 ms 135 ms 96 ms 172.18.1.162
7 29 ms 29 ms 30 ms 41.160.2.69
8 41 ms 29 ms 30 ms rrba-ip-lir-1-gig-0-0-0-102.telkom-ipnet.co.za [196.43.25.137]
9 30 ms 29 ms 30 ms rndf-ip-hsll-2-gig-6-0-0.telkom-ipnet.co.za [196.43.52.162]
10 49 ms 48 ms 67 ms telkom-internet-gw.telkom-ipnet.co.za [165.165.216.222]
11 49 ms 63 ms 52 ms www.telkomsa.net [196.25.211.40]

Those look like Afrihost IP's?

 

[MickeyD]

Mweb insists 100% that they do not see any issues with my trace routes, even though these numbers are 100% higher than what they normally are.

What DNS settings are you using? MWeb or Google's should be ok.

 

[ronnie_94]

Im not sure why?

Those look like Afrihost IP's?

 

[krustyrsa]

Im not sure why?

well who is your ISP?. Because if Afrihost is your ISP, you need to report this issue.

 

[ronnie_94]

I am using google's DNS settings

What DNS settings are you using? MWeb or Google's should be ok.

 

[ronnie_94]

I am with mweb

well who is your ISP?. Because if Afrihost is your ISP, you need to report this issue.

 

[krustyrsa]

View attachment 369323

Here is a trace route to telkom.

Tracing route to www.telkomsa.net [196.25.211.40]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms dsldevice.lan [192.168.1.254]
2 * * * Request timed out.
3 38 ms 39 ms 58 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 40 ms 58 ms 36 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 34 ms 26 ms 72 ms 41.162.84.192
6 92 ms 135 ms 96 ms 172.18.1.162
7 29 ms 29 ms 30 ms 41.160.2.69
8 41 ms 29 ms 30 ms rrba-ip-lir-1-gig-0-0-0-102.telkom-ipnet.co.za [196.43.25.137]
9 30 ms 29 ms 30 ms rndf-ip-hsll-2-gig-6-0-0.telkom-ipnet.co.za [196.43.52.162]
10 49 ms 48 ms 67 ms telkom-internet-gw.telkom-ipnet.co.za [165.165.216.222]
11 49 ms 63 ms 52 ms www.telkomsa.net [196.25.211.40]

I am with mweb

Well these tests indicate both Afrihost and Mweb.

Are you running of WIFI?

 

[ronnie_94]

That is with cable

Well these tests indicate both Afrihost and Mweb.

Are you running of WIFI?

 

[ronnie_94]

what about these ping tests? i get a permanent 5% packet loss while playing cs

C:\Users\ronni>ping mweb.co.za

Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=41ms TTL=118
Reply from 196.2.63.110: bytes=32 time=887ms TTL=118
Reply from 196.2.63.110: bytes=32 time=41ms TTL=118
Reply from 196.2.63.110: bytes=32 time=41ms TTL=118

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

C:\Users\ronni>ping mweb.co.za

Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=42ms TTL=118
Reply from 196.2.63.110: bytes=32 time=41ms TTL=118
Reply from 196.2.63.110: bytes=32 time=41ms TTL=118
Request timed out.

Ping statistics for 196.2.63.110:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 42ms, Average = 41ms

C:\Users\ronni>ping mweb.co.za

Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=668ms TTL=118
Reply from 196.2.63.110: bytes=32 time=41ms TTL=118
Reply from 196.2.63.110: bytes=32 time=40ms TTL=118
Reply from 196.2.63.110: bytes=32 time=41ms TTL=118

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

View attachment 369323

 

[Defib]

Can anyone comment on my PP speeds below?

Tracert to Telkomsa.net

#1
10.0.0.2
Ping: 1.68 ms
#2
105.226.0.21
wbs-ip-hsll-2-gi4-0-0-vl102.telkom-ipnet.co.za
Ping: 901 ms
#3
105.226.0.22
ipc-2-up.south.dsl.telkomsa.net
Ping: 920 ms
#4
105.226.0.57
ipc-aggr-2.south.dsl.telkomsa.net
Ping: 906 ms
#5
165.165.214.213
Ping: 907 ms
#6
196.43.52.162
rndf-ip-hsll-2-gig-6-0-0.telkom-ipnet.co.za
Ping: 945 ms
#7
196.25.166.218
telkom-internet-gw.telkom-ipnet.co.za
Ping: 928 ms
#8
196.25.211.40
www.telkomsa.net
Ping: 910 ms

 

[krustyrsa]

Can anyone comment on my PP speeds below?

Tracert to Telkomsa.net

#1
10.0.0.2
Ping: 1.68 ms
#2
105.226.0.21
wbs-ip-hsll-2-gi4-0-0-vl102.telkom-ipnet.co.za
Ping: 901 ms
#3
105.226.0.22
ipc-2-up.south.dsl.telkomsa.net
Ping: 920 ms
#4
105.226.0.57
ipc-aggr-2.south.dsl.telkomsa.net
Ping: 906 ms
#5
165.165.214.213
Ping: 907 ms
#6
196.43.52.162
rndf-ip-hsll-2-gig-6-0-0.telkom-ipnet.co.za
Ping: 945 ms
#7
196.25.166.218
telkom-internet-gw.telkom-ipnet.co.za
Ping: 928 ms
#8
196.25.211.40
www.telkomsa.net
Ping: 910 ms

looks like exchange congestion. If so there nothing you can do, but keep on reporting it, until telkom upgrades the exchange.

 

[Defib]

Nooooooo don't tell me that. So I'm stuck with this now for months on end.? I used to have awesome speed.... Nooooo

 

[krustyrsa]

Nooooooo don't tell me that. So I'm stuck with this now for months on end.? I used to have awesome speed.... Nooooo

Keep a close Eye on this Notice board, Telkom is constantly rolling out new MSAN's, every week there's something like 10-15 exchange upgrades
https://ssl-1.ipact.telkom-ipnet.co.za/pubcgi/internal/NBView.pl

 

[ronnie_94]

Who do i blame? here are packets to mweb vs telkom, i previously did 200 and in mweb's one i got a lot of 600 to 1000ms on them.

C:\Users\ronni>Ping -n 50 www.telkomsa.net

Pinging www.telkomsa.net [196.25.211.40] with 32 bytes of data:
Reply from 196.25.211.40: bytes=32 time=25ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=27ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=25ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=25ms TTL=119
Reply from 196.25.211.40: bytes=32 time=31ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Request timed out.
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119
Reply from 196.25.211.40: bytes=32 time=25ms TTL=119
Reply from 196.25.211.40: bytes=32 time=24ms TTL=119

Ping statistics for 196.25.211.40:
Packets: Sent = 50, Received = 49, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 31ms, Average = 24ms

C:\Users\ronni>Ping -n 50 www.mweb.co.za

Pinging www.mweb.co.za [196.2.63.110] with 32 bytes of data:
Request timed out.
Reply from 196.2.63.110: bytes=32 time=39ms TTL=118
Reply from 196.2.63.110: bytes=32 time=40ms TTL=118
Reply from 196.2.63.110: bytes=32 time=39ms TTL=118
Reply from 196.2.63.110: bytes=32 time=39ms TTL=118
Reply from 196.2.63.110: bytes=32 time=40ms TTL=118
Reply from 196.2.63.110: bytes=32 time=53ms TTL=118
Request timed out.
Reply from 196.2.63.110: bytes=32 time=39ms TTL=118
Reply from 196.2.63.110: bytes=32 time=40ms TTL=118
Reply from 196.2.63.110: bytes=32 time=40ms TTL=118
Reply from 196.2.63.110: bytes=32 time=40ms TTL=118
Reply from 196.2.63.110: bytes=32 time=40ms TTL=118
Reply from 196.2.63.110: bytes=32 time=40ms TTL=118
Reply from 196.2.63.110: bytes=32 time=99ms TTL=118
Reply from 196.2.63.110: bytes=32 time=40ms TTL=118
Reply from 196.2.63.110: bytes=32 time=39ms TTL=118
Reply from 196.2.63.110: bytes=32 time=39ms TTL=118
Reply from 196.2.63.110: bytes=32 time=40ms TTL=118
Reply from 196.2.63.110: bytes=32 time=40ms TTL=118
Reply from 196.2.63.110: bytes=32 time=40ms TTL=118
Reply from 196.2.63.110: bytes=32 time=40ms TTL=118
Reply from 196.2.63.110: bytes=32 time=40ms TTL=118
Reply from 196.2.63.110: bytes=32 time=40ms TTL=118
Reply from 196.2.63.110: bytes=32 time=860ms TTL=118
Reply from 196.2.63.110: bytes=32 time=39ms TTL=118
Reply from 196.2.63.110: bytes=32 time=40ms TTL=118
Reply from 196.2.63.110: bytes=32 time=45ms TTL=118
Reply from 196.2.63.110: bytes=32 time=89ms TTL=118
Reply from 196.2.63.110: bytes=32 time=39ms TTL=118
Reply from 196.2.63.110: bytes=32 time=39ms TTL=118
Reply from 196.2.63.110: bytes=32 time=39ms TTL=118
Reply from 196.2.63.110: bytes=32 time=40ms TTL=118
Reply from 196.2.63.110: bytes=32 time=40ms TTL=118
Reply from 196.2.63.110: bytes=32 time=39ms TTL=118
Reply from 196.2.63.110: bytes=32 time=749ms TTL=118
Reply from 196.2.63.110: bytes=32 time=40ms TTL=118
Reply from 196.2.63.110: bytes=32 time=39ms TTL=118
Reply from 196.2.63.110: bytes=32 time=40ms TTL=118
Reply from 196.2.63.110: bytes=32 time=39ms TTL=118
Reply from 196.2.63.110: bytes=32 time=40ms TTL=118
Reply from 196.2.63.110: bytes=32 time=39ms TTL=118
Reply from 196.2.63.110: bytes=32 time=39ms TTL=118
Reply from 196.2.63.110: bytes=32 time=40ms TTL=118
Reply from 196.2.63.110: bytes=32 time=48ms TTL=118
Reply from 196.2.63.110: bytes=32 time=39ms TTL=118
Request timed out.
Reply from 196.2.63.110: bytes=32 time=40ms TTL=118
Reply from 196.2.63.110: bytes=32 time=39ms TTL=118
Reply from 196.2.63.110: bytes=32 time=39ms TTL=118

Ping statistics for 196.2.63.110:
Packets: Sent = 50, Received = 47, Lost = 3 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 860ms, Average = 75ms

View attachment 369323