Connection problem to certain websites

[Khamsin]

Every day, usually during the same times, my connection to a particular website goes down. However, when I access it from my phone's 3G, it loads up just fine with no hint of slowdown.

The computer that I can't connect from has no issues connecting to any other website, however.

Any ideas on why a given website won't let you connect from one ISP (in this case, Comcast) but has no problem with ATT 3G? And only during certain times? I can connect just fine during any other time of day from my computer. And I've tried dns flushes and using just the IP. Also, my phone can't connect either if it's on wifi, it has to be on 3G to connect.

[Yabby]

Have you tried using a tracert to see where the problem starts?

[Khamsin]

Here's a couple tracerts done one right after the other:

Tracing route to static-72-66-123-21.washdc.fios.verizon.net [72.66.123.21]
over a maximum of 30 hops:

  1    12 ms    11 ms    15 ms  73.105.140.1
  2    14 ms    13 ms    13 ms  ge-3-3-ur01.bellevue.wa.seattle.comcast.net [68.85.144.225]
  3    34 ms    16 ms    13 ms  be-50-ar01.burien.wa.seattle.comcast.net [68.86.96.213]
  4    13 ms    14 ms    13 ms  be-0-0-ar03.burien.wa.seattle.comcast.net [68.86.177.130]
  5    21 ms    32 ms    22 ms  pos-0-1-0-0-cr01.portland.or.ibone.comcast.net [68.86.93.109]
  6    18 ms    14 ms    20 ms  pos-1-8-0-0-cr01.seattle.wa.ibone.comcast.net [68.86.85.205]
  7    18 ms    16 ms    21 ms  pos-0-1-0-0-pe01.seattle.wa.ibone.comcast.net [68.86.85.38]
  8    32 ms    22 ms    40 ms  if-4-0-0.core2.S00-Seattle.as6453.net [66.110.64.1]
  9   132 ms   281 ms    45 ms  if-15-0-0.mcore4.PDI-PaloAlto.as6453.net [207.45.196.65]
 10    48 ms    45 ms    37 ms  if-13-0-0-1281.core4.SQN-SanJose.as6453.net [216.6.30.61]
 11     *        *      111 ms  Vlan1280.icore1.SQN-SanJose.as6453.net [216.6.30.26]
 12     *       42 ms    41 ms  0.xe-4-1-0.BR3.SJC7.ALTER.NET [204.255.168.177]
 13    42 ms    47 ms    59 ms  0.ge-2-0-0.SJC01-BB-RTR2.verizon-gni.net [152.63.2.46]
 14   119 ms   121 ms   119 ms  P15-0.WASHDC-LCR-05.verizon-gni.net [130.81.28.145]
 15   124 ms   126 ms   127 ms  P15-0.WASHDC-LCR-07.verizon-gni.net [130.81.27.33]
 16   123 ms   124 ms     *     P0-12-2-0.WASHDC-LCR-21.verizon-gni.net [130.81.27.83]
 17     *        *        *     Request timed out.
 18     *        *      135 ms  static-72-66-123-21.washdc.fios.verizon.net [72.66.123.21]

Trace complete.

Tracing route to static-72-66-123-21.washdc.fios.verizon.net [72.66.123.21]
over a maximum of 30 hops:

  1    17 ms    12 ms    24 ms  73.105.140.1
  2    15 ms    14 ms    38 ms  ge-3-3-ur01.bellevue.wa.seattle.comcast.net [68.85.144.225]
  3    16 ms    12 ms    14 ms  be-50-ar01.burien.wa.seattle.comcast.net [68.86.96.213]
  4    25 ms    25 ms    19 ms  be-0-0-ar03.burien.wa.seattle.comcast.net [68.86.177.130]
  5    15 ms    20 ms    18 ms  pos-0-2-0-0-cr01.portland.or.ibone.comcast.net [68.86.93.117]
  6    22 ms    25 ms    24 ms  pos-1-8-0-0-cr01.seattle.wa.ibone.comcast.net [68.86.85.205]
  7    17 ms    18 ms    16 ms  pos-0-1-0-0-pe01.seattle.wa.ibone.comcast.net [68.86.85.38]
  8    24 ms    33 ms    14 ms  if-4-0-0.core2.S00-Seattle.as6453.net [66.110.64.1]
  9    38 ms    39 ms    49 ms  if-15-0-0.mcore4.PDI-PaloAlto.as6453.net [207.45.196.65]
 10    39 ms    41 ms    37 ms  if-13-0-0-1281.core4.SQN-SanJose.as6453.net [216.6.30.61]
 11    52 ms    53 ms     *     Vlan1280.icore1.SQN-SanJose.as6453.net [216.6.30.26]
 12    41 ms    46 ms    58 ms  0.xe-4-1-0.BR3.SJC7.ALTER.NET [204.255.168.177]
 13    38 ms    42 ms    56 ms  0.ge-2-0-0.SJC01-BB-RTR2.verizon-gni.net [152.63.2.46]
 14   125 ms   125 ms   123 ms  P15-0.WASHDC-LCR-05.verizon-gni.net [130.81.28.145]
 15   131 ms   126 ms   124 ms  P15-0.WASHDC-LCR-07.verizon-gni.net [130.81.27.33]
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19   134 ms     *        *     static-72-66-123-21.washdc.fios.verizon.net [72.66.123.21]
 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   131 ms     *        *     static-72-66-123-21.washdc.fios.verizon.net [72.66.123.21]
 27   124 ms     *        *     static-72-66-123-21.washdc.fios.verizon.net [72.66.123.21]
 28     *        *        *     Request timed out.
 29   127 ms     *      132 ms  static-72-66-123-21.washdc.fios.verizon.net [72.66.123.21]

Trace complete.

This is on the computer on wifi that cannot connect to the website. On my phone, with 3G, however, the site loads up instantly. I wish I could do a tracert from my iphone or I would post that, too.

Thing that puzzles me is that it looks like it's on their end, yet my phone can connect just fine. So why does Verizon let my ATT 3G connect but not Comcast?

[Minions]

Donno if it's related, but I've been having similar problems connecting to amazon. No problem connecting from my phone however. I also have Comcast. This is just in the past couple days. I normally just open a tab that timed out on amazon and let it auto refresh till it appears after 5-10mins.

[Bloodfire]

What time are you attempting to connect to these websites on your PC?

I mean with cable internet it's not like you have a dedicated line for you only, unlike DSL.

Also, Wireless is very tricky, make sure you are not getting interference. Refer to this site for some info on that: http://lifehacker.com/5657613/why-is...w-can-i-fix-it

When a lot of people are using bandwidth within a particular area that area will slow down dramatically. Go to this website and test your Downstream and upstream speed: http://speakeasy.net/speedtest/

In general most residential PCs have a downstream of roughly 7-10 Mbps and an upstream of 1-4 Mbps depending on your internet plan.


I like to default to the process of elimination in 2 steps:

Step one - Software: IE, do your malware scans, update drivers through device manager, and other software maintenance to ensure it's not a software issue.

Step two - Hardware: Reset your router and modem, check connections etc.,etc.

The general idea is to unplug your router and modem then wait 30-60 sec the plug the modem first wait 30-60 sec then your router and wait 30-60 seconds.

generally if you have done the 2 step process and no dice, it's your ISP. I say this cause I have had similar problems, multiple random websites just don't go down inexplicably.

Also, I have heard around that comcast likes to reduce your bandwidth if they catch you doing "shady" things on their systems, IE torrents.

I hope this helps answer your issue.

[Khamsin]

What time are you attempting to connect to these websites on your PC?

I mean with cable internet it's not like you have a dedicated line for you only, unlike DSL.

When a lot of people are using bandwidth within a particular area that area will slow down dramatically. Go to this website and test your Downstream and upstream speed: http://speakeasy.net/speedtest/

In general most residential PCs have a downstream of roughly 7-10 Mbps and an upstream of 1-4 Mbps depending on your internet plan.


I like to default to the process of elimination in 2 steps:

Step one - Software: IE, do your malware scans, update drivers through device manager, and other software maintenance to ensure it's not a software issue.

Step two - Hardware: Reset your router and modem, check connections etc.,etc.

The general idea is to unplug your router and modem then wait 30-60 sec the plug the modem first wait 30-60 sec then your router and wait 30-60 seconds.

Also, I have heard around that comcast likes to reduce your bandwidth if they catch you doing "shady" things on their systems, IE torrents.

I hope this helps answer your issue.

Between 3pm and 8pm, which would be a popular time for everyone else to be on the internet, too. However, I notice no issues whatsoever with any other website other than this particular one. Not even a hint of slowdown anywhere else, but this single website is flat out unavailable. Yet I can connect to it with my phone on 3G.

As for software issues, I can't connect to the website with my computer or my phone if I'm on wifi, but if my phone is on 3G, I can connect. So I doubt it's a software issue.

As for router/modem resetting, I've done all that. It didn't help.

It's an isolated problem that happens with a particular website, everything else is fine. And while the tracert drops out when it reaches their end, suggesting it's a problem with the destination server or their ISP, that still doesn't explain how my phone can connect on 3G. I know for a fact the server I'm trying to connect to isn't down, it's just that I can't connect to it via Comcast between 3pm and 8pm, though any other website is just fine during that time. It also didn't use to be an issue until a week or two ago.

Only new thing I saw from Comcast during that time is their DNSSEC thing that just went on trial in my area, but I don't see how that could cause anything considering I didn't opt in.

[Bloodfire]

then I say it's the website not playing nice with your wireless network. Try a direct connect maybe?

[Minions]

then I say it's the website not playing nice with your wireless network. Try a direct connect maybe?

I'm directly connected, so that does not solve my issue. I swear Comcast just has issues with some websites randomly.