TPG Community

Get online support

Lost 10mbps downpseed after modem reset.

SOLVED Go to solution
Level 3

Previous modem Downstream/Upstream rates:

~45mbps/~18mbps

 

This morning I was cleaning around the modem and once done I noticed I no longer had internet connected. It was the only thing not working.

I tried turning it off and on and nothing came of it. I then went about unpluggin everything, and blowing out any potential dust and firmly placing the plugs back into the back of the modem.

This seemed to work and it finally connected back to the internet, except I lost roughly half the downstream speed and it sat at ~22mbps with the same upstream of ~18mbps.

I gave it a restart to see if it would fix it and it only went up a tiny amount to ~32mbps/~18mbps.

 

Can you run a test on my line and potentially the modem to see if there is a problem.

Current DSL Information.

DSL synchronization status: Up
Connection status: Showtime
Upstream line rate (kbit/s): 18170
Downstream line rate (kbit/s): 32548
Maximum upstream rate (kbit/s): 18414
Maximum downstream rate (kbit/s): 33049
Upstream noise safety coefficient (dB): 7.6
Downstream noise safety coefficient (dB): 6.5
Upstream interleave depth: 0
Downstream interleave depth: 0
Line standard: VDSL
Upstream line attenuation (dB): 36.8
Downstream line attenuation (dB): 17.7
Upstream output power (dBmV): 9.3
Downstream output power (dBmV): 11.8
Downstream interleave depth: None

 

I've attached a pic of the recently speedtests I have done on the Speedtest app.

 

Could you also please inform me of the costs to a replacement modem.

1 ACCEPTED SOLUTION

Accepted Solutions
Level 3

Well it stayed up for ~8 hours then dropped again. Hopefully the tech; if still coming around, will be able to fix it.

View solution in original post

6 REPLIES 6
Level 3

My sync settings this morning at 9am.

DSL synchronization status: Up
Connection status: Showtime
Upstream line rate (kbit/s): 17990
Downstream line rate (kbit/s): 26516
Maximum upstream rate (kbit/s): 19867
Maximum downstream rate (kbit/s): 37255
Upstream noise safety coefficient (dB): 9
Downstream noise safety coefficient (dB): 12.9
Upstream interleave depth: 0
Downstream interleave depth: 0
Line standard: VDSL
Upstream line attenuation (dB): 36.8
Downstream line attenuation (dB): 17.6
Upstream output power (dBmV): 9.6
Downstream output power (dBmV): 11.6
Downstream interleave depth: None

My internet doesn't seem to be as stable as it was 2 days ago, it is disconnecting alot now.

Level 3

These intermitant disconnections are getting really annoying.

DSL synchronization status: Up
Connection status: Showtime
Upstream line rate (kbit/s): 21117
Downstream line rate (kbit/s): 35831
Maximum upstream rate (kbit/s): 21117
Maximum downstream rate (kbit/s): 36259
Upstream noise safety coefficient (dB): 6.2
Downstream noise safety coefficient (dB): 6.3
Upstream interleave depth: 0
Downstream interleave depth: 0
Line standard: VDSL
Upstream line attenuation (dB): 36.9
Downstream line attenuation (dB): 17.6
Upstream output power (dBmV): 9.4
Downstream output power (dBmV): 11.8
Downstream interleave depth: None

The network seems to be fine, its just the internet connection that is the problem.

Could a faulty cable connecting to the phone wall socket be a potential problem?

Level 3

When it drops out I cannot even go into the modem settings.

 

Cable error[8180]. Please make sure the cable is connected to the gateway properly. If the cable connection is secure, click "Try Again". You can also click Try WLAN to set up a WLAN connection. 

One of the errors that shows up when it disconnects.

Level 3

This is getting beyond rediculous, it is taking upwards of 10+mins for it to "attempt" to reconnect.

Just replaced the RJ45 phone cable, will see if it holds for long.

I have my doubts.

Level 3

With the change of the RJ45 cable it has now held for 1.5 hours, hopefully that was a cause of the issues. Will report back if problem picks up again.

Level 3

Well it stayed up for ~8 hours then dropped again. Hopefully the tech; if still coming around, will be able to fix it.

View solution in original post