ADSL2 and ADSL2+ carry asymmetric broadband over a copper telephone pair. Their names identify signaling standards. To understand your service, combine the negotiated mode with your line statistics, purchased profile and a controlled test through the modem.
Identify the mode your line actually uses
ITU-T G.992.3 specifies ADSL2; G.992.5 specifies ADSL2+. ADSL2+ extends the downstream frequency range. The G.992.5 summary describes downstream operation up to 2.208 MHz. Additional spectrum can provide more capacity where line conditions support it.
Record the modem’s actual negotiated standard and annex, along with the provider’s service profile. The annex and configuration affect the frequencies and service combinations used. A modem supporting ADSL2+ can still connect in another supported mode when the provider or line configuration requires it. Ask the provider to confirm compatibility before buying replacement equipment.
Read the statistics as a set
| Field | Meaning | Useful comparison |
|---|---|---|
| Negotiated or sync rate | The current data rate established across the DSL link | Compare upstream and downstream separately with the subscribed profile. |
| Attainable rate | The modem’s estimate under its current assumptions and conditions | Track changes over time; treat it as an estimate rather than an offered service. |
| SNR margin | Headroom reported relative to the current operating target | Compare at similar times and with the provider’s expected profile. |
| Attenuation | A reported measure of signal loss on the line | Interpret using the mode and equipment’s own definitions. |
| Errors and retrains | Counters and events that help describe stability | Record elapsed time; distinguish corrected errors from failed data or reconnects. |
Labels differ by modem. The CenturyLink Zyxel C3000Z status example shows negotiated speed, estimated attainable rate, SNR and error information together. Use your own model’s help to interpret its counters. A single universal “good SNR” cutoff would hide differences in profiles and line management.
Compare sync and throughput fairly
Hypothetical downstream example
A modem reports 12 Mbps sync and 15 Mbps attainable. A wired speed test measures 10.2 Mbps while other local traffic is paused. Measured throughput is 10.2 ÷ 12 = 85% of the sync rate. The 15 Mbps estimate suggests a question about the line profile, not an automatic entitlement to that speed.
This invented ratio is an arithmetic example, not a normal-performance threshold. Protocol overhead, the service profile, congestion and the test endpoint all influence application throughput. Compare repeated results with the provider’s expectations for that service.
Use the same wired device and test method, record the time and ensure another upload or backup is not consuming the connection. Note units: Mbps measures megabits per second, while a download application may display megabytes per second. Eight bits make one byte, before accounting for overhead.
Choose the next check from the evidence
If sync is stable but measured throughput varies by time of day, compare quiet and busy periods and test another suitable endpoint. If the DSL connection itself repeatedly retrains, save the timing, line statistics and error counts for the provider. Avoid repeated manual reboots while collecting evidence, because they reset useful counters and change the observation period.
If sync consistently matches a lower purchased profile, discuss available services with the provider using the exact line address and modem model. If performance changed after moving equipment, use the DSL troubleshooting guide to check the local setup systematically. Preserve a before-and-after record for each change so support can follow the evidence.
Explore the Internet library
Internet: Connections, Networks and Online Life brings together connection choices, network explanations, travel connectivity and practical online tasks.