Recent Problem. High Ping.

[lLuffyl]

So, I've had FiOS for years now.  My family subscribed to it when it was very new.  I've never really had a problem.  My download is not as much as I would like it to be.  The most I've downloaded at a time is maybe 620kb/s, but that really doesn't even bug me.  The real problem is this high amount of ping that I have been getting recently, only during the day.  I do have a decent amount of devices connected, but they're not all on.  The only things that are really connected at one time is my computer and two laptops used by my nephews.  Usually I could tell when one of them was downloading something because my ping would be high and lag would be horrible on online games.  All that I would have to do was wait it out, but that wasn't a big deal.  The big deal now is that even when they aren't downloading (I am not either) the ping remains constantly high, in the 300's to 400's, sometimes maxing out at 600.  The only time it runs smoothly is late at night (around 11:00 PM) and early mornings (up until around 12:00 PM).  I'm not sure if there is a problem with my router and it's not distributing the bandwith correctly or what.  I've downloaded the in home agent, optimized my settings, updated my router, checked all my settings, etc.  Really out of ideas.

[MrBoozy]

I also got that problem, Except it started around 1-2 in the morning and went back to normal somtime later while i was sleeping. Now it's bad all the time and it's hard to do anything that requires a good ping.

[lLuffyl]

---

@MrBoozy wrote:

I also got that problem, Except it started around 1-2 in the morning and went back to normal somtime later while i was sleeping. Now it's bad all the time and it's hard to do anything that requires a good ping.

---

Yes, it is frustrating.  This whole problem does not interfere with downloading or anything with a dedicated server really.  I only have problems with certain games, as you said, that require ping to be good, games that use Peer to Peer.

[spacedebris]

many many possibilities.

First. Lets start with a tracert. See if there is anything obvious there. (I'm assuming you've already tried rebooting and resetting your router)

Post a tracert and we will take a look at it.

[lLuffyl]

Should I wait until a time when the problem begins?  Also, where should I test it, just any domain?  I've never really done a tracert so, I'm not exactly sure what you will need to be looking for. 

[spacedebris]

best bet is to run it several times. both when it happens and when everything is OK. This way we can see if/where any changes are happening.

Do you know how to run a tracert? You want to run it to the server that is having the high pings. So test it to the gaming server you play on.

[Hubrisnxs]

also make sure that you're getting these high ping times using dos or tracert, and not letting the game server report back to you what your ping time is.

if dos and tracert look good when you're having a problem with the game, then it's likely the game getting overloaded and not your connection.

[lLuffyl]

Well, the one thing is, it's not just this game.  If I were to do anything, it would be a bit laggy.  Web browsing too.  I usually notice it, then I got to www.pingtest.net and my ping, as I said, can sometimes max at maybe 600-700.  So, I'm not sure if I should just try a specific game, or just something else.

[spacedebris]

Well, it doesnt really matter where you test to. just so long as you have high ping to that location. I just suggest the game as it is one that you mentioned. But game, domain, or IP doensnt really matter, just so long as you are seeing the high ping so we can check to see if it is on your side, internet side, or destination side.

[lLuffyl]

Okay, sorry for my lack of knowledge in this area, this isn't my strength when it comes to computer/network knowledge.  So, I tried a few areas.  The first two are to google.  Now as you said, I should try the game I was mentioning.  The thing is the game is peer to peer.  So, I decided to connect to my friend, which are the next two.  Then, I got my friend to connect to me, the last one.  During this I made sure all other devices were off that were connected to the internet.

Spoiler

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Ryan>tracert google.com

Tracing route to google.com [72.14.204.104]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     7 ms     7 ms     9 ms  L100.PHLAPA-VFTTP-92.verizon-gni.net [98.111.139
.1]
  3     8 ms     8 ms     7 ms  G1-2-792.PHLAPA-LCR-07.verizon-gni.net [130.81.1
31.138]
  4   496 ms   147 ms   119 ms  so-3-1-0-0.PHIL-BB-RTR1.verizon-gni.net [130.81.
29.4]
  5    62 ms    99 ms    50 ms  so-8-0-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net
[130.81.17.3]
  6    26 ms    15 ms    22 ms  te-11-0-0.edge1.Washington4.level3.net [4.68.111
.253]
  7   100 ms    61 ms    74 ms  ae-3-89.edge1.Washington1.Level3.net [4.68.17.14
4]
  8   367 ms   112 ms    35 ms  GOOGLE-INC.edge1.Washington1.Level3.net [4.79.22
8.38]
  9   122 ms    65 ms    27 ms  209.85.240.136
 10    31 ms    19 ms    34 ms  66.249.94.46
 11    20 ms    17 ms    17 ms  iad04s01-in-f104.1e100.net [72.14.204.104]

Trace complete.

C:\Documents and Settings\Ryan>




~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~




Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Ryan>tracert google.com

Tracing route to google.com [72.14.204.147]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     7 ms     7 ms     7 ms  L100.PHLAPA-VFTTP-92.verizon-gni.net [98.111.139
.1]
  3     7 ms    10 ms     7 ms  1-2-892.PHLAPA-LCR-08.verizon-gni.net [130.81.13
3.60]
  4     7 ms     9 ms     8 ms  so-3-1-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.
29.6]
  5    17 ms    14 ms    15 ms  so-13-2-0-0.RES-BB-RTR2.verizon-gni.net [130.81.
19.118]
  6    14 ms    14 ms    14 ms  0.xe-10-0-0.BR2.IAD8.ALTER.NET [152.63.34.9]
  7    73 ms    42 ms    14 ms  te-11-0-0.edge1.Washington4.level3.net [4.68.111
.253]
  8    17 ms    19 ms    17 ms  ae-4-99.edge1.Washington1.Level3.net [4.68.17.20
8]
  9    16 ms    19 ms    17 ms  GOOGLE-INC.edge1.Washington1.Level3.net [4.79.23
1.6]
 10    20 ms    16 ms    17 ms  209.85.240.136
 11    24 ms    19 ms    29 ms  66.249.94.54
 12    18 ms    17 ms    18 ms  iad04s01-in-f147.1e100.net [72.14.204.147]

Trace complete.

C:\Documents and Settings\Ryan>





~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~





Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Ryan>tracert 75.177.118.84

Tracing route to cpe-075-177-118-084.triad.res.rr.com [75.177.118.84]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     5 ms     8 ms     9 ms  L100.PHLAPA-VFTTP-92.verizon-gni.net [98.111.139
.1]
  3     6 ms     7 ms     7 ms  G1-2-792.PHLAPA-LCR-07.verizon-gni.net [130.81.1
31.138]
  4     6 ms     9 ms    10 ms  so-3-1-0-0.PHIL-BB-RTR1.verizon-gni.net [130.81.
29.4]
  5    48 ms    44 ms    14 ms  so-8-0-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net
[130.81.17.3]
  6    15 ms    14 ms    14 ms  xe-10-1-0.edge1.Washington4.level3.net [4.68.63.
245]
  7    14 ms    14 ms    14 ms  ae-1-69.edge2.Washington1.Level3.net [4.68.17.17
]
  8    53 ms    17 ms    16 ms  ROADRUNNER.edge2.Washington1.Level3.net [4.79.22
.58]
  9    18 ms    16 ms    17 ms  ae-1-0.cr0.dca10.tbone.rr.com [66.109.6.182]
 10    24 ms    21 ms    24 ms  66.109.6.81
 11    26 ms    27 ms    24 ms  gig5-0-0.gnboncsg-rtr1.triad.rr.com [24.93.64.17
9]
 12    36 ms    37 ms    37 ms  gig3-0-0.gnbonckrn-10k1.triad.rr.com [24.28.225.
185]
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *




~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~




Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Ryan>tracert 75.177.118.85

Tracing route to cpe-075-177-118-085.triad.res.rr.com [75.177.118.85]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     9 ms     7 ms     7 ms  L100.PHLAPA-VFTTP-92.verizon-gni.net [98.111.139
.1]
  3    10 ms     7 ms     9 ms  1-2-892.PHLAPA-LCR-08.verizon-gni.net [130.81.13
3.60]
  4     6 ms     7 ms     9 ms  so-3-1-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.
29.6]
  5    14 ms    14 ms    15 ms  so-13-2-0-0.RES-BB-RTR2.verizon-gni.net [130.81.
19.118]
  6    14 ms    14 ms    14 ms  0.xe-2-3-0.BR1.IAD8.ALTER.NET [152.63.32.158]
  7    16 ms    14 ms    14 ms  xe-10-1-0.edge1.Washington4.level3.net [4.68.63.
245]
  8    16 ms    16 ms    17 ms  ae-1-69.edge2.Washington1.Level3.net [4.68.17.17
]
  9    18 ms    17 ms    17 ms  ROADRUNNER.edge2.Washington1.Level3.net [4.79.22
.6]
 10    18 ms    17 ms    17 ms  ae-1-0.cr0.dca10.tbone.rr.com [66.109.6.182]
 11    22 ms    22 ms    21 ms  66.109.6.81
 12    25 ms    26 ms    25 ms  gig5-0-0.gnboncsg-rtr1.triad.rr.com [24.93.64.17
9]
 13    42 ms    36 ms    36 ms  gig3-0-0.gnbonckrn-10k1.triad.rr.com [24.28.225.
185]
 14     *        *        *     Request timed out.
 15




~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~





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

C:\Users\Joe>tracert 71.244.102.164

Tracing route to pool-71-244-102-164.phlapa.fios.verizon.net [71.244.102.164]
over a maximum of 30 hops:

  1    <1 ms     1 ms     1 ms  192.168.2.1
  2    11 ms     9 ms     9 ms  10.207.128.1
  3    11 ms    12 ms    11 ms  gig2-0-3.gnboncsg-rtr1.triad.rr.com [24.28.225.1
86]
  4    11 ms    13 ms    12 ms  ge-1-3-0.rlghncpop-rtr1.southeast.rr.com [24.93.
64.48]
  5    18 ms    18 ms    19 ms  ae-3-0.cr0.dca10.tbone.rr.com [66.109.6.80]
  6    28 ms    21 ms    19 ms  ae-1-0.pr0.dca20.tbone.rr.com [66.109.6.183]
  7    21 ms    19 ms    18 ms  xe-4-1-0.edge2.Washington1.Level3.net [4.79.22.5
3]
  8    23 ms    20 ms    20 ms  ae-1-69.edge1.Washington4.Level3.net [4.68.17.18
]
  9    20 ms    21 ms    20 ms  mci-level3-te.washington4.Level3.net [4.68.63.16
6]
 10    20 ms    21 ms    22 ms  0.ge-13-1-0.RES-BB-RTR2.verizon-gni.net [152.63.
32.162]
 11    30 ms    27 ms    28 ms  so-6-2-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.
19.105]
 12    28 ms    28 ms    26 ms  P14-0-0.PHLAPA-LCR-04.verizon-gni.net [130.81.29
.215]
 13    27 ms    28 ms    29 ms  P4-0-0.PHLAPA-LCR-06.verizon-gni.net [130.81.30.
155]
 14    29 ms    29 ms    32 ms  P13-0.PHLAPA-LCR-08.verizon-gni.net [130.81.27.5
1]
 15     *        *        *     Request timed out.
 16    35 ms    39 ms    39 ms  pool-71-244-102-164.phlapa.fios.verizon.net [71.
244.102.164]

Trace complete.

[slammedcivic778]

i too am having the same issue can anybody help me here are my tracert results

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

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

  1     3 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2   667 ms   390 ms   579 ms  L100.NWRKNJ-VFTTP-61.verizon-gni.net [96.242.19.1]
  3   129 ms    91 ms   151 ms  G11-3-661.NWRKNJ-LCR-06.verizon-gni.net [130.81.104.84]
  4   968 ms  1314 ms  1470 ms  so-6-2-0-0.NWRK-BB-RTR2.verizon-gni.net [130.81.28.150]
  5   532 ms   924 ms   177 ms  so-1-2-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.17.74]
  6   591 ms   302 ms   805 ms  so-12-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.17.6]
  7   902 ms   232 ms   967 ms  xe-4-1-3-0.NY325-BB-RTR2.verizon-gni.net [130.81.17.83]
  8   462 ms    41 ms    63 ms  vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
  9   181 ms   129 ms   234 ms  ae-4-4.ebr1.NewYork1.Level3.net [4.69.141.17]
 10   201 ms    56 ms    21 ms  ae-84-84.csw3.NewYork1.Level3.net [4.69.134.122]
 11  1169 ms  1159 ms  1032 ms  ae-3-89.edge1.NewYork1.Level3.net [4.68.16.142]
 12   404 ms  1111 ms   295 ms  GOOGLE-INC.edge1.NewYork1.Level3.net [4.71.172.82]
 13   205 ms   610 ms   838 ms  72.14.238.232
 14   409 ms   426 ms   927 ms  209.85.241.222
 15   585 ms  1111 ms   622 ms  lga15s04-in-f104.1e100.net [66.249.90.104]

C:\Users\Brian>tracert verizon.net
Tracing route to verizon.net [206.46.232.39]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2    66 ms   157 ms   117 ms  L100.NWRKNJ-VFTTP-61.verizon-gni.net [96.242.19.1]
  3   148 ms   128 ms   144 ms  G11-3-561.NWRKNJ-LCR-05.verizon-gni.net [130.81.97.6]
  4    14 ms   127 ms   135 ms  so-6-2-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.28.148]
  5   150 ms    32 ms   126 ms  so-12-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.17.6]
  6   108 ms   131 ms   159 ms  so-10-0-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net [130.81.19.111]
  7   251 ms   219 ms   223 ms  so-4-0-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.17.41]
  8   775 ms   578 ms   536 ms  so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
  9   305 ms   267 ms   192 ms  po1.ctn-border1.vzlink.com [206.46.225.85]
 10    97 ms    66 ms   162 ms  po121.ctn-core1.vzlink.com [206.46.225.18]
 11    77 ms   281 ms    86 ms  206.46.228.131
 12   314 ms   186 ms   821 ms  206.46.232.39

Trace complete.

C:\Users\Brian>tracert verizon.net
Tracing route to verizon.net [206.46.232.39]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2   232 ms    20 ms   229 ms  L100.NWRKNJ-VFTTP-61.verizon-gni.net [96.242.19.1]
  3   151 ms   115 ms   270 ms  G11-3-561.NWRKNJ-LCR-05.verizon-gni.net [130.81.97.6]
  4   262 ms   206 ms    14 ms  so-6-2-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.28.148]
  5   103 ms    24 ms    24 ms  so-12-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.17.6]
  6   132 ms    40 ms   140 ms  so-10-0-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net [130.81.19.111]
  7   104 ms    95 ms   133 ms  so-4-0-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.17.41]
  8   326 ms   187 ms   279 ms  so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
  9   308 ms   403 ms   248 ms  po1.ctn-border1.vzlink.com [206.46.225.85]
 10   206 ms   237 ms   228 ms  po121.ctn-core1.vzlink.com [206.46.225.18]
 11    91 ms    92 ms   220 ms  206.46.228.131
 12   265 ms   239 ms   244 ms  206.46.232.39

Trace complete.

[lasagna]

Wow ...  you've got good connectivity to your router, but 600ms or more to the first hop out in Verizon's network?   You should never see more than 10-20ms between your router and the first hop in Verizon's network.   You should call this in to Verizon and ask them to test your connection to the router.   If they don't see it, then it's likely the router itself.  Show them these traceroutes -- anyone beyond a level 1 tech will agree there's something wrong there.

[lLuffyl]

I'm guessing I should do something along the same lines.  This is one that I recently did during the "bad connectivity." 

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Ryan>tracert google.com

Tracing route to google.com [72.14.204.99]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2   607 ms   698 ms   721 ms  L100.PHLAPA-VFTTP-92.verizon-gni.net [98.111.139
.1]
  3   719 ms   614 ms   680 ms  1-2-892.PHLAPA-LCR-08.verizon-gni.net [130.81.13
3.60]
  4   649 ms   700 ms   604 ms  so-3-1-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.
29.6]
  5   725 ms   722 ms   704 ms  so-13-2-0-0.RES-BB-RTR2.verizon-gni.net [130.81.
19.118]
  6   492 ms   604 ms   649 ms  0.xe-5-1-0.BR2.IAD8.ALTER.NET [152.63.34.73]
  7   728 ms   630 ms   616 ms  xe-5-1-0.edge1.washinton4.level3.net [4.68.62.97
]
  8   719 ms   715 ms   682 ms  ae-3-89.edge1.Washington1.Level3.net [4.68.17.14
4]
  9   778 ms   767 ms   752 ms  GOOGLE-INC.edge1.Washington1.Level3.net [4.79.22
8.38]
 10   533 ms   514 ms   563 ms  209.85.240.136
 11   613 ms   654 ms   612 ms  66.249.94.46
 12   668 ms   675 ms   727 ms  iad04s01-in-f99.1e100.net [72.14.204.99]

Trace complete.

C:\Documents and Settings\Ryan>

[lasagna]

That doesn't look good either ... here's one more thing to try ....

Login to the router, go to Advanced Settings, choose Diagnostics, and run the ping test against somewhere like www.google.com for about 10 or so pings and see what your times look like.   Not quite as much detail as the traceroute but it takes out some of the internal portions of the router as a potential point of the failure.

Also, try the traceroute from the PC with the "-d" option (just to take DNS resolution out of the picture).   Here's a traceroute from my network to www.google.com for example (I'm in central PA for reference - my IP address removed from hop #2):

C:\>tracert www.google.com

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

1     4 ms     4 ms     3 ms  192.168.1.1 

2    10 ms     8 ms    10 ms  L100.HRBGPA-VFTTP-10.verizon-gni.net [x.x.x.x] 

3    10 ms    10 ms     9 ms  G9-0-0-210.HRBGPA-LCR-02.verizon-gni.net [130.81.139.122] 

4    23 ms    24 ms    22 ms  so-12-1-0-0.RES-BB-RTR2.verizon-gni.net [130.81.28.254] 

5    23 ms    59 ms    24 ms  0.xe-7-1-0.BR2.IAD8.ALTER.NET [152.63.34.189] 

6    26 ms    59 ms    24 ms  xe-10-1-0.edge1.Washington4.level3.net [4.68.63.245] 

7    23 ms    22 ms    22 ms  ae-1-69.edge1.Washington1.Level3.net [4.68.17.16] 

8    25 ms    42 ms    26 ms  GOOGLE-INC.edge1.Washington1.Level3.net [4.79.228.38] 

9    24 ms   133 ms    26 ms  209.85.240.136 

10    34 ms    34 ms    32 ms  66.249.94.46 

11    25 ms    26 ms    25 ms  iad04s01-in-f104.1e100.net [72.14.204.104]

Trace complete.

[lLuffyl]

Okay, from Diagnostic I recieved:

Minimum = 16 ms
Maximum = 46 ms
Average = 21 ms

From google.  This is during the time when everything is fine though, so maybe I will try tomorrow when it acts up again. 

This is with the -d:

C:\Documents and Settings\Ryan>tracert -d google.com

Tracing route to google.com [72.14.204.103]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    39 ms    14 ms    14 ms  98.111.139.1
  3     8 ms     7 ms     8 ms  130.81.133.60
  4     7 ms     9 ms    10 ms  130.81.29.6
  5    14 ms    15 ms    16 ms  130.81.19.104
  6    15 ms    14 ms    75 ms  152.63.34.73
  7    14 ms    14 ms    44 ms  4.68.63.141
  8    14 ms    14 ms    15 ms  4.68.17.80
  9    17 ms    17 ms    17 ms  4.79.231.6
 10    17 ms    17 ms    17 ms  209.85.240.136
 11    26 ms    22 ms    19 ms  66.249.94.46
 12    16 ms    19 ms    17 ms  72.14.204.103

Trace complete.

C:\Documents and Settings\Ryan>

[lasagna]

Yeah ... if it's not acting up, you can't really do much.   I had a similar problem a year or so ago when I was on Comcast and it took me a couple of days before I managed to get them to "see" the problem and acknowledge that it was between the router and their upstream network (turned out to be a bad router card in there upstream network somewhere).

Since the fiber shot is a dedicated run all the way back to the first hop, even when there's heavy congesting within Verizon's network, your first hop shouldn't be seeing high latency.   All bets are off after the first hop outside your network if they have a bandwidth issue ... but to the first hop beyon your router, should always be clean as a whistle.

[radove]

I have this same issue in Baltimore Maryland.  Its off and on but most of the time, its pretty bad.  I can't even play games anymore. 

[spacedebris]

Luffy (go one piece!!! LOL )

your first set of tracerts show a problem on hops 4 and 5. Being part of the Verizon network. For this you would need to contact Verizon and ask that a network tech take a look at those routers. Have your tracert's handy because the name and IP address of those routers are important.

Now for the second post of tracert you posted and for slammedcivic, thoses show a problem on the gateway router. This also could be a problem on the Verizon gateway router (again talk to the network tech) or it could be a communication error between your router and the fiber network. This could possibly be fixed by rebooting your ONT. However I got a note from Verizon the last time I suggested rebooting your ONT telling me they wished I wouldnt tell you that because it can clear out the logs or something they need to help troubleshoot your problem. So I would probably start by calling them and then after you've given them a chance to help you, THEN I would reboot your ONT (unplug power, disconnect battery, wait 2 minutes, reconnect electric, then when working, reconnect battery)

[slammedcivic778]

spacedebris i have done all of that and none of it has worked i need to really get it at a bad time and call tech support and hope it stays down during that call because it has a weird way of working when i call in sometimes

[lasagna]

Yeah ... this are the most frustrating type of problem because you have to catch it while it's doing it and get Verizon on the phone at the same time.    Like I said previously, it took me several days of repeat calls when I had a similar problem on Comcast to get it resolve -- and then it took the local tech (who showed up at my house each time) giving me his cell phone number so I could call him exactly when it was happening so that they could investigate it right when it happened.   Good Luck with that.

You could ask Verizon if they have a line monitor or other quality of service test that they could put on your connection for a 24-hour period to watch what's going on.   I don't know that they do, but that would be the right way to handle it.  If you can get past the level 1 tech support, the next person up the chain would probably know.

[slammedcivic778]

im not gonna give up and will take your info and continue to fight with them on this thanks for your input