Xfinity plant
Xfinity globe
Community Forum

Gigabit Download Speeds Slower Than Advertised | Possible Noise Issue

Regular Visitor

Gigabit Download Speeds Slower Than Advertised | Possible Noise Issue

Hello,

 

Have had the gigabit tier service for 5 months and in that time have not received faster than 45% of advertised download speeds. The upload speeds are to be expected since it is a whopping 35 Mbps.

 

I have verified that I am subscribed to the Gigabit Tier service.

My modem is a supported SB8200.

My router is currently a Netgear R6300.

I have tested plugging directly into the modem as well as through the router.

This is all hardwired, not using the wireless.

 

The following are the stats taken from my modem:

 

Downstream Bonded Channels
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
25 Locked QAM256 639000000 Hz -2.0 dBmV 40.6 dB 232 663
1 Locked QAM256 495000000 Hz -2.7 dBmV 41.1 dB 160 292
2 Locked QAM256 501000000 Hz -3.3 dBmV 40.8 dB 128 282
3 Locked QAM256 507000000 Hz -3.2 dBmV 40.9 dB 129 326
4 Locked QAM256 513000000 Hz -3.3 dBmV 40.8 dB 217 325
5 Locked QAM256 519000000 Hz -2.8 dBmV 40.8 dB 179 439
6 Locked QAM256 525000000 Hz -2.8 dBmV 40.7 dB 183 466
7 Locked QAM256 531000000 Hz -2.5 dBmV 40.9 dB 196 537
8 Locked QAM256 537000000 Hz -2.4 dBmV 40.9 dB 222 447
9 Locked QAM256 543000000 Hz -2.5 dBmV 40.8 dB 215 512
10 Locked QAM256 549000000 Hz -2.3 dBmV 40.8 dB 246 595
11 Locked QAM256 555000000 Hz -2.1 dBmV 40.8 dB 235 636
12 Locked QAM256 561000000 Hz -1.8 dBmV 41.0 dB 268 636
13 Locked QAM256 567000000 Hz -1.4 dBmV 40.9 dB 296 664
14 Locked QAM256 573000000 Hz -1.5 dBmV 40.9 dB 243 807
15 Locked QAM256 579000000 Hz -1.4 dBmV 41.0 dB 247 712
16 Locked QAM256 585000000 Hz -1.6 dBmV 40.8 dB 279 819
17 Locked QAM256 591000000 Hz -1.5 dBmV 41.0 dB 300 923
18 Locked QAM256 597000000 Hz -1.3 dBmV 40.8 dB 304 847
19 Locked QAM256 603000000 Hz -1.3 dBmV 41.0 dB 367 927
20 Locked QAM256 609000000 Hz -1.4 dBmV 41.0 dB 327 1068
21 Locked QAM256 615000000 Hz -1.6 dBmV 40.9 dB 448 870
22 Locked QAM256 621000000 Hz -1.7 dBmV 40.7 dB 335 976
23 Locked QAM256 627000000 Hz -1.9 dBmV 40.8 dB 359 1147
24 Locked QAM256 633000000 Hz -1.8 dBmV 40.6 dB 446 1080
26 Locked QAM256 645000000 Hz -2.0 dBmV 40.6 dB 354 1237
27 Locked QAM256 651000000 Hz -2.3 dBmV 40.6 dB 437 1200
28 Locked QAM256 657000000 Hz -2.4 dBmV 40.7 dB 334 1311
159 Locked Other 666000000 Hz 1.5 dBmV 39.2 dB 4124483 17

 

If I'm reading this correctly, it appears that I have possible noise in the line as there are a high number of errors outside of the OFDM channel.

 

This is over the course of a week after power-cycling both my modem and my router.

Speed tests at fast.com, speedtest.net and Comcast's speed test average around 290 Mbps down, varying between 75 and 430 Mbps.

Neubot testing for the week shows the following:

 

Timestamp Connect time Appl. latency Download speed Upload speed
2018-07-05 10:06 19 ms 20 ms 180.009 Mbit/s 32.220 Mbit/s
2018-07-05 08:55 20 ms 17 ms 258.292 Mbit/s 34.162 Mbit/s
2018-07-05 07:45 16 ms 16 ms 235.447 Mbit/s 37.753 Mbit/s
2018-07-05 04:15 11 ms 16 ms 361.188 Mbit/s 33.910 Mbit/s
2018-07-05 00:20 16 ms 17 ms 114.951 Mbit/s 33.107 Mbit/s
2018-07-04 22:46 19 ms 20 ms 273.082 Mbit/s 31.311 Mbit/s
2018-07-04 22:23 15 ms 16 ms 364.785 Mbit/s 37.965 Mbit/s
2018-07-04 21:59 19 ms 16 ms 130.603 Mbit/s 37.468 Mbit/s
2018-07-04 20:25 15 ms 16 ms 274.377 Mbit/s 36.981 Mbit/s
2018-07-04 14:56 18 ms 19 ms 244.977 Mbit/s 27.505 Mbit/s
2018-07-04 14:10 15 ms 16 ms 243.981 Mbit/s 34.509 Mbit/s
2018-07-04 12:59 17 ms 16 ms 162.809 Mbit/s 37.746 Mbit/s
2018-07-04 12:36 15 ms 16 ms 124.356 Mbit/s 34.638 Mbit/s
2018-07-04 11:49 17 ms 17 ms 164.358 Mbit/s 38.545 Mbit/s
2018-07-03 06:59 14 ms 16 ms 273.382 Mbit/s 31.839 Mbit/s
2018-07-03 05:10 14 ms 16 ms 362.613 Mbit/s 35.416 Mbit/s
2018-07-03 03:21 17 ms 16 ms 128.887 Mbit/s 38.503 Mbit/s
2018-07-02 10:32 18 ms 21 ms 149.533 Mbit/s 37.408 Mbit/s
2018-07-02 09:43 14 ms 16 ms 163.384 Mbit/s 37.859 Mbit/s
2018-07-02 07:14 15 ms 16 ms 114.468 Mbit/s 32.647 Mbit/s
2018-07-01 22:09 19 ms 20 ms 261.158 Mbit/s 30.987 Mbit/s
2018-07-01 21:45 16 ms 15 ms 228.784 Mbit/s 35.963 Mbit/s
2018-07-01 21:20 14 ms 17 ms 305.524 Mbit/s 37.734 Mbit/s
2018-07-01 19:41 15 ms 16 ms 337.646 Mbit/s 38.341 Mbit/s
2018-07-01 19:16 44 ms 36 ms 9.243 Mbit/s 15.788 Mbit/s
2018-07-01 07:31 18 ms 20 ms 189.330 Mbit/s 37.761 Mbit/s
2018-07-01 07:05 16 ms 16 ms 263.321 Mbit/s 35.419 Mbit/s
2018-07-01 04:02 15 ms 16 ms 227.177 Mbit/s 32.910 Mbit/s
2018-07-01 03:10 15 ms 16 ms 125.498 Mbit/s 34.795 Mbit/s
2018-07-01 01:00 29 ms 29 ms 191.069 Mbit/s 34.707 Mbit/s
2018-07-01 00:34 19 ms 21 ms 198.846 Mbit/s 31.038 Mbit/s
2018-06-30 23:16 17 ms 18 ms 386.926 Mbit/s 37.871 Mbit/s
2018-06-30 06:34 14 ms 16 ms 281.967 Mbit/s 36.063 Mbit/s
2018-06-30 06:08 15 ms 16 ms 274.132 Mbit/s 34.049 Mbit/s
2018-06-30 04:25 18 ms 20 ms 229.485 Mbit/s 37.788 Mbit/s
2018-06-30 03:08 18 ms 20 ms 224.526 Mbit/s 32.783 Mbit/s
2018-06-29 23:17 26 ms 20 ms 173.129 Mbit/s 34.186 Mbit/s
2018-06-29 22:51 13 ms 17 ms 146.229 Mbit/s 37.486 Mbit/s
2018-06-29 21:48 23 ms 17 ms 230.400 Mbit/s 38.156 Mbit/s
2018-06-29 09:17 14 ms 16 ms 215.838 Mbit/s 34.121 Mbit/s
2018-06-29 07:56 16 ms 20 ms 239.848 Mbit/s 31.879 Mbit/s
2018-06-29 03:26 15 ms 16 ms 197.238 Mbit/s 34.108 Mbit/s
2018-06-29 02:32 15 ms 16 ms 212.598 Mbit/s 34.737 Mbit/s
2018-06-29 02:05 20 ms 17 ms 236.607 Mbit/s 35.872 Mbit/s

 

As you can see, most times are off hours as well, so it shouldn't be an issue with congestion.

 

Any help will be much appreciated, thanks!

Problem Solver

Re: Gigabit Download Speeds Slower Than Advertised | Possible Noise Issue

What about the Upstream signal levels and the event log?
Expert

Re: Gigabit Download Speeds Slower Than Advertised | Possible Noise Issue

Hi @WubADubDub

Your downstream channel levels look fine. The reported errors on your ODMF channel are normal and not a cause for concern. Make sure your upstream levels meet specifications too (see the troubleshooting guide).

 

 

Other things:

 

    • Disable your antivirus/firewall briefly and check speeds.
    • Boot your computer into safe mode w/networking and check speeds.
    • Verify that you meet the system requirements. 

 

gig_system_req.PNG

Regular Visitor

Re: Gigabit Download Speeds Slower Than Advertised | Possible Noise Issue

Hi, and thanks for responding.

 

Here's the upstream data:

Upstream Bonded Channels
Channel Channel ID Lock Status US Channel Type Frequency Width Power
1 1 Locked SC-QAM 36500000 Hz 6400000 Hz 42.8 dBmV
2 2 Locked SC-QAM 30100000 Hz 6400000 Hz 42.3 dBmV
3 3 Locked SC-QAM 23700000 Hz 6400000 Hz 42.8 dBmV

 

Here's the event log info:

 

Time Priority Description
1-1-1970, 0:0:41 Notice(6) "Honoring MDD; IP provisioning mode = IPv6"
1-1-1970, 0:0:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
6-29-2018, 11:37:44 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
6-29-2018, 11:37:31 Critical(3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
6-29-2018, 11:37:30 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
6-29-2018, 11:36:14 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
6-11-2018, 11:30:54 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
6-8-2018, 13:59:56 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
6-3-2018, 18:5:30 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
6-3-2018, 18:5:17 Critical(3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
6-3-2018, 18:5:17 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
6-3-2018, 18:4:0 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
5-30-2018, 14:47:16 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
5-30-2018, 14:47:16 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:9:31 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
5-30-2018, 14:18:45 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
5-30-2018, 14:18:45 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
5-30-2018, 14:18:25 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
5-30-2018, 14:18:25 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
5-30-2018, 14:18:5 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
5-30-2018, 14:18:5 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
5-30-2018, 14:17:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
5-30-2018, 14:17:27 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
5-30-2018, 14:17:24 Critical(3) "SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
5-30-2018, 14:17:23 Critical(3) "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
5-28-2018, 14:22:54 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
5-14-2018, 16:59:12 Critical(3) "16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
5-14-2018, 16:59:12 Critical(3) "Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
5-14-2018, 16:59:12 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:36 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
4-30-2018, 12:40:0 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
4-30-2018, 12:39:42 Critical(3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
4-30-2018, 12:39:41 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
4-30-2018, 12:38:30 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
4-12-2018, 15:23:47 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
4-12-2018, 15:23:46 Critical(3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
4-12-2018, 15:23:45 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
4-12-2018, 15:23:26 Critical(3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
4-12-2018, 15:23:25 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
4-12-2018, 15:22:17 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
4-12-2018, 14:29:26 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:12:2a:fd;CMTS-MAC=00:59:dc:78:c9:d0;CM-QOS=1.1;CM-VER=3.1;"
4-12-2018, 14:29:7

Critical(3)

 

This last column in the last line is blank in my log, just cuts off there.

 

@nerdbug:

 

Thanks, here's the additional info you mentioned and my hardware's specs.

 

Disabling firewall/AV results in no change in observed speeds.

Safe mode w/ networking results in no change in observed speeds.

 

gig_system_req.PNG

 

Operating System: Windows 10 Home Version 17134.112

Browser: Chrome Version 67.0.3396.99 (Official Build) (64-bit) and Firefox 61.0.1 (64-bit)

Ethernet Cable: Cat7

Ethernet Adapter: Intel I217-V Gigabit Adapter

CPU: Intel 4770K @ 3.9 GHz

SSD: Samsung 850 EVO 250 GB

 

Using the same testing method with the 1.3 Gigabit wireless adapter I have results in no change as well.

Expert

Re: Gigabit Download Speeds Slower Than Advertised | Possible Noise Issue

@WubADubDub

I think your next step is to have an employee to take a look and make sure everything on your account is correct. They can also look at your modem/node health.

 

I've asked an employee to check the CMTS for real-time and historical RF signal reports from your modem. They can also check your local node/plant for any degradation or error reports. You can expect a reply in this thread. 

Highlighted
Official Employee

Re: Gigabit Download Speeds Slower Than Advertised | Possible Noise Issue

 

WubADubDub, thanks for reaching out. Let's look into your service issues. Please send me your full name via private message so I can access your account. 

 

KenF