Massive Lag Spikes packet loss Verizon FIOS CA
|
Anyone else with verizon fios getting ridiculous packet loss over the last few days? I'm in socal. Problem seems to start with the NTT servers.
|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | Wireless_Broadband_Router.home - 0 | 114 | 114 | 0 | 0 | 1 | 0 | | L100.LSANCA-VFTTP-147.verizon-gni.net - 0 | 114 | 114 | 5 | 7 | 24 | 7 | | G0-11-3-4.LSANCA-LCR-22.verizon-gni.net - 0 | 114 | 114 | 8 | 10 | 20 | 10 | |so-3-1-0-0.LAX01-BB-RTR2.verizon-gni.net - 0 | 114 | 114 | 8 | 12 | 62 | 10 | | 0.xe-5-1-0.BR1.LAX15.ALTER.NET - 0 | 114 | 114 | 8 | 11 | 62 | 12 | | ae-7.r05.lsanca03.us.bb.gin.ntt.net - 6 | 94 | 89 | 37 | 39 | 43 | 39 | | ae-5.r21.lsanca03.us.bb.gin.ntt.net - 21 | 64 | 51 | 38 | 43 | 80 | 38 | | ae-1.r20.snjsca04.us.bb.gin.ntt.net - 43 | 42 | 24 | 0 | 30 | 121 | 121 | | ae-1.r07.snjsca04.us.bb.gin.ntt.net - 10 | 82 | 74 | 18 | 31 | 121 | 20 | | ae1.bbr02.eq01.sjc01.networklayer.com - 19 | 66 | 54 | 18 | 22 | 71 | 22 | | ae7.bbr02.eq01.sjc02.networklayer.com - 25 | 58 | 44 | 17 | 22 | 69 | 18 | | ae7.bbr01.cs01.lax01.networklayer.com - 14 | 74 | 64 | 0 | 33 | 125 | 20 | | ae7.bbr01.cs01.lax01.networklayer.com - 19 | 66 | 54 | 16 | 53 | 165 | 18 | | ae19.bbr01.eq01.dal03.networklayer.com - 12 | 78 | 69 | 60 | 83 | 167 | 70 | | ae0.dar01.sr01.dal01.networklayer.com - 14 | 74 | 64 | 51 | 71 | 123 | 67 | |173.192.44.22-static.reverse.softlayer.com - 14 | 74 | 64 | 48 | 77 | 178 | 172 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider Last edited by Menacetech on Jun 19, 2014, 12:01:30 AM
|
|
|
Looks like there might be a peering issue between alter and ntt.net here:
| 0.xe-5-1-0.BR1.LAX15.ALTER.NET - 0 | 114 | 114 | 8 | 11 | 62 | 12 | | ae-7.r05.lsanca03.us.bb.gin.ntt.net - 6 | 94 | 89 | 37 | 39 | 43 | 39 | You'll have to contact your ISP and provide that trace for their reference so they can escalate it appropriately. Good luck. | |
|
Thanks for the response drakier.. i finally had a chance to speak with verizon on the issue.
Verizon says the problem is "beyond" their control and I should contact the host. I already did that and the NTT server host tells me to contact my isp for assistance as i'm not a customer of theirs. Any other suggestions? |
|
" Verizon needs to contact NTT on your behalf. NTT is correct that they don't deal directly with end-users. Most carriers don't. Verizon is also correct that it is not their issue. But it is their responsibility as your ISP to forward issues to the later carriers as those carriers don't deal with end-users. You are not a customer of Level3 or NTT... but it is the ISP's responsibility to pass on that information to the correct party to get it resolved (if it hasn't been already). Have you checked again recently to see if you have the same issue in the same place? Often, this is self-corrected. | |
|
Same issue, same place in my trace. I'll contact Verizon again to see if they will communicate with NTT on my behalf.
Thanks again. |
|
" Actually.. they should probably contact ALTER on your behalf and then ALTER can work with NTT directly to figure out who's side the issue is on. The actual problem appears BETWEEN the ALTER and NTT hops (at the peer exchange). That means it could be either ALTER or NTT's problem.. or both. So Verizon should escalate your issue to ALTER, then ALTER can look into it and contact NTT if it turns out to be an issue with NTT. | |
|
Sounds like a plan. I'll give it a shot.
|
|
|
I've also been having lag spikes. FIOS in NY. Is it the same problem? Any recommendations?
|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | Wireless_Broadband_Router.home - 1 | 699 | 698 | 0 | 8 | 135 | 30 | | L100.NYCMNY-VFTTP-209.verizon-gni.net - 0 | 702 | 702 | 6 | 24 | 684 | 11 | |G103-0-0-0.NYCMNY-LCR-21.verizon-gni.net - 0 | 702 | 702 | 7 | 22 | 691 | 21 | | No response from host - 100 | 140 | 0 | 0 | 0 | 0 | 0 | | 0.ae1.BR3.NYC4.ALTER.NET - 0 | 702 | 702 | 9 | 23 | 685 | 14 | |xe-0-2-0-6.r06.nycmny01.us.bb.gin.ntt.net - 1 | 691 | 688 | 8 | 21 | 692 | 30 | | ae-3.r05.nycmny01.us.bb.gin.ntt.net - 1 | 699 | 698 | 8 | 21 | 692 | 21 | |xe-1-0-0.bbr01.tl01.nyc01.networklayer.com - 1 | 695 | 693 | 8 | 28 | 684 | 28 | | ae7.bbr02.tl01.nyc01.networklayer.com - 1 | 691 | 688 | 9 | 29 | 672 | 31 | | ae1.bbr01.eq01.chi01.networklayer.com - 1 | 695 | 693 | 26 | 37 | 121 | 63 | | ae20.bbr01.eq01.dal03.networklayer.com - 0 | 702 | 702 | 46 | 61 | 683 | 56 | | ae0.dar02.sr01.dal01.networklayer.com - 0 | 702 | 702 | 46 | 61 | 692 | 70 | | po2.fcr05.sr06.dal01.networklayer.com - 0 | 702 | 702 | 46 | 62 | 210 | 58 | |173.192.44.20-static.reverse.softlayer.com - 1 | 695 | 693 | 45 | 57 | 691 | 67 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider Last edited by JudgeGallows on Sep 17, 2014, 7:43:29 PM
|
|
" Next time please read the "Rules" sticky post, and please post your own thread. This was an old and resolved thread and there is no need to post to it for your issue. Even if it WAS related, the ACTUAL issue wouldn't be related to 3 months ago. As for your actual problem, my guess based on your trace is that you're using Wireless. Are you able to use a hard-wired connection to test with? Also, do you have a separate router and modem for the FIOS? If so, can you connect directly to the modem and test again and eliminate the router? You might also want to give everything a quick reboot just to ensure that it's not just the hardware acting up (it can do that). If you still have issues, post your issues in a new thread with new WinMTR reports with the new configurations. Good luck. |
