Intermittent Connection - Need help!

K

Kevmb

Member
Joined
Jan 17, 2011
Messages
18
Reaction score
0
Hi,

I have very little experience regarding ADSL and internet connectivity so please bare with me...

In short, our internet connection is working, but during certain times the connection gets dropped over and over again.
It works for 5 minutes, gets dropped for 5 minutes, spends another 5 minutes syncing to the network, then works, and so on.

It happens mostly between 8am-10am and 5pm-9pm, when I actually want to use the internet too.

My suburb is Risidale, next to Northcliff/ Cresta/ Linden, and near Randburg.
I'm not sure where my exchange is, but according to this thread it is in Linden, which is a couple of kilometers away from our house.
(http://mybroadband.co.za/vb/showthread.php/552483-Linden-Northcliff-ADSL-problems?highlight=risidale)

I do not torrent or do big downloads.

My router is an MWEB one (model: Technicolor TG589vn v3)

I have phoned both my ISP (MWEB) and Telkom, and both give me different reasons but no solution.

MWEB blames Telkom saying our exchange is congested during those times.

Telkom blames many things, including MWEB, and we have tried all of their solutions but to no avail.
Some include:
- New/ different router
- Decreasing our line speed
- Resetting the port
- Getting our line tested by a technician (which was verified as working perfectly)
- Changing ISP (doesn't work)

Also, Telkom did mention they were upgrading "the" exchange (he didn't mention which one), but they said it would be fixed over two months ago and yet nothing has changed

All I can say is I have no idea where else to go, so please can someone offer me some advice on what to do next.

Many Thanks!
 
"t happens mostly between 8am-10am and 5pm-9pm, when I actually want to use the internet too."


What seems to be your problem is an overloaded pop. What happens is you have something called contention ratio which is the amount of users put in to a pool to share the same line what happens is when there are too many users on a line at the same time its drops, this is what makes adsl so cheap because they share it with more people using less equipment but dedicating nothing to anybody which makes the line so bad.
 
@Andrew; Hi and thanks for that explanation. Much better than what I received from my ISP and Telkom. Would you perhaps know of a way to fix this?

@Rickster; Hi, Which test would that be? a Tracert? I apologize for my incompetence :P
 
Kevmb said:
@Andrew; Hi and thanks for that explanation. Much better than what I received from my ISP and Telkom. Would you perhaps know of a way to fix this?

@Rickster; Hi, Which test would that be? a Tracert? I apologize for my incompetence :P
Click to expand...

Test? I asked for line stats, which are found in your router.

They look like this.

be6d18e513.png


It should be under "statistics" or similar.
 
Thanks for showing me :)

Link Information

Uptime: 0 days, 0:02:24

DSL Type: ITU-T G.992.5 Annex A (ADSL2+ over POTS)

Bandwidth (Up/Down) [kbps/kbps]: 511 / 2.048

Output Power (Up/Down) [dBm]: 6,2 / 2,5

Line Attenuation (Up/Down) [dB]: 4,3 / 14,0

SN Margin (Up/Down) [dB]: 22,0 / 27,2

System Vendor ID (Local/Remote): TMMB / ----

Chipset Vendor ID (Local/Remote): BDCM / GSPN

Loss of Framing (Local/Remote): 1.575 / 0

Loss of Signal (Local/Remote): 178 / 0

Loss of Power (Local/Remote): 0 / 0

Loss of Link (Remote): -

Error Seconds (Local/Remote): 1.894 / 0

FEC Errors (Up/Down): 0 / 0

CRC Errors (Up/Down): 0 / 0

HEC Errors (Up/Down): 0 / 0
 
Kevmb said:
Thanks for showing me :)

Link Information

Uptime: 0 days, 0:02:24

DSL Type: ITU-T G.992.5 Annex A (ADSL2+ over POTS)

Bandwidth (Up/Down) [kbps/kbps]: 511 / 2.048

Output Power (Up/Down) [dBm]: 6,2 / 2,5

Line Attenuation (Up/Down) [dB]: 4,3 / 14,0

SN Margin (Up/Down) [dB]: 22,0 / 27,2

System Vendor ID (Local/Remote): TMMB / ----

Chipset Vendor ID (Local/Remote): BDCM / GSPN

Loss of Framing (Local/Remote): 1.575 / 0

Loss of Signal (Local/Remote): 178 / 0

Loss of Power (Local/Remote): 0 / 0

Loss of Link (Remote): -

Error Seconds (Local/Remote): 1.894 / 0

FEC Errors (Up/Down): 0 / 0

CRC Errors (Up/Down): 0 / 0

HEC Errors (Up/Down): 0 / 0
Click to expand...

Those are very good stats so it is congestion, but to prove it we need a tracert to anything.
 
Tracert as ADSL2+ to mybroadband.co.za

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

1 1 ms <1 ms <1 ms myrouter.Home [192.168.1.1]
2 20 ms 21 ms 22 ms 41-132-20-1.dsl.mweb.co.za [41.132.20.1]
3 21 ms 22 ms 24 ms 197-80-96-162.jhb.mweb.co.za [197.80.96.162]
4 19 ms 21 ms 18 ms vl-92-vic-hscore-1.mweb.co.za [197.80.2.1]
5 26 ms 23 ms 23 ms tengig-0-0-0-2-11-vic-p-2.mweb.co.za [197.80.5.2
26]
6 23 ms 18 ms 18 ms 197-80-7-102.jhb.mweb.co.za [197.80.7.102]
7 20 ms 31 ms 19 ms africainx.jb1.napafrica.net [196.46.25.135]
8 21 ms 23 ms 42 ms CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.
10G.za [41.84.13.66]
9 21 ms 21 ms 21 ms 41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
10 54 ms 21 ms 22 ms core-access-switch1.jnb1.host-h.net [197.189.193
.1]
11 46 ms 53 ms 57 ms row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
12 21 ms 20 ms 20 ms 197.242.89.170

Trace complete.

I really cannot find any setting to change it to ADSL from ADSL2+, but I do remember my other Billion W40 router having that option so I will give that one a try too.
 
Kevmb said:
Tracert as ADSL2+ to mybroadband.co.za

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

1 1 ms <1 ms <1 ms myrouter.Home [192.168.1.1]
2 20 ms 21 ms 22 ms 41-132-20-1.dsl.mweb.co.za [41.132.20.1]
3 21 ms 22 ms 24 ms 197-80-96-162.jhb.mweb.co.za [197.80.96.162]
4 19 ms 21 ms 18 ms vl-92-vic-hscore-1.mweb.co.za [197.80.2.1]
5 26 ms 23 ms 23 ms tengig-0-0-0-2-11-vic-p-2.mweb.co.za [197.80.5.2
26]
6 23 ms 18 ms 18 ms 197-80-7-102.jhb.mweb.co.za [197.80.7.102]
7 20 ms 31 ms 19 ms africainx.jb1.napafrica.net [196.46.25.135]
8 21 ms 23 ms 42 ms CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.
10G.za [41.84.13.66]
9 21 ms 21 ms 21 ms 41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
10 54 ms 21 ms 22 ms core-access-switch1.jnb1.host-h.net [197.189.193
.1]
11 46 ms 53 ms 57 ms row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
12 21 ms 20 ms 20 ms 197.242.89.170

Trace complete.

I really cannot find any setting to change it to ADSL from ADSL2+, but I do remember my other Billion W40 router having that option so I will give that one a try too.
Click to expand...

Might have to do a tracert when it is giving problems also
 
Okay so the other router is a Billion N73X* (not W40)

The options I could change it to were ADSL2+, ADSL2, and ADSL Multimode. I chose the latter.
Other options included "Auto", G.Lite, T1.413, and G.DMT (Not sure if relevant)

Will see if there is any improvement.

Will also do a Tracert when/ if the connection drops again.

Router stats:

DSP Firmware Version DMT FwVer: 3.10.0.0_A, HwVer:TeF7_7.0
DMT Status Up
Operational Mode ADSL2+ (It still shows this after I changed it to ADSL Multimode)
Upstream 511 kbps
Downstream 2048 kbps
SNR Margin (Upstream) 25.5 db
SNR Margin (Downstream) 39.1 db
Line Attenuation (Upstream) 4.1 db
Line Attenuation (Downstream) 12.0 db

Tracert when set to ADSL Multimode

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

1 1 ms 1 ms 1 ms home.gateway.home.gateway [192.168.1.254]
2 17 ms 17 ms 17 ms 41-132-20-1.dsl.mweb.co.za [41.132.20.1]
3 17 ms 18 ms 17 ms 197-80-96-210.jhb.mweb.co.za [197.80.96.210]
4 18 ms 18 ms 18 ms vl-92-vic-hscore-2.mweb.co.za [197.80.2.2]
5 24 ms 22 ms 22 ms tengig-0-7-0-2-12-vic-p-2.mweb.co.za [197.80.5.2
42]
6 19 ms 18 ms 18 ms 197-80-7-102.jhb.mweb.co.za [197.80.7.102]
7 19 ms 18 ms 19 ms africainx.jb1.napafrica.net [196.46.25.135]
8 20 ms 21 ms 20 ms CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.
10G.za [41.84.13.66]
9 21 ms 20 ms 23 ms 41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
10 21 ms 21 ms 21 ms core-access-switch1.jnb1.host-h.net [197.189.193
.1]
11 21 ms 21 ms 21 ms row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
12 20 ms 20 ms 19 ms 197.242.89.170

Trace complete.

Tracert when connection was down

Unable to resolve target system name mybroadband.co.za.
 
I should also add that we were originally on a 4mbit line when the problem started, and we then moved down to a 2mbit line because Telkom said it would work. :P
 
Ran the tests when it down,

There was no noise on the phone line when it was down (no more than usual)

Tracerts:

Local Tracert

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * 39 ms 39 ms 196.28.178.66
9 92 ms 54 ms 41 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
10 43 ms 43 ms 43 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
11 43 ms 43 ms 42 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
12 39 ms 39 ms 38 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.

International Tracert

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

1 4 ms 1 ms 1 ms home.gateway.home.gateway [192.168.1.254]
2 17 ms 16 ms 16 ms 41-132-20-1.dsl.mweb.co.za [41.132.20.1]
3 17 ms 18 ms 17 ms 197-80-96-162.jhb.mweb.co.za [197.80.96.162]
4 18 ms 18 ms 18 ms vl-92-vic-hscore-2.mweb.co.za [197.80.2.2]
5 201 ms 199 ms 199 ms tengig-0-7-0-2-12-vic-p-1.mweb.co.za [197.80.5.241]
6 202 ms 199 ms 202 ms s2-pos0-3-0-0-pos0-3-2-0-thd-p-2.mweb.co.za [197.80.5.7]
7 201 ms 198 ms 199 ms be-3-777-thd-up-1.mweb.co.za [176.67.177.131]
8 197 ms 199 ms 200 ms be-15-779-thd-linx-1.mweb.co.za [176.67.177.228]
9 198 ms 197 ms 197 ms linx-gw1.thn.ncuk.net [195.66.224.240]
10 197 ms 198 ms 197 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
11 197 ms 198 ms 197 ms te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
12 196 ms 195 ms 196 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

International Speedtest

Local Speedtest

Line test:

Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 19ms
Your maximum ping was 37ms

Looking at your average ping, your line seems to be running perfectly :-)
Looking at your maximum ping, however, it seems as though there could be a slight intermittant issue on the line. If required, please post the results to a forum post.

Detailed Report
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)

Pinging 41.132.20.1 with 32 bytes of data:
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=20ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=37ms TTL=254
Reply from 41.132.20.1: bytes=32 time=36ms TTL=254
Reply from 41.132.20.1: bytes=32 time=19ms TTL=254
Reply from 41.132.20.1: bytes=32 time=19ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=17ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=30ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=17ms TTL=254
Reply from 41.132.20.1: bytes=32 time=17ms TTL=254
Reply from 41.132.20.1: bytes=32 time=19ms TTL=254
Reply from 41.132.20.1: bytes=32 time=17ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=17ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254

Ping statistics for 41.132.20.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 37ms, Average = 19ms

2014-09-05 8:23:40,80
 
Kevmb said:
Ran the tests when it down,

There was no noise on the phone line when it was down (no more than usual)

Tracerts:

Local Tracert

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * 39 ms 39 ms 196.28.178.66
9 92 ms 54 ms 41 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
10 43 ms 43 ms 43 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
11 43 ms 43 ms 42 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
12 39 ms 39 ms 38 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.

International Tracert

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

1 4 ms 1 ms 1 ms home.gateway.home.gateway [192.168.1.254]
2 17 ms 16 ms 16 ms 41-132-20-1.dsl.mweb.co.za [41.132.20.1]
3 17 ms 18 ms 17 ms 197-80-96-162.jhb.mweb.co.za [197.80.96.162]
4 18 ms 18 ms 18 ms vl-92-vic-hscore-2.mweb.co.za [197.80.2.2]
5 201 ms 199 ms 199 ms tengig-0-7-0-2-12-vic-p-1.mweb.co.za [197.80.5.241]
6 202 ms 199 ms 202 ms s2-pos0-3-0-0-pos0-3-2-0-thd-p-2.mweb.co.za [197.80.5.7]
7 201 ms 198 ms 199 ms be-3-777-thd-up-1.mweb.co.za [176.67.177.131]
8 197 ms 199 ms 200 ms be-15-779-thd-linx-1.mweb.co.za [176.67.177.228]
9 198 ms 197 ms 197 ms linx-gw1.thn.ncuk.net [195.66.224.240]
10 197 ms 198 ms 197 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
11 197 ms 198 ms 197 ms te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
12 196 ms 195 ms 196 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

International Speedtest

Local Speedtest

Line test:

Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 19ms
Your maximum ping was 37ms

Looking at your average ping, your line seems to be running perfectly :-)
Looking at your maximum ping, however, it seems as though there could be a slight intermittant issue on the line. If required, please post the results to a forum post.

Detailed Report
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)

Pinging 41.132.20.1 with 32 bytes of data:
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=20ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=37ms TTL=254
Reply from 41.132.20.1: bytes=32 time=36ms TTL=254
Reply from 41.132.20.1: bytes=32 time=19ms TTL=254
Reply from 41.132.20.1: bytes=32 time=19ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=17ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=30ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=17ms TTL=254
Reply from 41.132.20.1: bytes=32 time=17ms TTL=254
Reply from 41.132.20.1: bytes=32 time=19ms TTL=254
Reply from 41.132.20.1: bytes=32 time=17ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=17ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254

Ping statistics for 41.132.20.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 37ms, Average = 19ms

2014-09-05 8:23:40,80
Click to expand...


Try:
If you have a surge protector .Remove it and connect the Telkom connection to the router.
 
@sreddi Hi, we don't have a surge protector at the moment

Redid the line test:

Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 29ms
Your maximum ping was 330ms

Looking at your average ping, your line seems to be running perfectly :-)
Looking at your maximum ping, however, it seems as though there could be a serious intermittent fault on the line. This could be a cause of an issue. Please post the results (at the end of the program) into the forum for advice.

So if that is the case, is there anything I could possibly do to fix it? :P
Could I change ISP's?
Ask Telkom to put me onto a different line?
Upgrade to premium uncapped?
Anything?
 
Detailed Report
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)

Pinging 41.132.20.1 with 32 bytes of data:
Reply from 41.132.20.1: bytes=32 time=19ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=21ms TTL=254
Reply from 41.132.20.1: bytes=32 time=19ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=19ms TTL=254
Reply from 41.132.20.1: bytes=32 time=19ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=20ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=27ms TTL=254
Reply from 41.132.20.1: bytes=32 time=17ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=17ms TTL=254
Reply from 41.132.20.1: bytes=32 time=24ms TTL=254
Reply from 41.132.20.1: bytes=32 time=330ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=20ms TTL=254
Reply from 41.132.20.1: bytes=32 time=18ms TTL=254
Reply from 41.132.20.1: bytes=32 time=20ms TTL=254
Reply from 41.132.20.1: bytes=32 time=19ms TTL=254
Reply from 41.132.20.1: bytes=32 time=19ms TTL=254

Ping statistics for 41.132.20.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 330ms, Average = 29ms
 
Hi guys, just letting you know it was the exchange that was causing the problem.

As of yesterday Telkom upgraded the exchange from copper to fiber and I am now getting consistent 4meg speeds with no drops in connection.

Thanks again for all the input! Really do appreciate it
 
Kevmb said:
Hi guys, just letting you know it was the exchange that was causing the problem.

As of yesterday Telkom upgraded the exchange from copper to fiber and I am now getting consistent 4meg speeds with no drops in connection.

Thanks again for all the input! Really do appreciate it
Click to expand...

How did you manage to get them to do that?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X