Timeout on Verizon nodes *.PHLAPA-LCR-21.verizon-gni.net PLEASE FIX!!!!
josh123451
Newbie

This has been going on for ages. I try to go to a website, and it sits at "Looking up (whatever.com)..." for ages. When I run a tracert on the website, it's always the same...

1     1 ms     1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
2     9 ms     4 ms     5 ms  L100.PHLAPA-VFTTP-107.verizon-gni.net [masked]
3    18 ms    15 ms    15 ms  G0-9-3-7.PHLAPA-LCR-21.verizon-gni.net [130.81.137.154]
4     *        *        *     Request timed out.
5     *        *        *     Request timed out.
6    18 ms    14 ms    19 ms  0.et-9-1-0.GW13.IAD8.ALTER.NET [140.222.235.213]
7    17 ms    21 ms    16 ms  neustar-gw.customer.alter.net [152.179.50.58]

And on until it gets to the site. There is ALWAYS A timeout and delay on hop 3, which is always a server at PHLAPA-LCR-21.verizon-gni.net. The actual node name and IP address can vary, a few I have seen are

G0-9-3-7.PHLAPA-LCR-21.verizon-gni.net [130.81.137.154]

G103-0-0-4.PHLAPA-LCR-21.verizon-gni.net [100.41.14.216]

G102-0-0-31.PHLAPA-LCR-21.verizon-gni.net [100.41.213.156]

I try calling Verizon support but they are useless, insisting the problem is on my side, but one a packet leaves that first hop away from my routers, it's 100% verizons network. At this point my wait time toload a web page are so long it'soverall slower than dial up speeds, and I'm paying a lot morethan dial up costs.

Does anyone knowhow to get a network tech on the phone at Verizon who can actully fix this?

0 Likes
Re: Timeout on Verizon nodes *.PHLAPA-LCR-21.verizon-gni.net PLEASE FIX!!!!
lasagna
Community Leader
Community Leader

Your analysis is incorrect.  This is not necessarily an error or problem, but can simply be by intended operation.   The choice of whether a router will issue a TTL time exceeded ICMP packet which traceroute uses to perform hop-based measurements is purely a configuration choice (traceroute uses ever increasing TTL hop count values to map each successive hop along a route path).  It's possible that these hops may be a multi-hop cloud (such as an MPLS path) or a traffic inspection device (such as a firewall, IPS, or similar protective device) which typically do not respond with time exceeded ICMP packets.   It is very unlikely that Vz will change that configuration to make your traceroute look pretty.

Your interpretation of the lack of response from these two nodes as the source of your issues is also incorrect ... that is proven out by the simple fact that once you start hitting node 6 in your path and find a device that provides the ICMP timeout responses, you see 18/14/19ms responses and then consistently thereafter.   These are insignificantly different than the response time immediately before you hit the two Vz routers you're citing and thus not the source of latency or throughput issues.

If you're upset about the amount of time it's taking to resolve these, then use the "-w" option on Microsoft's traceroute to set a maximum number of milliseconds to wait -- say 50ms, and use the "-d" option to turn off name resolution (-w and -n on linux).  

If you truly want to measure throughput, try using ping to various IP addresses along the path using the "-l" (Microsoft) option to set a buffer size in the packet up to 65535 bytes and see if you pick up substantial latency or throughput issues at some point along the line.

Absent any of that, I'd start looking locally first.  If the performance is consistent across all websites, you may have a issue at your end (firewall, proxy included with antivirus that's gone awry, etc.).  And best ... a completely different machine (say a friends laptop) to see if it experiences the same issues.

The numbers in your traceroute certainly don't indicate that there's any issue.

Re: Timeout on Verizon nodes *.PHLAPA-LCR-21.verizon-gni.net PLEASE FIX!!!!
josh123451
Newbie

> Your analysis is incorrect.

No it's not.

>  This is not necessarily an error or problem, but can simply be by intended operation.

If the "intended operation" is to timeout a node on your netowrk every time a customer gets to it, that is an error. Period.

> The choice of whether a router will issue a TTL time exceeded ICMP packet which traceroute uses to perform hop-based measurements is purely a configuration choice

Which has nothing to do with anything. It's timing out within the parameters set, which is WAY to long for what I am paying for.

> These are insignificantly different than the response time immediately before you hit the two Vz routers you're citing and thus not the source of latency or throughput issues.

You are 100% incorrect. Conststent response times before a node, and after a node, and a timeout on the node, indicates a problem WITH THAT NODE.

> Absent any of that, I'd start looking locally first.

And again, the default Verizon answer "it must be you". It's not. The tracert CLEARLY shows the issue is on Verizons side. You want to know how I 100% know you are wrong? Because previously that same node stopped ALL traffic going to it, causing an outage. An outage Verizon acknowledged, and "fixed" by making it go back to timing out, and not becoming a black hole. So you are demonstrably wrong. If you don't know something, don't blame the user.

Verizon needs to fix the node correctly. It is absolutely inexcusable to have slower than dialup speeds for the price they pay.

> The numbers in your traceroute certainly don't indicate that there's any issue.

Yes, they absoltuely do.

So does anyone know how to get in touch with a Verzon network engineer to fix this?

0 Likes
Re: Timeout on Verizon nodes *.PHLAPA-LCR-21.verizon-gni.net PLEASE FIX!!!!
jonjones1
Legend

I just did a whois which has a support email and phone number.

additionally this link may help you better understand the process.

the main factor is you said it times out at certain hops. Is this for every site you try to reach? Did you try to tracert to Google or Amazon or Yahoo or another site that is well known? Apple, Microsoft etc. see if that still occurs.

Good Luck

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/public/whoisinaccuracy/index.xhtml
#


#
# The following results may also be obtained via:
# https://whois.arin.net/rest/nets;q=130.81.137.154?showDetails=true&showARIN=false&showNonArinTopLeve...
#

NetRange: 130.81.0.0 - 130.81.255.255
CIDR: 130.81.0.0/16
NetName: VZGNI-PUB-7
NetHandle: NET-130-81-0-0-1
Parent: NET130 (NET-130-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: MCI Communications Services, Inc. d/b/a Verizon Business (MCICS)
RegDate: 1988-06-29
Updated: 2016-05-17
Ref: https://whois.arin.net/rest/net/NET-130-81-0-0-1

OrgName: MCI Communications Services, Inc. d/b/a Verizon Business
OrgId: MCICS
Address: 22001 Loudoun County Pkwy
City: Ashburn
StateProv: VA
PostalCode: 20147
Country: US
RegDate: 2006-05-30
Updated: 2017-01-28
Ref: https://whois.arin.net/rest/org/MCICS


OrgAbuseHandle: ABUSE3-ARIN
OrgAbuseName: abuse
OrgAbusePhone: +1-800-900-0241
OrgAbuseEmail: email@verizonbusiness.com
OrgAbuseRef: https://whois.arin.net/rest/poc/ABUSE3-ARIN

OrgTechHandle: SWIPP-ARIN
OrgTechName: swipper
OrgTechPhone: +1-800-900-0241
OrgTechEmail: email@verizonbusiness.com
OrgTechRef: https://whois.arin.net/rest/poc/SWIPP-ARIN

OrgNOCHandle: OA12-ARIN
OrgNOCName: UUnet Technologies, Inc., Technologies
OrgNOCPhone: +1-800-900-0241
OrgNOCEmail: email@verizonbusiness.com
OrgNOCRef: https://whois.arin.net/rest/poc/OA12-ARIN

OrgTechHandle: SWIPP9-ARIN
OrgTechName: SWIPPER
OrgTechPhone: +1-800-900-0241
OrgTechEmail: email@verizon.com
OrgTechRef: https://whois.arin.net/rest/poc/SWIPP9-ARIN


#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/public/whoisinaccuracy/index.xhtml
#

0 Likes
Re: Timeout on Verizon nodes *.PHLAPA-LCR-21.verizon-gni.net PLEASE FIX!!!!
lasagna
Community Leader
Community Leader

Failing to understand of how traceroute works, what it shows you, and more importantly what it doesn't show isn't going to result in fixing your problem.  Dropping low or expired TTL packets (ICMP or otherwise) is a common practice on busy routers and security boundary devices and it's as simple as that.  I would venture that just about everyone's traceroute path on FiOS drops about 2 or 3 hops out.

I don't doubt you have performance problems, but you're looking under the wrong rock.    Others have suggested that you can sometimes find Vz engineers monitoring the Verizon FiOS channel on DSL Reports.   I suggest you try there.

0 Likes
Re: Timeout on Verizon nodes *.PHLAPA-LCR-21.verizon-gni.net PLEASE FIX!!!!
josh123451
Newbie

> Others have suggested that you can sometimes find Vz engineers monitoring the Verizon FiOS channel on DSL Reports.

Multiple people on the DSL reports forum have allreported the exact same issue I am having, which once again proves this is on the Verizon side. O ce when this node turned into a black hole and was actually dropping packets, someone actually noticed and fixed it, but they just fixed it to it's former (and current) state, which is unacceptable

It doesn't happen on every site. It varies based on which path through the Verizon network the request goes through. I can ever flip it, if I reboot my router, and get a new IP address, some sites that were not effected will be, and other sites that were effected will skip that hop. Apparently Verizon is assigning that node to a portion of it's user base as determined by IP.

I checked the WHOIS and all it gives back is Verizon support emails, which just go back to the "Our network is infallible it's all your fault" nonsense. I'm trying to find a phone number or email that will get the attention of the appropriate network support team who can actually fix the problem

0 Likes