Child Item

Site Totals

61410 Questions Answered 270 Categories

Certain websites not accessible since Wednesday in multiple Fios households.

Since December 4th in the PM certain websites and servers aren't able to be accessed on Fios in the northern Philadelphia suburban region. I noticed on my home connection first and verified by going to a few other people's houses with Fios that it was a problem on Fios' end. I can connect on my Sprint data connection and on Comcast connections. The problem is on wired and wireless connections through the Fios Actiontech router. I've reset the router, reset the computers, flushed the DNS cache, changed to use Google's DNS servers on the router and the computers, etc. and repeated a bunch of times. Pinging the unconnectable sites always times out. Doing a trace route does the same after hop 3. I'm pretty sure at this point that it's nothing on my end. Fios users in other parts of the country are able to view the sites and connect to the servers fine. I changed nothing since the problem started. Below are my results for one of the sites with issues.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\wexxxx>ping heynowlife.org

Pinging heynowlife.org [46.17.103.120] with 32 bytes of data&colon;
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 46.17.103.120:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\wexxxx>tracert heynowlife.org

Tracing route to heynowlife.org [46.17.103.120]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 12 ms 6 ms L100.PHLAPA-VFTTP-100.verizon-gni.net [98.114.29
.1]
3 11 ms 10 ms 11 ms G0-6-0-0.PHLAPA-LCR-21.verizon-gni.net [130.81.1
37.140]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
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.

Comments

dslr595148

One of the many possbile answer(s) to what is going on..

1. Verizon assigns IP addresses dynamically. It's an automatic process, no one is manually handing out IPs.

2. The issue is not with the IP addresses that Verizon assigns, but with the blacklists not updating the IP addresses when they are changed. Verizon can't change third party sites' lists; it is up to the listing site to keep their filters updated

sisnerafa1

This happened with more than one site as well as not being able to connect to some programs' update servers at the same time. Don't think it's the sites' problem.

somegirl

I'm going to post Justin's reply from this thread, as it sounds like this might be a BOGON filter issue.

Short answer: Get a new IP address, and the issue will probably clear up.

@Justin wrote:
If you Google "bogon filter" you will find a Wikipedia article that talks about this problem, plus of course plenty of other links to articles, etc. Basically what has happened is that many "bad guys" have used IP addresses in the past for nefarious uses, so to protect themselves many websites use a "bogon filter" to block those addresses. But IP addresses that were once used for bad things in the past can be used for good ones now; as ISPs expand their networks they acquire blocks of IP addresses and start using them for legitimate purposes. But it is up to each website to manage their own bogon filters, and many don't keep them up to date very well.
For you, probably you recently got a new IP address (this happens regularly for people who do not pay for and have static IP addresses) and the new address was on a bogon filter list for those sites, and still is. The only way to get your current IP address removed from the list is to contact the websites, or just wait, eventually they will probably update their filter and then you will be able to access the sites.
Another option for you is to record your IP address right now, then turn off your router overnight, turn it on tomorrow and see what IP address you get. If it is on another block of IP addresses the odds are good that you will then be able to reach the sites just fine.
Oh, and I too can get to those websites just fine, I am also a FiOS user.
Hope this helps.
__________________________________
Justin
FiOS TV, 25/25 Internet, and Digital Voice user
QIP7232, QIP7100-P2, IMG 1.9
Keller, TX 76248

sisnerafa1

I did this today while at work and it didn't help. I can try it again over night, but I have a feeling it won't work still because the same sites are not working at another house with Fios about 5 miles away. Any other possibilities? I still think it's on Verizon's end since I don't seem to get past their regional servers when I do trace route.

smith6612

Considering the trace fails at a Verizon hop, Verizon will need to check their network. Bad routing table, bad link, bad upstream peering, or bad return path causing problems.

Child Item