Accessibility Resource Center Skip to main content
Get gifts fast with In-Store & Curbside Pickup or same-day delivery.

Routing / Latency issues

SOLVED
Reply
Highlighted
Contributor
Contributor
Posts: 2
Registered: ‎02-01-2013

Re: Routing / Latency issues

Message 61 of 77
(1,556 Views)

Does anyone here use Twitter? If what he says is true, I say a number of us should start spamming this thread over to @VerizonSupport. It's been almost a month with no signs of this issue being fixed, let alone Verizon even knowing about it beyond these community boards.

Highlighted
Nickel Contributor
Nickel Contributor
Posts: 28
Registered: ‎07-19-2012

Re: Routing / Latency issues

Message 62 of 77
(1,531 Views)

Situation is again horrible here tonight again.  SPeeds cut down to 12Mb/s however the latency and packet loss is so bad, I cannot do anything but comment on forums.  I have HAD it with this sub-par service.

 

Long Beach, CA 75/35 FIOS

Highlighted
Copper Contributor
Copper Contributor
Posts: 10
Registered: ‎01-29-2013

Re: Routing / Latency issues

Message 63 of 77
(1,519 Views)

I tweeted them a message tonight.  And will continue to do so every day until it is addressed.

Highlighted
Nickel Contributor
Nickel Contributor
Posts: 28
Registered: ‎07-19-2012

Re: Routing / Latency issues

Message 64 of 77
(1,509 Views)

I will do the same then!

Highlighted
Contributor
Contributor
Posts: 1
Registered: ‎02-08-2013

Re: Routing / Latency issues

Message 65 of 77
(1,446 Views)

I myself am having the same issues.  Tonight is particularly bad, as I cant even carry a basic voice chat conversation.

 

Here are some of my traces: 

 

traceroute to 173.2.198.87 (173.2.198.87), 30 hops max, 60 byte packets
1 10.58.1.1 (10.58.1.1) 1.493 ms 2.177 ms 2.835 ms
2 10.144.1.1 (10.144.1.1) 0.415 ms 0.428 ms 0.411 ms
3 Wireless_Broadband_Router.home (192.168.1.1) 2.142 ms 2.701 ms 4.812 ms
4 L100.NYCMNY-VFTTP-48.verizon-gni.net (71.167.106.1) 11.406 ms 11.358 ms 11.886 ms
5 G0-1-1-3.NYCMNY-LCR-22.verizon-gni.net (130.81.188.72) 13.924 ms 13.605 ms 13.582 ms
6 ae0-0.NY5030-BB-RTR1.verizon-gni.net (130.81.209.118) 34.274 ms * 20.606 ms
7 0.xe-3-3-0.BR2.NYC4.ALTER.NET (152.63.23.133) 95.534 ms 95.497 ms 95.499 ms
8 204.255.168.90 (204.255.168.90) 13.373 ms 13.368 ms 13.302 ms
9 cr1-te-0-7-3-0.newyork.savvis.net (204.70.224.254) 56.858 ms 56.864 ms 56.850 ms
10 msr1-tengig-0-0-0-0.NewYork.savvis.net (204.70.196.110) 19.184 ms 19.121 ms 21.417 ms
11 cr2-tengig-0-15-2-0.NewYork.savvis.net (204.70.196.113) 91.327 ms 96.139 ms 87.757 ms
12 208.175.101.66 (208.175.101.66) 37.672 ms 37.696 ms 46.210 ms
13 * * *
14 * * *
15 dstswr2-ge3-16.rh.stjmny.cv.net (167.206.39.134) 16.235 ms dstswr1-ge3-16.rh.stjmny.cv.net (167.206.39.130) 90.036 ms 89.664 ms
16 * * *

And a reverse trace from the far end: 

Tracing route to {edited for privacy}
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  HomePC [192.168.1.1]
  2     *        *        *     Request timed out.
  3     7 ms     5 ms     5 ms  67.59.238.133
  4     8 ms     8 ms     9 ms  rtr4-ge1-9.mhe.hcvlny.cv.net [167.206.39.133]
  5    11 ms     9 ms     9 ms  451be0b9.cst.lightpath.net [65.19.99.185]
  6     *        *        *     Request timed out.
  7    10 ms     9 ms     9 ms  xe-9-1-3.edge2.Newark1.Level3.net [4.30.130.237]
 
  8    11 ms     9 ms     9 ms  ae-31-51.ebr1.Newark1.Level3.net [4.69.156.30]
  9    11 ms    10 ms    10 ms  ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
 10     9 ms     9 ms     9 ms  ae-4-4.ebr1.NewYork2.Level3.net [4.69.141.18]
 11     *        *        *     Request timed out.
 12    20 ms     *       24 ms  po6-20G.ar6.NYC1.gblx.net [208.51.134.113]
 13    10 ms    12 ms    12 ms  0.ae11.BR2.NYC4.ALTER.NET [204.255.168.189]
 14     *       10 ms    12 ms  0.so-5-0-0.NY5030-BB-RTR2.ALTER.NET [152.63.10.4
6]
 15     *        *        *     Request timed out.
 16    25 ms     *       18 ms  pool-96-232-85-72.nycmny.fios.verizon.net
 
Trace complete.
 
Trace to a different destination:
 

trace silicon.typefrag.com
traceroute to silicon.typefrag.com (74.217.195.66), 30 hops max, 60 byte packets
1 10.58.1.1 (10.58.1.1) 7.625 ms 8.067 ms 8.635 ms
2 10.144.1.1 (10.144.1.1) 0.655 ms 0.674 ms 0.668 ms
3 Wireless_Broadband_Router.home (192.168.1.1) 2.331 ms 2.368 ms 2.350 ms
4 L100.NYCMNY-VFTTP-48.verizon-gni.net (71.167.106.1) 14.061 ms 9.365 ms 9.375 ms
5 G0-1-1-4.NYCMNY-LCR-21.verizon-gni.net (130.81.146.230) 18.201 ms 17.538 ms 20.217 ms
6 130.81.151.228 (130.81.151.228) 95.311 ms 93.620 ms 93.605 ms
7 * * *
8 204.255.168.90 (204.255.168.90) 52.169 ms 48.335 ms 50.653 ms
9 cr1-te-0-7-3-0.newyork.savvis.net (204.70.224.254) 50.066 ms 50.092 ms 50.085 ms
10 cr2-pos0-0-0-0.sanfrancisco.savvis.net (204.70.192.90) 98.690 ms 98.703 ms 98.695 ms
11 er2-xe-3-1-0.SanJoseEquinix.savvis.net (204.70.200.197) 152.797 ms 152.790 ms 152.759 ms
12 er1-te-1-3.SanJoseEquinix.savvis.net (204.70.198.141) 99.004 ms 206.28.98.69 (206.28.98.69) 117.008 ms 117.026 ms
13 208.175.172.10 (208.175.172.10) 139.097 ms 139.104 ms 139.086 ms
14 border1.te7-1-bbnet1.sfo002.pnap.net (63.251.63.1) 105.070 ms * border1.te8-1-bbnet2.sfo002.pnap.net (63.251.63.65) 120.573 ms
15 74.217.195.66 (74.217.195.66) 133.900 ms 103.103 ms 103.169 ms

 

This problem also seems to come and go.  I also have packet loss pinging some hops directly.  And one my trace from my desktop vs my unix machine, behind the same network.

 

Tracing route to silicon.typefrag.com [74.217.195.66]
over a maximum of 30 hops:

1 * * * Request timed out.
2 <1 ms <1 ms <1 ms 10.144.1.1
3 <1 ms <1 ms <1 ms 192.168.1.1
4 7 ms 9 ms 9 ms L100.NYCMNY-VFTTP-48.verizon-gni.net [71.167.106
.1]
5 11 ms 15 ms 14 ms G0-1-1-4.NYCMNY-LCR-21.verizon-gni.net [130.81.1
46.230]
6 35 ms 33 ms 18 ms 130.81.151.228
7 * * 114 ms 0.xe-3-2-0.BR2.NYC4.ALTER.NET [152.63.20.213]
8 49 ms 50 ms 51 ms 204.255.168.90
9 45 ms 48 ms 50 ms cr1-te-0-7-3-0.newyork.savvis.net [204.70.224.25
4]
10 101 ms 95 ms 96 ms cr2-pos0-0-0-0.sanfrancisco.savvis.net [204.70.1
92.90]
11 129 ms 93 ms 92 ms er2-xe-3-1-0.SanJoseEquinix.savvis.net [204.70.2
00.197]
12 102 ms 103 ms 100 ms er1-te-1-4.SanJoseEquinix.savvis.net [204.70.198
.145]
13 136 ms * 118 ms 208.175.172.10
14 97 ms 99 ms 116 ms border1.te7-1-bbnet1.sfo002.pnap.net [63.251.63.
1]
15 * 131 ms 129 ms 74.217.195.66

Trace complete.

Highlighted
Copper Contributor
Copper Contributor
Posts: 10
Registered: ‎02-09-2013

Re: Routing / Latency issues

Message 66 of 77
(1,425 Views)

Just found this forum thread. Same problem I just posted about here:

 

http://forums.verizon.com/t5/FiOS-Internet/Many-websites-load-painfully-slow/td-p/536875

 

I did tweet verizonsupport today to for whatever that is worth.

 

Looks like, for me at least, it could be a level3.net problem but still..our provider ( verizon) should be helping it's paying customers!

Highlighted
Contributor
Contributor
Posts: 2
Registered: ‎02-09-2013

Re: Routing / Latency issues

Message 67 of 77
(1,381 Views)

Anyone get an answer on:

 

  8   173 ms   129 ms   128 ms  tinet-gw.customer.alter.net [152.179.72.122]
 

This hop is always the slowest on my tracert.  Before January 2013 there was no 173-128 ms problem.  It was more like 50ms.

Highlighted
Copper Contributor
Copper Contributor
Posts: 7
Registered: ‎02-01-2013

Re: Routing / Latency issues

Message 68 of 77
(1,353 Views)

FYI - other forums have a similiar issue, a senior member states

 


 

tinet-gw.customer

Thats a peering point, its not Verizon's issue but the games ISP isn't paying for the bandwidth there customers are trying to consume

tinet comes up allot on people complaining about bad pings, if your paying for that game service, complain, its their issue, not Verizons



 

 

 

 

Nice Try Incognito Verizon Customer Service rep.

 

If this is the case would you like to explain why it's ONLY Verizon customers with the problem?  I've had 3 different friends on different ISP's around the philly area.  Verizon is the only ISP with this server.

Highlighted
Platinum Contributor III
Platinum Contributor III
Posts: 5,881
Registered: ‎07-22-2009

Re: Routing / Latency issues

Message 69 of 77
(1,341 Views)

you realize he was quoting someone else on another forum and he linked you to there response right? 

Nickel Contributor
Nickel Contributor
Posts: 28
Registered: ‎07-19-2012

Re: Routing / Latency issues

Message 70 of 77
(1,319 Views)

To one of our Gold Contributes who certainly knows more than I do:

 

 

Does anyone know where the Verizon Speedtester is located for California?  When these problems occur for me (8pm-11pm PST EVERY night) I use the Verizon Speedtester and show VERY low download speeds.  I then went to speedtest.net and use the Los Angeles area and get NORMAL speeds.  However, it looks like me big problems happen when trying to hit East Coast servers.

How-To Videos
 
The following videos were produced by users like you!
   
Videos are subject to the Verizon Fios Community Terms of Service and User Guidelines and contains content that is not created by Verizon.
Covid19


Browse Categories
Categories:
Posts

Verizon Troubleshooters
Unable to find your answer here? Try searching Verizon Troubleshooters for more options.