massive package loss issue.
moonfang
Enthusiast - Level 2

i live in germantown, maryland.  i am a online gamer and recently i been expereincing frequent (like once everyone 5 minutes) disconnects from my games, which bascially means i can't play at all.  i did a ping google.com -t test with cmd, and it's showing about 1/3 to 1/4 of my pings are timing out.

i'm wondering if this is because of the storm, if this is due to damage done to your network, or if my box/router got wet or something.  could you let me know if there are other people in my area experiencing the same difficulties?

Re: massive package loss issue.
smith6612
Community Leader
Community Leader

When you post a traceroute to one of the affected game servers, where does the trace start to show packet loss, or a sudden jump in latency? If you can do this and provide the trace, that would be appreciated.

0 Likes
Re: massive package loss issue.
moonfang
Enthusiast - Level 2

here are two screen shots of my cmd box.  i dont see a upload button on this forum so i'm linking to deviant art.

tracert google.com

http://lxl-moonfang-lxl.deviantart.com/art/tracerrtgoogle-256276808

tracert pvp.net

http://lxl-moonfang-lxl.deviantart.com/art/tracertpvp-256277017

thank you for your help.

Re: massive package loss issue.
moonfang
Enthusiast - Level 2

i'd also like to add that when running the ping google.com -t test on cmd, in the past 6 hrs or so, the ammount of packet losses have gone down a little, although it is still casuing issues when i need a continous connection for something like a live stream or o online game.

Re: massive package loss issue.
moonfang
Enthusiast - Level 2

i take back what i said about any improvements.  =_=

Re: massive package loss issue.
smith6612
Community Leader
Community Leader

Which router are you currently using for the FiOS service, and in addition, are you using an Ethernet connection or a Wireless connection to the router? You also seem to be on an older, legacy FiOS network since you seem to be using PPPoE and I am assuming you are using a D-Link DI-524. This would also imply a BPON connection. If possible, please confirm this if you know the answer. If not, telling us at least the model number of your ONT would be a start, or how long you have had FiOS.

It's hard to say where the problem is off the bat since latency is all over the place, everywhere. We need to start ruling out things, starting with the connection to your router. Here's a comparison trace from my DSL connection. I'm connected to my network via Ethernet.

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\>tracert pvp.net

Tracing route to pvp.net [64.202.189.170]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.3.1
  2     9 ms     9 ms     8 ms  10.15.3.1
  3     9 ms    10 ms     9 ms  so-1-1-0-0.BUFF-CORE-RTR2.verizon-gni.net [130.81.13.77]
  4    19 ms    19 ms    19 ms  as4-0.NY5030-BB-RTR1.verizon-gni.net [130.81.20.106]
  5    20 ms    20 ms    20 ms  0.ae5.BR3.NYC4.ALTER.NET [152.63.16.9]
  6    20 ms    20 ms    21 ms  te-7-3-0.edge2.NewYork2.level3.net [4.68.111.137]
  7    20 ms    21 ms    20 ms  vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
  8    27 ms    26 ms    27 ms  ae-3-3.ebr2.Washington1.Level3.net [4.69.132.89]
  9    27 ms    27 ms    27 ms  ae-82-82.csw3.Washington1.Level3.net [4.69.134.154]
 10    26 ms    26 ms    26 ms  ae-81-81.ebr1.Washington1.Level3.net [4.69.134.137]
 11    43 ms    44 ms    43 ms  ae-2-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
 12    63 ms    63 ms    62 ms  ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
 13    67 ms    66 ms    66 ms  ae-93-93.csw4.Dallas1.Level3.net [4.69.151.169]
 14    63 ms    61 ms    62 ms  ae-91-91.ebr1.Dallas1.Level3.net [4.69.151.162]
 15   101 ms   100 ms   129 ms  ae-1-8.bar1.Phoenix1.Level3.net [4.69.133.29]
 16   101 ms   100 ms    99 ms  ae-5-5.car1.Phoenix1.Level3.net [4.69.148.117]
 17    99 ms   100 ms   100 ms  THE-GO-DADD.car1.Phoenix1.Level3.net [4.53.104.2]
 18   101 ms   100 ms   101 ms  ip-208-109-112-153.ip.secureserver.net [208.109.112.153]
 19     *        *        *     Request timed out.
 20   124 ms   104 ms   107 ms  ip-64-202-161-89.secureserver.net [64.202.161.89]
 21   103 ms   103 ms   103 ms  pwfwd-v01.prod.mesa1.secureserver.net [64.202.189.170]

Trace complete.

C:\Users\>tracert www.google.com

Tracing route to www.l.google.com [74.125.115.99]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.3.1
  2     9 ms     8 ms     9 ms  10.15.3.1
  3     9 ms     9 ms     9 ms  so-1-1-0-0.BUFF-CORE-RTR1.verizon-gni.net [130.81.13.73]
  4    20 ms    20 ms    19 ms  as4-0.NY325-BB-RTR1.verizon-gni.net [130.81.20.104]
  5    20 ms    20 ms    20 ms  0.so-0-0-0.XL3.NYC4.ALTER.NET [152.63.1.41]
  6    21 ms    21 ms    20 ms  TenGigE0-4-2-0.GW8.NYC5.ALTER.NET [152.63.16.73]
  7    88 ms    41 ms    41 ms  google-gw.customer.alter.net [152.179.72.62]
  8    22 ms    20 ms    20 ms  209.85.252.215
  9    22 ms    21 ms    22 ms  209.85.251.35
 10    29 ms    29 ms    30 ms  72.14.239.93
 11    39 ms    39 ms    40 ms  209.85.243.114
 12    38 ms    39 ms    37 ms  209.85.241.207
 13    39 ms    51 ms    38 ms  209.85.253.185
 14    39 ms    39 ms    39 ms  vx-in-f99.1e100.net [74.125.115.99]

Trace complete.

C:\Users\>

0 Likes
Re: massive package loss issue.
moonfang
Enthusiast - Level 2

thank you, i am indeed using a d-link router.  i have had this service for many years now.

Re: massive package loss issue.
moonfang
Enthusiast - Level 2

need to bump this for solutions. been going on around 2 weeks now. still dont know whats up.

0 Likes
Re: massive package loss issue.
lswartz1
Enthusiast - Level 1

How about asking tech support to update the firmware on your router/modem? They did that when I switched to Ubuntu & the very old modem would not connect except in windows. They replaced it with a new one about a year later too.

Re: massive package loss issue.
smith6612
Community Leader
Community Leader

Considering the latency to the router, it almost seems like the router might be the issue for those spikes you are having. Unless you're on wireless, that should be <1ms in regards to latency. As suggested above, see if you can upgrade the firmware on the D-Link (do it on Ethernet, not on Wireless) should one be available as a last resort. It might improve the performance of it. But otherwise, it could be possible if the D-Link is the problem, it is also on it's way out. It wouldn't be a surprise since I have a D-Link DIR-625 in service at a friend's home, and it loves to reboot constantly which only started happening within the last year. I have no clue why it's doing that, and I've even cracked it open to see if it's dusty inside but for the time being I'm using an older, less powerful Linksys router that can hardly handle the Cable connection to do the job. You haven't made it too clear if you were on Ethernet or Wireless, so this needs to be ruled out and new traces need to be posted up from Ethernet, if you were on Wireless.

While you're on the phone with Verizon, ask the tech if they can check to see what the usage is for your particular PON splitter. They might be able to find out if the problem is due to high usage on the splitter, dirty fiber, or rule it out to a router or backbone issue.

The beauty about these old FiOS installs is that they are all Ethernet. The negatory issue with them is, now with the higher speed packages, BPON is starting to show it's age and some people have noticed issues with speeds due to bandwidth usage across a particular splitter. Now, those seem to be far and few at the moment, but I wouldn't doubt such occurrances in college areas stuck on BPON.

0 Likes