EDO3 Exchange Congestion - High Latency

N

nerf

Well-Known Member
Joined
Jul 5, 2011
Messages
420
Reaction score
0
Me and a few other forum users im in contact with have been getting exchange congestion on EDO3

I've created this thread where we can all put our results together to prove to Telkom that there is a problem

TelkomZA has mentioned to me in PM that we are on a metro Ethernet network and the DSLAM is not congested but we are stilling getting bad pings during peak hours :(

During the day its perfect , ill post another during non peak time when it comes

Here is my tracert done 08 August 2013 @ 19:19

Tracing route to www.google.co.za [74.125.233.88]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 108 ms 141 ms 153 ms 105-236-4-129-esr-lo.mtnbusiness.co.za [105.236.4.129]
3 101 ms 93 ms 126 ms ipc-recieve-rb-1a.za.mtnbusiness.net [41.181.178.53]
4 151 ms 163 ms 110 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 113 ms 122 ms 126 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 135 ms 134 ms 248 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 202 ms 177 ms 200 ms 72.14.194.74
8 110 ms 99 ms 83 ms 64.233.174.57
9 85 ms 93 ms 107 ms jnb01s02-in-f24.1e100.net [74.125.233.88]

Trace complete.
 
Last edited:
Its fine now @21:21

Tracing route to www.google.co.za [74.125.233.88]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 7 ms 8 ms 7 ms 105.236.4.129
3 9 ms 9 ms 9 ms 41.181.178.53
4 12 ms 10 ms 9 ms 196.44.0.146
5 13 ms 9 ms 10 ms 196.44.31.95
6 9 ms 9 ms 9 ms 41.181.165.115
7 10 ms 10 ms 10 ms 72.14.194.74
8 11 ms 11 ms 11 ms 64.233.174.57
9 10 ms 11 ms 12 ms 74.125.233.88

Trace complete.
 
Last night I was also experiencing latency problems on EDO3, it was varying between 50ms to 200ms
I have also found this to be intermittent mostly during peak hours (6pm to 10pm), this was tested with my Telkom 4Meg Uncapped account and also with FNB account but the results are the same.
TelkomZA also mentioned to me that the DSLAM is not congested. But this proves that there is definitely congestion somewhere:wtf:

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 7 ms 6 ms 7 ms . [192.168.2.1]
2 35 ms 35 ms 34 ms ti-224-76-01.telkomadsl.co.za [105.224.76.1]
3 51 ms 49 ms 48 ms ti-224-0-06.telkomadsl.co.za [105.224.0.6]
4 46 ms 47 ms 47 ms ti-224-0-13.telkomadsl.co.za [105.224.0.13]
5 41 ms 38 ms 37 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.37]
6 34 ms 34 ms 32 ms 196.43.39.166
7 53 ms 54 ms 55 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
8 55 ms 59 ms 61 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.34]
9 63 ms 60 ms 61 ms telkom.co.za [196.43.22.222]

Trace complete.

Tracing route to www.saix.net [196.25.1.204]
over a maximum of 30 hops:

1 10 ms 6 ms 15 ms . [192.168.2.1]
2 52 ms 51 ms 50 ms ti-224-76-01.telkomadsl.co.za [105.224.76.1]
3 51 ms 43 ms 40 ms ti-224-0-06.telkomadsl.co.za [105.224.0.6]
4 146 ms 208 ms 210 ms ti-224-0-13.telkomadsl.co.za [105.224.0.13]
5 89 ms 42 ms 49 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.37]
6 69 ms 59 ms 59 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [1
96.43.11.30]
7 wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [196.43.11.30] reports: Dest
ination net unreachable.

Trace complete.
 
I am getting the same its very jumpy

22:29 on 11 august

Tracing route to www.google.co.za [74.125.233.88]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 79 ms 61 ms 97 ms 105-236-4-129-esr-lo.mtnbusiness.co.za [105.236.
4.129]
3 117 ms 75 ms 96 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178
.77]
4 95 ms 80 ms 91 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
5 107 ms 119 ms 96 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 126 ms 107 ms 98 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 47 ms 45 ms 74 ms 72.14.194.74
8 31 ms 45 ms 52 ms 64.233.174.57
9 103 ms 94 ms 85 ms jnb01s02-in-f24.1e100.net [74.125.233.88]
 
I sent a pm to TelkomZA with a link to this forum, perhaps send him one as well as we have the proof that something is not well here
 
Hi guys.

I'm on 012 654 xxxx, as far as I know that is ELDORAIGNE (TEDO03).

All tests from an Afrihost unshaped account but I get similar results from Web Africa and Telkom guest account.
I had it particularly bad last night:

Pinging www-bbc-com.bbc.net.uk [212.58.244.71] with 32 bytes of data:
Reply from 212.58.244.71: bytes=32 time=490ms TTL=48
Reply from 212.58.244.71: bytes=32 time=504ms TTL=48
Reply from 212.58.244.71: bytes=32 time=518ms TTL=48
Reply from 212.58.244.71: bytes=32 time=518ms TTL=48

Pinging www.afrihost.co.za [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=237ms TTL=59
Reply from 197.242.144.102: bytes=32 time=306ms TTL=59
Reply from 197.242.144.102: bytes=32 time=306ms TTL=59
Reply from 197.242.144.102: bytes=32 time=296ms TTL=59

There is no 1ms first hop because I use a manual connect pppoe connection.
Tracing route to www.afrihost.co.za [197.242.144.102]
over a maximum of 30 hops:

1 267 ms 269 ms 293 ms 105-236-4-129-esr-lo.mtnbusiness.co.za [105.236.4.129]
2 329 ms 312 ms 299 ms ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178.89]
3 261 ms 240 ms 241 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
4 272 ms 276 ms 297 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
5 318 ms 286 ms 272 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
6 253 ms 279 ms 276 ms 196.44.31.99
7 316 ms 307 ms 321 ms 196.30.1.39
8 279 ms 279 ms 289 ms tengigabitethernet1-1.gw20.jnb6.za.mtnbusiness.net [196.31.220.23]
9 308 ms 303 ms 277 ms tengigabitethernet5-1.hr15.jnb6.za.mtnbusiness.net [196.31.63.198]
10 300 ms 312 ms 313 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

I hope they dont take 3-4 months (as it did last time) to fix it.
 
Hi Guys

I got the below reply from TelkomZA

Hi Nerf

Had a look @ the forum thread and the trace routes definitely shows that DSLam might be congesting intermittently during the evenings, I have sent a request for confirmation and motivated for bandwidth to be increased, if it is approved it will take about 2 weeks.
Will confirm once motivation has been approved.

Regards Charl
P.S- Unable to confirm ISAM info, not sure where ^GH sourced it, currently no live ISAM in your area
Click to expand...
 
Wow latency is really bad tonight;

Time 6h21pm
Tracing route to www.saix.net [196.25.1.204]
over a maximum of 30 hops:

1 7 ms 6 ms 7 ms . [192.168.2.1]
2 115 ms 114 ms 110 ms ti-224-76-01.telkomadsl.co.za [105.224.76.1]
3 102 ms 97 ms 99 ms ti-224-0-06.telkomadsl.co.za [105.224.0.6]
4 117 ms 117 ms 119 ms ti-224-0-13.telkomadsl.co.za [105.224.0.13]
5 184 ms 101 ms 97 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.37]
6 198 ms 125 ms 121 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [1
96.43.11.30]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [196.43.11.
30] reports: Destination net unreachable.

Trace complete.
 
sakkiemotto said:
Wow latency is really bad tonight;

Time 6h21pm
Tracing route to www.saix.net [196.25.1.204]
over a maximum of 30 hops:

1 7 ms 6 ms 7 ms . [192.168.2.1]
2 115 ms 114 ms 110 ms ti-224-76-01.telkomadsl.co.za [105.224.76.1]
3 102 ms 97 ms 99 ms ti-224-0-06.telkomadsl.co.za [105.224.0.6]
4 117 ms 117 ms 119 ms ti-224-0-13.telkomadsl.co.za [105.224.0.13]
5 184 ms 101 ms 97 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.37]
6 198 ms 125 ms 121 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [1
96.43.11.30]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [196.43.11.
30] reports: Destination net unreachable.

Trace complete.
Click to expand...

Did TelkomZA reply to your PM ?

Same bad latency by me

Tracing route to www.google.co.za [74.125.233.88]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms 192.168.1.254
2 142 ms 103 ms 103 ms 105-236-4-129-esr-lo.mtnbusiness.co.za [105.236.4.129]
3 123 ms 102 ms 100 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178.77]
4 135 ms 98 ms 105 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.120]
5 123 ms 118 ms 83 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 104 ms 98 ms 104 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 125 ms 100 ms 101 ms 72.14.194.74
8 119 ms 57 ms 148 ms 64.233.174.57
9 85 ms 100 ms 102 ms jnb01s02-in-f24.1e100.net [74.125.233.88]
 
Last edited:
nerf said:
Did TelkomZA reply to your PM ?

Same bad latency by me

Tracing route to www.google.co.za [74.125.233.88]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms 192.168.1.254
2 142 ms 103 ms 103 ms 105-236-4-129-esr-lo.mtnbusiness.co.za [105.236.4.129]
3 123 ms 102 ms 100 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178.77]
4 135 ms 98 ms 105 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.120]
5 123 ms 118 ms 83 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 104 ms 98 ms 104 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 125 ms 100 ms 101 ms 72.14.194.74
8 119 ms 57 ms 148 ms 64.233.174.57
9 85 ms 100 ms 102 ms jnb01s02-in-f24.1e100.net [74.125.233.88]
Click to expand...

Yes, I got the same reply from TelkomZA as you did. So i am hoping he can get this sorted for us.
 
I got an update on the problem, many thanks to Charl for finding the problem !!

Morning

Problem has been localized to a intermittently congested port, receiving attention, unfortunately lead time can be up to 2 weeks but have advise on urgency, will follow up with you once work has been completed.

Regards
Charl
Click to expand...
 
tonight seems beter ?

tool trace www.google.co.za
# ADDRESS RT1 RT2 RT3 STATUS
1 105.236.4.129 6ms 7ms 6ms
2 41.181.178.77 10ms 11ms 12ms
3 196.44.31.120 11ms 10ms 9ms <MPLS:L=306492,...
4 196.44.0.42 9ms 9ms 10ms <MPLS:L=304880,...
5 41.181.165.115 11ms 11ms 9ms
6 72.14.194.74 11ms 11ms 12ms
7 64.233.174.57 11ms 11ms 11ms
8 74.125.233.87 13ms 12ms 12ms
 
Tested @ 7h52 very bad:wtf:


Tracing route to google.co.za [74.125.233.87]
over a maximum of 30 hops:

1 7 ms 7 ms 7 ms . [192.168.2.1]
2 99 ms 100 ms 101 ms ti-224-76-01.telkomadsl.co.za [105.224.76.1]
3 110 ms * 115 ms ti-224-0-06.telkomadsl.co.za [105.224.0.6]
4 91 ms 86 ms 81 ms ti-224-0-13.telkomadsl.co.za [105.224.0.13]
5 102 ms 98 ms 96 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.37]
6 105 ms 105 ms 107 ms 196.43.11.202
7 114 ms 109 ms 108 ms 196.43.26.106
8 114 ms 114 ms 108 ms 72.14.212.1
9 108 ms 108 ms 108 ms 64.233.174.57
10 134 ms 131 ms 129 ms jnb01s02-in-f23.1e100.net [74.125.233.87]

Trace complete.
 
Last night was the first time in about 2 weeks where my latency was mostly under control. Not as good as it should be, but I was able to play some fairly successful online games.
 
Telkom ZA sent me a pm with quotes from previous message I didn't really understand what he meant, replied and asked nicely that he please explain but no reply , that actually makes me a bit angry
 
Last night it was back to being useless. Latency was once again 100ms+ more than it should be.
 
Send a pm to TelkomZA, add the link to this forum as reference, lets get the pressure up
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X