unable to access certain websites

[mg234]

for the past week or so I've been unable to access a number of websites. they're timing out halfway through the connection. other sites hosted by the same companies work fine. looking through the archives i found a similar issue from a year ago in MD. I'm in MA. a group ticket was opened for that MD issue and the problem ultimately was resolved, although i'm not sure what the problem or the solution were.

traceroutes are below.

traceroute to twitpic.com (174.36.58.233), 64 hops max, 52 byte packets
 1  wireless_broadband_router (192.168.1.1)  2.902 ms  1.878 ms  1.433 ms
 2  l100.bstnma-vfttp-144.verizon-gni.net (71.184.194.1)  9.141 ms  23.041 ms  7.338 ms
 3  g14-0-7-1644.bstnma-lcr-06.verizon-gni.net (130.81.49.82)  8.115 ms  8.843 ms  7.066 ms
 4  so-7-2-0-0.bos-bb-rtr2.verizon-gni.net (130.81.29.174)  7.642 ms  8.831 ms  10.219 ms
 5  0.so-0-2-0.xl4.bos4.alter.net (152.63.16.141)  20.263 ms  18.529 ms  19.981 ms
 6  0.so-4-1-0.xl4.dfw7.alter.net (152.63.103.58)  61.535 ms  61.975 ms  60.011 ms
 7  tengige0-7-0-0.gw4.dfw13.alter.net (152.63.101.9)  67.275 ms *  65.177 ms
 8  * * *
 9  * * *
10  * * *
11  * * *
12  po1.fcr04.sr05.dal01.networklayer.com (66.228.118.214)  64.798 ms  81.764 ms  92.380 ms
13  174.36.58.233-static.reverse.softlayer.com (174.36.58.233)  64.785 ms  70.376 ms  65.155 ms

traceroute to tumblr.com (174.120.238.130), 64 hops max, 52 byte packets
 1  wireless_broadband_router (192.168.1.1)  2.317 ms  1.148 ms  0.927 ms
 2  l100.bstnma-vfttp-144.verizon-gni.net (71.184.194.1)  8.967 ms  9.794 ms  22.609 ms
 3  g14-0-7-1544.bstnma-lcr-05.verizon-gni.net (130.81.49.80)  7.639 ms  10.893 ms  8.386 ms
 4  so-7-2-0-0.bos-bb-rtr1.verizon-gni.net (130.81.29.172)  15.036 ms  10.146 ms  7.169 ms
 5  * * *
 6  0.ae1.br2.nyc4.alter.net (152.63.18.37)  16.425 ms  15.997 ms  15.082 ms
 7  204.255.168.26 (204.255.168.26)  14.592 ms  19.407 ms  14.453 ms
 8  xe-1-1-0.cr1.lga5.us.above.net (64.125.26.161)  35.631 ms  16.836 ms  15.364 ms
 9  xe-2-2-0.cr1.dca2.us.above.net (64.125.26.97)  52.478 ms  54.231 ms  52.020 ms
10  xe-2-2-0.cr1.iah1.us.above.net (64.125.29.37)  60.437 ms  60.762 ms  60.101 ms
11  xe-1-2-0.cr1.dfw2.us.above.net (64.125.26.129)  59.777 ms  64.259 ms  60.330 ms
12  xe-1-1-0.er1.dfw2.us.above.net (64.125.26.210)  59.773 ms  62.499 ms  59.858 ms
13  * * *
14  te9-1.dsr01.dllstx3.networklayer.com (70.87.253.6)  60.315 ms * *
15  te3-1.dsr02.dllstx2.networklayer.com (70.87.255.130)  62.490 ms * *
16  te6-1.car12.dllstx6.networklayer.com (70.87.254.230)  63.498 ms
    te5-1.car12.dllstx6.networklayer.com (70.87.254.226)  60.873 ms  58.153 ms
17  82.ee.78ae.static.theplanet.com (174.120.238.130)  60.580 ms  58.942 ms  59.762 ms

traceroute to tweetgrid.com (174.143.233.65), 64 hops max, 52 byte packets
 1  wireless_broadband_router (192.168.1.1)  1.711 ms  0.909 ms  2.226 ms
 2  l100.bstnma-vfttp-144.verizon-gni.net (71.184.194.1)  8.547 ms  8.179 ms  8.963 ms
 3  g14-0-7-1644.bstnma-lcr-06.verizon-gni.net (130.81.49.82)  9.275 ms  10.212 ms  13.182 ms
 4  so-7-2-0-0.bos-bb-rtr2.verizon-gni.net (130.81.29.174)  11.268 ms  9.629 ms  9.012 ms
 5  0.so-0-2-0.xl4.bos4.alter.net (152.63.16.141)  18.944 ms  18.658 ms  18.453 ms
 6  0.xe-4-1-0.xl4.nyc4.alter.net (152.63.3.102)  18.879 ms  17.754 ms  17.349 ms
 7  gigabitethernet5-0-0.gw1.nyc4.alter.net (152.63.20.101)  17.818 ms  18.298 ms
    gigabitethernet7-0-0.gw1.nyc4.alter.net (152.63.20.53)  19.984 ms
 8  teliasonera-test.customer.alter.net (157.130.255.206)  18.123 ms  18.891 ms  18.311 ms
 9  nyk-bb1-link.telia.net (80.91.248.145)  22.293 ms  20.642 ms
    nyk-bb1-link.telia.net (80.91.248.149)  21.309 ms
10  * * *
11  rackspace-ic-127247-dls-bb1.c.telia.net (213.248.88.174)  64.094 ms  62.772 ms  64.733 ms
12  core7-edge3-vlan3307.dfw1.rackspace.net (174.143.123.114)  63.308 ms  61.301 ms  60.134 ms
13  aggr511a-1-core7.dfw1.rackspace.net (98.129.84.149)  59.766 ms  61.259 ms  59.765 ms
14  174-143-233-65.slicehost.net (174.143.233.65)  65.405 ms  63.891 ms  64.786 ms

[Anti-Phish1]

---

@mg234 wrote:

for the past week or so I've been unable to access a number of websites. they're timing out halfway through the connection.  

---

The traceroutes that you posted all reach their destination.

The hops that show "* * *" are routers that have been configured not to respond to ICMP ECHO packets.

That does not mean anything is wrong.

[mg234]

---

@Anti-Phish wrote:

The traceroutes that you posted all reach their destination.

The hops that show "* * *" are routers that have been configured not to respond to ICMP ECHO packets.

That does not mean anything is wrong.

---

I know the trace reaches the destination, but a browser still times out. I increased the timeout in the browser, but still can't connect.

The greater problem is the majority of sites are slow to load, since they're pulling content from some site that is unreachable. Browser will sit there saying it has loaded 30 of 32 items.

[#4]

Good to know I am not the only one experiencing this frustrating problem!!! I have tried to no avail to get into my banking website to pay bills and it will not load all the way, it'll just do 51 out of 52 items. Also, I cannot even get the server to connect to another website to check something for school either.

I am really not impressed with FiOS.

[Hubrisnxs]

are you able to access the sites using a proxy like https://www.megaproxy.com/freesurf/    ?

[#6]

No, I just tried it. This is what I got : (Now, to clarify my situation, the webpage will load 51/52 and the area where I am supposed to login does not show up. It's only on my computer/laptop/ipod. I've accessed it at two other people's houses.

SERVICE ERROR

 

AN ERROR HAS OCCURRED WHILE PROCESSING YOUR REQUEST:
(my bank's website url)

PLEASE NOTE THE ERROR DETAILS BELOW:

UNEXPECTED ERROR: THERE IS A PROBLEM WITH A SSL CERTIFICATE ON THE REMOTE SITE. FOR SECURITY REASONS, THIS CONNECTION IS NOT ALLOWED.

The SSL certificate error occured on both websites that i've been unable to access for the 4 days.

[cjacobs001]

this has nothing to do with verizon

[cjacobs001]

I meant FiOS.  Nothing to do with FiOS

[#9]

Ah, well, I've had other problems with my tv and phone connections previously with FiOS, thought it was safe to assume the internet would go too 🙂

Any help with the SSL certificate?

[cjacobs001]

if the problem is on the remote site, you may just have to wait.  Or turn off your need for SSL