Same issue will not go online Zoom 5352 called twice to comcast told them I read this issue online on their forums and they only tried to ping it said it timesout. I said I know you need to do something on your end to make it work I am reading this is a known issue please let me speak to a senior tech. They said you need to either contact Zoom or return the modem and buy one compatible. I told them it is on your DOCIS 3 list. Very frustrating and waste of time calling Comcast. I emailed ZOOM as it was a Sunday so hope they fix it Monday.

I upgraded to Extreme a couple months ago and had 105ish speeds, but checked today because things seemed slow and found I'm back to the Blast speed 60ish.  Is this Comcasts system or ?

I have a log-in site on my list of available services with my business name and "-Guest".

If I try to open it, it asks for a password.  I have never used or setup this account so I don't know the password.  How do I set it up for use by my patients in the waiting room?

Long story short:

- I have been having intermitent HSD with T3 time outs for several months.

- Called to schedule a tech to come out. Found out that my uSNR is low and there seems to be a problem on my node since there were several open tickets for the same issue.

- Tech put in a work order for work to be done at the tap and to investigate the cause of the low uSNR.

- I got an automated phone call from Comcast stating that outside work has been scheduled and that I would recieve a phone call once the work was completed.

-  I was told this work would be completed within 24-48hrs. This was Tuesday June 2nd. I have yet to receive any phone call.

- I have recently had a bunch of T3 time outs as recent as last night. So obviously nothing was looked at.

- I have called to inquire about the scheduled work and no one could seem to find the work order.

Does this seem typical of Comcast?

Hello,

There are several of us at my company that use Cisco IP phones for telecommuting, connected to our XFINITY home internet service, and they connect back to our home office via VPN.  The phones have recently stopped being able to connect via VPN over the XFINITY internet connection, whether it be through a regular Motorola cable modem, or a Comcast-provided XFINITY modem/router adapter.  These phones can connect properly over other non-Comcast internet connections, we are only seeing the issue occur specifically on XFINITY service.  The ports they are using to connect are as follows:  

    udp/500 (ISAKMP)

    udp/4500 (IPSec nat-traversal)

    udp/10000 (IPSec over TCP)

I know these ports are not listed on the official "blocked ports" list, but we believe that something has changed on the Comcast network to possibly cause our issue, due to the fact that the problems started for all of us at the same time.  We have XFINITY customers in multiple states of the US experiencing this issue, so it is not localized to one specific market.  Any help is greatly appreciated.  Thanks!

i would like to know the speed of my internet, all it says on my bill is performance and the price why dosent it say the speed

I hope this is in the right sub-forum, excuse me if it's not.

I have tried going through with Cusotmer Service online and on the phone, and no one can figure this out.

I'm already positive this is a issue with noise on our line, but we can never get any technical help sent out. We have made appointments plently of times, they've only showed up once about 6 months ago to install new line and upgrade our boxes for TV and internet.

Before they showed up to upgrade us, we still have had this problem. Old modem couldn't handle the noise as good as the current one we have, so we thought it was gone with the new modem. (Modem we have is Technicolor TC8305C) But it seems when the weather out side gets warmer, we experience more dropped signal to the router and get a modem reboot.

We get about 10-20 reboots a day.

When we got techs out, they removed old coaxial box that was on the outside of the house and moved a new one into our backyard. Including a new cable that was run underground. The cable was very poorly burried and the techs said they would call someone to come burry the cable, the company/people they called snipped the cable and had to get a connector added one to finish the line to the outside box that handles the whole neighborhoods coaxial connections.

The box that handle the neighborhood has been left uncovered for months I'm sure, the top doesn't even stay on and blows off with heavy wind. I have no idea if this could be the problem, but I'm sure it is. Neighbor also has Comcast modem with the xfinitywifi hotspot feature, when my connection drops, so does her hotspot. So I figure it's affecting the whole neighborhood in some way.

I'm trying to figure out who to contact to fix this, online support does not help. Line appear fine on their end, but this is a weather sensitive (at least I think it is) and completely random problem.

Here is a log from today:

System Logs:Today pg1

Time                      Priority         Description

Mon Jun 08 14:40:29 2015  Notice (6)       TLV-11 - unrecognized OID;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 14:39:03 2015  Critical (3)     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 14:37:47 2015  Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 14:37:34 2015  Critical (3)     Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 14:37:33 2015  Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 14:37:16 2015  Critical (3)     Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 14:37:15 2015  Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 14:07:41 2015  Notice (6)       TLV-11 - unrecognized OID;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 14:06:13 2015  Critical (3)     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Mon Jun 08 14:06:03 2015  Critical (3)     No Ranging Response received - T3 time-out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.0;CM-VER=3.0;

Mon Jun 08 14:05:23 2015  Critical (3)     Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.0;CM-VER=3.0;

Mon Jun 08 14:05:04 2015  Critical (3)     No Ranging Response received - T3 time-out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.0;CM-VER=3.0;

Mon Jun 08 14:04:20 2015  Critical (3)     Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.0;CM-VER=3.0;

Mon Jun 08 14:03:57 2015  Critical (3)     No Ranging Response received - T3 time-out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.0;CM-VER=3.0;

Mon Jun 08 14:03:05 2015  Critical (3)     Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.0;CM-VER=3.0;

Mon Jun 08 14:02:46 2015  Critical (3)     No Ranging Response received - T3 time-out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.0;CM-VER=3.0;

Mon Jun 08 14:02:30 2015  Critical (3)     Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.0;CM-VER=3.0;

Mon Jun 08 14:02:22 2015  Critical (3)     No Ranging Response received - T3 time-out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.0;CM-VER=3.0;

Mon Jun 08 14:00:54 2015  Critical (3)     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 13:58:44 2015  Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 13:58:33 2015  Critical (3)     Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 13:58:33 2015  Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 13:44:23 2015  Warning (5)      DBC-REQ denied - confirmation code 210: reject-dynamic-range-windowviolation;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 13:44:23 2015  Warning (5)      Dynamic Range Window violation

Mon Jun 08 13:43:12 2015  Notice (6)       TLV-11 - unrecognized OID;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

System Logs:Today pg2

Time                      Priority         Description

Mon Jun 08 13:31:18 2015  Critical (3)     Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.0;CM-VER=3.0;

Mon Jun 08 13:31:10 2015  Critical (3)     No Ranging Response received - T3 time-out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.0;CM-VER=3.0;

Mon Jun 08 13:30:40 2015  Critical (3)     Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.0;CM-VER=3.0;

Mon Jun 08 13:30:23 2015  Critical (3)     No Ranging Response received - T3 time-out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.0;CM-VER=3.0;

Mon Jun 08 13:30:05 2015  Critical (3)     Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.0;CM-VER=3.0;

Mon Jun 08 13:29:44 2015  Critical (3)     No Ranging Response received - T3 time-out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.0;CM-VER=3.0;

Mon Jun 08 13:29:24 2015  Critical (3)     Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.0;CM-VER=3.0;

Mon Jun 08 13:29:13 2015  Critical (3)     No Ranging Response received - T3 time-out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.0;CM-VER=3.0;

Mon Jun 08 13:28:17 2015  Critical (3)     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 13:26:07 2015  Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 13:25:57 2015  Critical (3)     Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 13:25:56 2015  Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 13:08:01 2015  Notice (6)       TLV-11 - unrecognized OID;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 13:07:49 2015  Notice (6)       Honoring MDD; IP provisioning mode = IPv6

Mon Jun 08 13:07:27 2015  Critical (3)     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 13:05:17 2015  Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 13:05:06 2015  Critical (3)     Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 13:05:05 2015  Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 13:04:37 2015  Critical (3)     Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 12:55:27 2015  Notice (6)       TLV-11 - unrecognized OID;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 12:53:52 2015  Notice (6)       Honoring MDD; IP provisioning mode = IPv6

Mon Jun 08 12:53:41 2015  Notice (6)       WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE

Mon Jun 08 12:53:34 2015  Critical (3)     Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.0;CM-VER=3.0;

Mon Jun 08 12:53:22 2015  Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.0;CM-VER=3.0;

Mon Jun 08 12:53:15 2015  Critical (3)     No Ranging Response received - T3 time-out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.0;CM-VER=3.0;

System Logs:Today pg3

Time                      Priority         Description

Mon Jun 08 12:52:44 2015  Notice (6)       WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE

Mon Jun 08 12:52:35 2015  Critical (3)     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 12:50:25 2015  Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 12:50:15 2015  Critical (3)     Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 12:50:15 2015  Warning (5)      Dynamic Range Window violation

Mon Jun 08 12:50:14 2015  Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 12:46:33 2015  Notice (6)       TLV-11 - unrecognized OID;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 12:46:13 2015  Notice (6)       Honoring MDD; IP provisioning mode = IPv6

Mon Jun 08 12:45:56 2015  Critical (3)     Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.0;CM-VER=3.0;

Mon Jun 08 12:45:50 2015  Critical (3)     No Ranging Response received - T3 time-out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.0;CM-VER=3.0;

Mon Jun 08 12:45:10 2015  Critical (3)     Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.0;CM-VER=3.0;

Mon Jun 08 12:45:02 2015  Critical (3)     No Ranging Response received - T3 time-out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.0;CM-VER=3.0;

Mon Jun 08 12:44:30 2015  Critical (3)     Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.0;CM-VER=3.0;

Mon Jun 08 12:42:52 2015  Critical (3)     No Ranging Response received - T3 time-out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.0;CM-VER=3.0;

Mon Jun 08 12:42:16 2015  Critical (3)     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 12:40:06 2015  Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

Mon Jun 08 12:39:55 2015  Critical (3)     Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:32:c8:25:1b:35;CMTS-MAC=6c:41:6a:f2:df:64;CM-QOS=1.1;CM-VER=3.0;

The internet has been slow for several days. I have cycled the modem and router and restarted many times. I tried having the automated system send a reset signal and the lights never go off. I called customer service and they said it needs to be escalated.

Download speed is only 0.2 Mb, it's like being on dial up.

I think I've done everything in testing. Restarted my computer, router, and modem multiple times. Tried connecting directly without my router. I've done many ping tests and am finding significant packet loss when pinging every site. I ran ping tests internally to each device including pinging my modem, and had no loss. The next thing in line to ping was the first comcast node that I see listed as the first IP of every traceroute. I get packet loss when pinging that node, which accurately matches packet loss on everything else I ping.

This started saturday afternoon and continued through sunday. Since comcast's site showed me a status error including essentially "it's not you, it's us" I gave up the day and waited it out. It was fine earlier today but as of two hours ago, it's still the same packet loss problem.

The failing happens at c-24-8-64-1.hsd1.co.comcast.net

EDIT: seems to be over for now, but dealing with packet loss across 3 days is quite a problem

I cannot resolve any sites in the .pci.gov domain.  Looking at other forum posts, it looks like we need a "negative trust anchor" for the pci.gov domain until the administrators of pci.gov fix their DNSSEC issues.

I have the same issue, but have no idea where you got those numbers and such. It goes out every day about ten times, for about a minute or two. I am not very tech savvy, so I have no clue about what to do or where to look.It does not affect television at all.

Help!!  Does anyone else have this issue.....My internet connection drops at least one time per day.  I have to unplug everything and wait a minute then start over.  It is so frustrating and when I called Comcast I got a lady that I could hardly understand a word she said.

Not expecting much from Comcast I guess just venting

Yes, I have a business. Everyday for two weeks, it shuts down several times a day. 

I have called Comcast several times, they are of no help at all. My credit card machines goes down too. No one seems to be able to help. So frustrated.

For some reason, using Xfinity internet I'm not able to get to http://www.onecalendar.nl

Name lookup seems to be working.   I've tried Chrome, IE and Firefox, from different machines, and also from my android phone using android chrome.   The connection always times out. 

If I use my Verizon cell phone internet, it works fine.  It looks like level 3 might be having issues in NL routing the packets to the destination, but not sure.  An ideas?

I ran a tracert, and came up with this:

 3     8 ms     8 ms     9 ms  xe-9-0-1-0-sur03.englewood.co.denver.comcast.ne
[68.85.221.185]
 4    50 ms     9 ms    16 ms  ae-10-0-sur02.englewood.co.denver.comcast.net [
.86.104.122]
 5    18 ms     9 ms    13 ms  ae-27-0-ar01.aurora.co.denver.comcast.net [68.8
128.9]
 6    10 ms    12 ms    12 ms  he-0-5-0-7-cr02.denver.co.ibone.comcast.net [68
6.93.149]
 7    10 ms    10 ms     9 ms  ae14.edge3.denver1.level3.net [4.68.127.129]
 8   130 ms   136 ms   129 ms  ae-238-3614.edge6.amsterdam1.level3.net [4.69.1
.246]
 9   143 ms   146 ms   142 ms  fiberring-b.edge6.amsterdam1.level3.net [213.19
95.106]
10     *        *        *     Request timed out.
11     *        *        *     Request timed out.
12   147 ms   146 ms   147 ms  85.17.3.81
13     *        *        *     Request timed out.
14     *        *        *     Request timed out.
15     *        *        *     Request timed out.
16     *        *        *     Request timed out.
17     *        *        *     Request timed out.
18     *        *        *     Request timed out.
19     *        *        *     Request timed out.
20     *        *        *     Request timed out.
21     *        *        *     Request timed out.
22     *        *        *     Request timed out.
23     *        *        *     Request timed out.
24     *        *        *     Request timed out.
25     *        *        *     Request timed out.
26     *        *        *     Request timed out.
27     *        *        *     Request timed out.
28     *        *        *     Request timed out.
29     *        *        *     Request timed out.
30     *        *        *     Request timed out.

My upload speed used to be around 11mpbs but now stays at 6 and lower. Meanwhile download speed maintains at above 50mpbs. I have reset both the modem (motorola sb6121) and router but no luck. Technical support is suck. It is helpless here.