Verizon FiOS → Can No Longer Reach A Website - Weird

I can no longer reach a website I have been using for YEARS and I can't understand why. I am a member of www.nikoncafe.com and have been posting on the forum for years with no issues. As of today (?) I can no longer reach the site. I do a tracert and it times out. I have no problem reaching any other sites. I had my nephew try the URL from his FiOS connection and he can reach the site.

My FiOS router was offline for 2.5 days due to a home electrical outage, but it was up and running once the power was restored. My FiOS IP address changed because I was offline so long, but the new IP address isn't causing any issues. Is it possible the website is blocking my new IP address? BTW, I've tried different browsers and another PC on my home network with the same result. Any ideas?

What is the fastest way to get a new FiOS IP? Very strange. Any help is appreciated.

TIA...JL

I can get there...

Works fine from my connection. Probably the site was down.

No problems here either.

To release your IP address lease see »Verizon FiOS FAQ »How do I release my DHCP lease? Why would I need to?

Thanks everyone. I am going to release my current FiOS IP and get a new one. Hopefully this will resolve the issue. I'll give you an update later.

Regards...JL

I ran this tracert to www.nikoncafe.com and it crapped out after the 10th hop. Can someone please run a trace and post the results for me. I want to see what is beyond the 10th hop.

10 38 ms 33 ms 35 ms ae-101-3501.edge2.Chicago2.Level3.net [4.69.158.1]
11 * * * Request timed out.
12 * * * Request timed out.
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.

Trace complete.

TIA....JL

This is from VA Beach:

 1  wireless_broadband_router (192.168.1.1)  6.663 ms  4.175 ms  3.872 ms
 2  l100.nrflva-vfttp-28.verizon-gni.net (173.71.147.1)  12.759 ms  12.148 ms  11.851 ms
 3  g0-3-4-7.nrflva-lcr-22.verizon-gni.net (130.81.191.70)  12.277 ms  14.865 ms  12.426 ms
 4  xe-0-1-8-0.phil-bb-rtr2.verizon-gni.net (130.81.209.48)  19.992 ms  22.535 ms  25.234 ms
 5  0.xe-7-3-0.br1.iad8.alter.net (152.63.3.125)  30.732 ms  28.285 ms  29.901 ms
 6  te7-4-10g.ar3.dca3.gblx.net (64.212.107.157)  30.009 ms  29.764 ms  29.906 ms
 7  giglinx.tengigabitethernet3-1.ar5.chi2.gblx.net (208.49.135.162)  56.420 ms  59.427 ms  58.127 ms
 8  lw-dc2-core3-te9-1.rtr.liquidweb.com (209.59.157.224)  64.636 ms  66.335 ms  64.892 ms
 9  lw-dc2-sec2-dist3-po1.rtr.liquidweb.com (209.59.157.222)  65.177 ms  63.499 ms  64.634 ms
10  nikoncafe.com (67.225.138.55)  65.438 ms  65.435 ms  64.995 ms
 

From your trace, I'd say this is a problem with the hop between Level3 and liquidweb.com

Thanks for taking the time to post your trace.

Regards...JL

From Harrisburg, PA suburbs:

traceroute to www.nikoncafe.com (67.225.138.55), 30 hops max, 38 byte packets
 1  L100.HRBGPA-VFTTP-12.verizon-gni.net (98.117.0.1)  1.610 ms  1.381 ms  1.542 ms
 2  G9-0-4-112.HRBGPA-LCR-01.verizon-gni.net (130.81.137.120)  4.081 ms  3.690 ms  3.816 ms
 3  P12-0-0.HRBGPA-LCR-02.verizon-gni.net (130.81.27.185)  16.285 ms  16.194 ms  16.245 ms
 4  so-12-1-0-0.RES-BB-RTR1.verizon-gni.net (130.81.28.254)  15.842 ms  16.123 ms  15.872 ms
 5  0.xe-1-1-1.BR2.IAD8.ALTER.NET (152.63.7.225)  13.897 ms  13.998 ms  14.071 ms
 6  te4-4-10G.ar6.DCA3.gblx.net (208.178.58.121)  23.842 ms  64.212.107.57 (64.212.107.57)  14.167 ms  14.202 ms
 7  GIGLINX.TenGigabitEthernet3-1.ar5.CHI2.gblx.net (208.49.135.162)  42.062 ms  42.100 ms  42.055 ms
 8  lw-dc2-core3-te9-1.rtr.liquidweb.com (209.59.157.224)  144.480 ms  50.112 ms  50.202 ms
 9  lw-dc2-sec2-dist3-po1.rtr.liquidweb.com (209.59.157.222)  49.494 ms  49.381 ms  49.392 ms
10  nikoncafe.com (67.225.138.55)  46.620 ms  46.636 ms  46.447 ms
 

You might want to post your full trace as opposed to just step 10, especially so you capture the IP to make sure its resolving to the same place.

Have you tried just typing in the sites IP into the url bar?

Thanks for your suggestions.

At this point I've determined it is either related to my FiOS IP address or my Nikoncafe account. It isn't a DNS issue because it resolves the URL when I ping it. I still cannot connect when I use the site's IP address.

I will be be out of the house for a few hours later today and will power off the Actiontec router before I leave. Hopefully my current IP address will expire and I will get a new one. I tried to release it through the router's utilities, but it keeps renewing the current address.

I will also try to access the site from another location and see what happens.

Thanks again....JL

I have no issue either and as a Nikon user I visit that site every day.
Hopefully you can get this issue resolved. I think that the best Nikon forum.

gugarci,
I tend to visit Nikoncafe on a daily basis and I'm annoyed I can't access it now. My handle is SRFast on the forums.

I have determined my problem is NOT related to my Nikoncafe account. I tried to load the site using the "InPrivate Browsing" feature and I still couldn't connect. Even if my account was hosed, using "InPrivate" would have loaded the site's home/login page. At this point, all the evidence points to an issue with the FiOS IP.

Regards....JL

I turned otf my Actiontec router at 11:15 hours to allow the IP address to expire. I powered it back on at 21:15 and got a new FiOS IP address and now I can access all my usual websites. I don't know why the IP I got on Thursday was bad, but it is history now. Thanks to all who offered advice.

Regards....JL

You didn't happen to write down what your WAN IP address was when you weren't connecting, did you? Might be useful to know. Just the first two octets.

Could someone with your Ip have been banned prior at the IP level?

I don't remember the exact IP address, but it was 108.nnn.nnn.106.

It was a very strange situation and all I know is that after being issued a new FiOS IP address, everything was back to normal.

Regards...JL

I have a problem with capitalone website it sometimes loads and sometimes doesn't , @ the guy who change his IP you think it would work if I left for like 5-10 min off?

I doubt that a 5-10 minute power down will expire your IP address. I recommend you power off the router before going to bed and power it back up in the morning. There is a way to release the IP via the Actiontec menus, but I couldn't get it to work. Here's a YouTube video on how to do it:
www.youtube.com/watch?v=8co-YCzh2zw

Good luck...JL

He wasn't getting beyond a level3 router. Had he been IP banned, he would have at least made it through to Nikoncafe's webhost, LiquidWeb. Bans very rarely prevent viewing a website anyways, it would only have prevented logging in and posting anything.

Looks like it was a routing issue to me.

Lol wow it worked! It doesn't show Verizon Internet anymore and it shows Verizon Fios

I did release/renew unplugged actiontec for 30 seconds , plug back in WORKED!

and my upload is fixed!! I get more then 33 mbps of upload wooot

I run a couple forums and host a few more
Most likely thing is your PC or your account got sideways with either the admins or the server itself

My server will autoblock IPs that attempt questionable behavior. Usually its for a short time then resets. But if you or your PC persist you can get banned permanently
If that happens the entire server disappears to you ... nothing

Nothing wrong with my PC or account. I was able to connect to the site and access my account from another location (different IP). I could not connect to this website from ANY of the PCs on my home network. The connection problem was resolved when I got a new IP address.

Regards....JL

like I said - Its likely your IP was banned by the server - the owner of the site might not even know.....