OpenWeb ADSL Feedback Thread

Status
Not open for further replies.
NAG - Wesley said:
This is new? Everyone's main issue is Telkom.
Click to expand...

The Telkom thread is full of angry users for weeks now. Lots of cancellations. Might be like the mweb exodus around here soon. Beepie I hope we have enough capacity. The last time this happened it got rough here.
 
TelkomZA confirms that my exchange is NOT CONGESTED. It's 30% utilised. So why am I getting ****ty speeds? :mad: IS? My ISP is Openweb, not TI.
 
DarkSpectre said:
TelkomZA confirms that my exchange is NOT CONGESTED. It's 30% utilised. So why am I getting ****ty speeds? :mad: IS? My ISP is Openweb, not TI.
Click to expand...

OW use different backbones.

Are you sure you on IS?

Do a tracert, 2nd hop will show who you on.
 
Although, I am noticing some issues with international on IS, like now it just drops for a minute or so then carries on as per normal, like last night but not as bad.

There seems to be stuff happening in general.
 
wingnut771 said:
OW use different backbones.

Are you sure you on IS?

Do a tracert, 2nd hop will show who you on.
Click to expand...

Yep, I'm on IS. I suspect that I'm being throttled lightly because I've downloaded too much (1.37gb) this month.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\88888>tracert www.mybroadband.co.za

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

1 1 ms <1 ms <1 ms dsldevice.lan [192.168.10.1]
2 18 ms 15 ms 16 ms 196-210-155-129.dynamic.isadsl.co.za [196.210.15
5.129]
3 45 ms 44 ms 54 ms vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
4 45 ms 56 ms 48 ms 196.35.115.136
5 46 ms 45 ms 44 ms 168.209.6.12
6 47 ms 45 ms 46 ms css1-ctn-gi0-2.ip.isnet.net [168.209.6.10]
7 47 ms 52 ms 44 ms 196.36.84.154
8 67 ms 69 ms 74 ms CORE.GP-CN-HET-MEE-1.TO.GP-MR-VOD-MEE-1.DFA.P2P.
10G.za.africainx.net [41.84.12.151]
9 78 ms 71 ms 69 ms 41-66-132-242-f2.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.242]
10 73 ms 69 ms 67 ms core-access-switch1.jnb1.host-h.net [197.189.193
.1]
11 70 ms 73 ms 81 ms row-access-switch1-row7-8.jnb1.host-h.net [197.1
89.193.39]
12 71 ms 75 ms 68 ms 41.203.24.42
13 83 ms 72 ms 89 ms 197.242.89.170

Trace complete.

C:\Users\888888>
Click to expand...
 
DarkSpectre said:
Yep, I'm on IS. I suspect that I'm being throttled lightly because I've downloaded too much (1.37gb) this month.
Click to expand...

I don't know hey, IS is unshaped on the weekends, it's only usually monday morning when you get punished.

EDIT: LOL - missed the sarcasm
 
Last edited:
What the hell? :eek: A few minutes ago, I was using another uncapped account from a certain myBB mate and it was running so smoothly. It's on IS too but it was running SOOOOO smoothly. Now I've switched back to my OW account and I'm shocked to find out that it's too running so smooth! :eek:
 
Full speed ahead here.

Screenshot%202014-01-25%2010.55.16.png


:D
 
DarkSpectre said:
What the hell? :eek: A few minutes ago, I was using another uncapped account from a certain myBB mate and it was running so smoothly. It's on IS too but it was running SOOOOO smoothly. Now I've switched back to my OW account and I'm shocked to find out that it's too running so smooth! :eek:
Click to expand...

Try each one for an extended period - if they both degrade - then you have line issues or something - same goes with AH account - apparently when you log in - it creates a new port (like leaving your router off for a while), and normally "hides" the issue initially, then starts it's downward trend into....
 
DrJohnZoidberg said:
Full speed ahead here.

Screenshot%202014-01-25%2010.55.16.png


:D
Click to expand...

wingnut771 said:
Try each one for an extended period - if they both degrade - then you have line issues or something - same goes with AH account - apparently when you log in - it creates a new port (like leaving your router off for a while), and normally "hides" the issue initially, then starts it's downward trend into....
Click to expand...

Ok, will do that this evening when our home network gets quiet.
 
Imagine101011 said:
Can someone tell me what the problem is, I am wanting to play Star Trek Online, have been playing for years with no issues, and now it just times out all the time, here is my trace router, from what I can see, local seems ok, but a soon as it goes international it sucks:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>tracert startrekonline.com

Tracing route to startrekonline.com [208.95.185.44]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 20 ms 91 ms 21 ms 196-210-140-1.dynamic.isadsl.co.za [196.210.140.
1]
3 23 ms 53 ms 23 ms cdsl1-rba-vl2153.ip.isnet.net [196.38.73.169]
4 26 ms 25 ms 23 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
5 36 ms 28 ms 27 ms core1-pkl-tg0-7-0-0.ip.isnet.net [168.209.1.162]

6 203 ms 201 ms 205 ms core1b-dock-tenge-0-4-0-0-127.ip.isnet.net [168.
209.201.77]
7 210 ms 193 ms 222 ms ge-2-1-0.mpr1.lhr2.uk.above.net [195.66.224.76]

8 203 ms 200 ms 218 ms xe-8-1-1.mpr2.lhr3.uk.above.net [64.125.31.198]

9 457 ms 198 ms 224 ms xe-1-1-1.mpr1.lhr3.uk.above.net [64.125.24.217]

10 285 ms 278 ms 272 ms ae3.cr1.lga5.us.above.net [64.125.21.205]
11 273 ms 274 ms 389 ms xe-1-1-0.mpr3.bos2.us.above.net [64.125.25.41]
12 425 ms 383 ms 412 ms 208.184.110.70.IPYX-072053-002-ZYO.above.net [20
8.184.110.70]
13 271 ms 274 ms 270 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
14 290 ms 392 ms 304 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
15 475 ms 268 ms 278 ms 208.95.185.44

Trace complete.
Click to expand...

Anybody?
 
Imagine101011 said:
Anybody?
Click to expand...

That local ping looks bad.

Do a tracert, make a note of the IP of the 2nd hop, then do a

ping -n 100 ip address (with an idle line)

which will ping 100 times, see if it bounces around. If it does, then you have telkom issues, best bet is to PM TelkomZA and explain your issues and what you've done. He might ask you to do other tests to gather evidence for motivation.

If you are having telkom issues, it might be an idea to check with the neighbours to see if they having issues too, if so, and you all log a fault, your chances should improve in waking up the dinosaur into pulling finger :)

Hope this helps.
 
wingnut771 said:
That local ping looks bad.

Do a tracert, make a note of the IP of the 2nd hop, then do a

ping -n 100 ip address (with an idle line)

which will ping 100 times, see if it bounces around. If it does, then you have telkom issues, best bet is to PM TelkomZA and explain your issues and what you've done. He might ask you to do other tests to gather evidence for motivation.

If you are having telkom issues, it might be an idea to check with the neighbours to see if they having issues too, if so, and you all log a fault, your chances should improve in waking up the dinosaur into pulling finger :)

Hope this helps.
Click to expand...

Thanks Wingnut :)

here is what I got:

C:\Windows\system32>ping -n 100 196.210.140.1

Pinging 196.210.140.1 with 32 bytes of data:
Reply from 196.210.140.1: bytes=32 time=25ms TTL=254
Request timed out.
Reply from 196.210.140.1: bytes=32 time=25ms TTL=254
Reply from 196.210.140.1: bytes=32 time=24ms TTL=254
Reply from 196.210.140.1: bytes=32 time=24ms TTL=254
Reply from 196.210.140.1: bytes=32 time=22ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=22ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=27ms TTL=254
Reply from 196.210.140.1: bytes=32 time=24ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=24ms TTL=254
Reply from 196.210.140.1: bytes=32 time=22ms TTL=254
Reply from 196.210.140.1: bytes=32 time=22ms TTL=254
Reply from 196.210.140.1: bytes=32 time=28ms TTL=254
Request timed out.
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=43ms TTL=254
Reply from 196.210.140.1: bytes=32 time=25ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=24ms TTL=254
Reply from 196.210.140.1: bytes=32 time=30ms TTL=254
Reply from 196.210.140.1: bytes=32 time=35ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Request timed out.
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=26ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=30ms TTL=254
Reply from 196.210.140.1: bytes=32 time=45ms TTL=254
Reply from 196.210.140.1: bytes=32 time=38ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Request timed out.
Reply from 196.210.140.1: bytes=32 time=22ms TTL=254
Request timed out.
Reply from 196.210.140.1: bytes=32 time=28ms TTL=254
Reply from 196.210.140.1: bytes=32 time=22ms TTL=254
Reply from 196.210.140.1: bytes=32 time=25ms TTL=254
Reply from 196.210.140.1: bytes=32 time=26ms TTL=254
Reply from 196.210.140.1: bytes=32 time=28ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=34ms TTL=254
Reply from 196.210.140.1: bytes=32 time=22ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=26ms TTL=254
Reply from 196.210.140.1: bytes=32 time=25ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=36ms TTL=254
Reply from 196.210.140.1: bytes=32 time=35ms TTL=254
Request timed out.
Reply from 196.210.140.1: bytes=32 time=38ms TTL=254
Reply from 196.210.140.1: bytes=32 time=27ms TTL=254
Reply from 196.210.140.1: bytes=32 time=27ms TTL=254
Reply from 196.210.140.1: bytes=32 time=25ms TTL=254
Request timed out.
Reply from 196.210.140.1: bytes=32 time=36ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=24ms TTL=254
Reply from 196.210.140.1: bytes=32 time=22ms TTL=254
Reply from 196.210.140.1: bytes=32 time=22ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=39ms TTL=254
Reply from 196.210.140.1: bytes=32 time=29ms TTL=254
Reply from 196.210.140.1: bytes=32 time=24ms TTL=254
Reply from 196.210.140.1: bytes=32 time=25ms TTL=254
Request timed out.
Reply from 196.210.140.1: bytes=32 time=22ms TTL=254
Reply from 196.210.140.1: bytes=32 time=24ms TTL=254
Reply from 196.210.140.1: bytes=32 time=25ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=31ms TTL=254
Reply from 196.210.140.1: bytes=32 time=25ms TTL=254
Reply from 196.210.140.1: bytes=32 time=24ms TTL=254
Reply from 196.210.140.1: bytes=32 time=49ms TTL=254
Reply from 196.210.140.1: bytes=32 time=24ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=28ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=24ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=24ms TTL=254
Reply from 196.210.140.1: bytes=32 time=32ms TTL=254
Reply from 196.210.140.1: bytes=32 time=28ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Request timed out.
Reply from 196.210.140.1: bytes=32 time=39ms TTL=254
Reply from 196.210.140.1: bytes=32 time=27ms TTL=254
Reply from 196.210.140.1: bytes=32 time=27ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=29ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=43ms TTL=254

Ping statistics for 196.210.140.1:
Packets: Sent = 100, Received = 91, Lost = 9 (9% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 49ms, Average = 26ms

what does it mean? Telkom issues?
 
Imagine101011 said:
Thanks Wingnut :)

here is what I got:

C:\Windows\system32>ping -n 100 196.210.140.1

Pinging 196.210.140.1 with 32 bytes of data:
Reply from 196.210.140.1: bytes=32 time=25ms TTL=254
Request timed out.
Reply from 196.210.140.1: bytes=32 time=25ms TTL=254
Reply from 196.210.140.1: bytes=32 time=24ms TTL=254
Reply from 196.210.140.1: bytes=32 time=24ms TTL=254
Reply from 196.210.140.1: bytes=32 time=22ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=22ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=27ms TTL=254
Reply from 196.210.140.1: bytes=32 time=24ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=24ms TTL=254
Reply from 196.210.140.1: bytes=32 time=22ms TTL=254
Reply from 196.210.140.1: bytes=32 time=22ms TTL=254
Reply from 196.210.140.1: bytes=32 time=28ms TTL=254
Request timed out.
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=43ms TTL=254
Reply from 196.210.140.1: bytes=32 time=25ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=24ms TTL=254
Reply from 196.210.140.1: bytes=32 time=30ms TTL=254
Reply from 196.210.140.1: bytes=32 time=35ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Request timed out.
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=26ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=30ms TTL=254
Reply from 196.210.140.1: bytes=32 time=45ms TTL=254
Reply from 196.210.140.1: bytes=32 time=38ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Request timed out.
Reply from 196.210.140.1: bytes=32 time=22ms TTL=254
Request timed out.
Reply from 196.210.140.1: bytes=32 time=28ms TTL=254
Reply from 196.210.140.1: bytes=32 time=22ms TTL=254
Reply from 196.210.140.1: bytes=32 time=25ms TTL=254
Reply from 196.210.140.1: bytes=32 time=26ms TTL=254
Reply from 196.210.140.1: bytes=32 time=28ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=34ms TTL=254
Reply from 196.210.140.1: bytes=32 time=22ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=26ms TTL=254
Reply from 196.210.140.1: bytes=32 time=25ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=36ms TTL=254
Reply from 196.210.140.1: bytes=32 time=35ms TTL=254
Request timed out.
Reply from 196.210.140.1: bytes=32 time=38ms TTL=254
Reply from 196.210.140.1: bytes=32 time=27ms TTL=254
Reply from 196.210.140.1: bytes=32 time=27ms TTL=254
Reply from 196.210.140.1: bytes=32 time=25ms TTL=254
Request timed out.
Reply from 196.210.140.1: bytes=32 time=36ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=24ms TTL=254
Reply from 196.210.140.1: bytes=32 time=22ms TTL=254
Reply from 196.210.140.1: bytes=32 time=22ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=39ms TTL=254
Reply from 196.210.140.1: bytes=32 time=29ms TTL=254
Reply from 196.210.140.1: bytes=32 time=24ms TTL=254
Reply from 196.210.140.1: bytes=32 time=25ms TTL=254
Request timed out.
Reply from 196.210.140.1: bytes=32 time=22ms TTL=254
Reply from 196.210.140.1: bytes=32 time=24ms TTL=254
Reply from 196.210.140.1: bytes=32 time=25ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=31ms TTL=254
Reply from 196.210.140.1: bytes=32 time=25ms TTL=254
Reply from 196.210.140.1: bytes=32 time=24ms TTL=254
Reply from 196.210.140.1: bytes=32 time=49ms TTL=254
Reply from 196.210.140.1: bytes=32 time=24ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=28ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=24ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=24ms TTL=254
Reply from 196.210.140.1: bytes=32 time=32ms TTL=254
Reply from 196.210.140.1: bytes=32 time=28ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Request timed out.
Reply from 196.210.140.1: bytes=32 time=39ms TTL=254
Reply from 196.210.140.1: bytes=32 time=27ms TTL=254
Reply from 196.210.140.1: bytes=32 time=27ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=29ms TTL=254
Reply from 196.210.140.1: bytes=32 time=23ms TTL=254
Reply from 196.210.140.1: bytes=32 time=43ms TTL=254

Ping statistics for 196.210.140.1:
Packets: Sent = 100, Received = 91, Lost = 9 (9% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 49ms, Average = 26ms

what does it mean? Telkom issues?
Click to expand...

Looks like. Packet loss not good. Ping is fluctuating, but not that bad, could be a line problem instead of a problem with the exchange. Is your line noisy if you pick up the phone? Do you have a ADSL filter? Do you have a house alarm? Many variables. Also, check your line stats in your router, SNR and attenuation can give an indication of a line fault.

Here are my line stats for you to compare:

Mode: ADSL_G.dmt
Traffic Type: ATM
Status: Up
Link Power State: L0

Downstream Upstream
Line Coding(Trellis): On On
SNR Margin (0.1 dB): 302 270
Attenuation (0.1 dB): 200 105
Output Power (0.1 dBm): 172 121
Attainable Rate (Kbps): 12160 1212

Path 0 Path 1
Downstream Upstream Downstream Upstream
Rate (Kbps): 4096 512

High SNR good, high atten bad AFAIK.

If you are having issues all the time, then I would say line, if it's just at certain times, then I would suspect exchange. Either way,I would log a fault with telkom (PM TelkomZA or 10210, your choice, I know which one I would choose :))

Good luck, hope you come right :)
 
wingnut771 said:
Looks like. Packet loss not good. Ping is fluctuating, but not that bad, could be a line problem instead of a problem with the exchange. Is your line noisy if you pick up the phone? Do you have a ADSL filter? Do you have a house alarm? Many variables. Also, check your line stats in your router, SNR and attenuation can give an indication of a line fault.

Here are my line stats for you to compare:

Mode: ADSL_G.dmt
Traffic Type: ATM
Status: Up
Link Power State: L0

Downstream Upstream
Line Coding(Trellis): On On
SNR Margin (0.1 dB): 302 270
Attenuation (0.1 dB): 200 105
Output Power (0.1 dBm): 172 121
Attainable Rate (Kbps): 12160 1212

Path 0 Path 1
Downstream Upstream Downstream Upstream
Rate (Kbps): 4096 512

High SNR good, high atten bad AFAIK.

If you are having issues all the time, then I would say line, if it's just at certain times, then I would suspect exchange. Either way,I would log a fault with telkom (PM TelkomZA or 10210, your choice, I know which one I would choose :))

Good luck, hope you come right :)
Click to expand...

Which one would you choose?

The line isnt "noisy" that I can hear but what do the stats below mean? Low snr....high atten?


Mode: ADSL_2plus
Type: ATM
Status: Up

Downstream Upstream
Line Coding(Trellis): On On
SNR Margin (dB): 142 56
Attenuation (dB): 595 380
Output Power (dBm): 150 116
Attainable Rate (Kbps): 4620 172
Rate (Kbps): 2048 171
D (interleaver depth): 1 1
Delay (msec): 0.25 0.22

HEC Errors: 0 0
OCD Errors: 0 0
LCD Errors: 0 0

Total ES: 4 0
 
Imagine101011 said:
Which one would you choose?

The line isnt "noisy" that I can hear but what do the stats below mean? Low snr....high atten?


Mode: ADSL_2plus
Type: ATM
Status: Up

Downstream Upstream
Line Coding(Trellis): On On
SNR Margin (dB): 142 56
Attenuation (dB): 595 380
Output Power (dBm): 150 116
Attainable Rate (Kbps): 4620 172
Rate (Kbps): 2048 171
D (interleaver depth): 1 1
Delay (msec): 0.25 0.22

HEC Errors: 0 0
OCD Errors: 0 0
LCD Errors: 0 0

Total ES: 4 0
Click to expand...

I would say that is your problem.
My SNR is 30db, your's is 15db.
My atten is around 20db, your's is 60db.

Are you far from the exchange?

I would log a line fault with Telkom (packet loss - noisy line)
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X