×

Switch Account

Chino Hills...AGAIN

Reply
Nickel Contributor
Nickel Contributor
Posts: 26
Registered: ‎10-15-2009
Message 11 of 46
(4,764 Views)

I come back from vacation and the network is broke AGAIN???  Am I not allowed to go on vacation anymore?

 

Tracing route to verizon.net [206.46.232.39]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]
  2     6 ms     7 ms     7 ms  xxxx.xxxxx-xxxxx-xxx.verizon-gni.net [173.55.xxx.xxx]
  3   988 ms   994 ms   970 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
  4   966 ms   927 ms   941 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  5   959 ms   982 ms   982 ms  130.81.17.27
  6    46 ms    47 ms    49 ms  ge-3-1-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.17.68]
  7    47 ms    47 ms    47 ms  so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
  8    46 ms    46 ms    47 ms  po1.ctn-border1.vzlink.com [206.46.225.85]
  9  1029 ms  1027 ms  1001 ms  po121.ctn-core1.vzlink.com [206.46.225.18]
 10    49 ms    47 ms    47 ms  206.46.228.130
 11    51 ms    49 ms    47 ms  206.46.232.39

Trace complete.


Traceroute: 11/5/09, 6:41pm.

 

Nickel Contributor
Nickel Contributor
Posts: 26
Registered: ‎10-15-2009
Message 12 of 46
(4,756 Views)

I called tech support and they opened up a ticket for me.  Last month when we had this problem, they said only a few people were on their "group ticket" for this issue, so it didn't seem like a big problem to them.  If you are experiencing high latency in the area, I recommend calling tech support so they know you're affected, and ask for a ticket number.  That way they know it's affecting more than just a few people.

 

Current stats:  11/5/09, 7:45pm...

 

Tracing route to verizon.net [206.46.232.39]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]
  2     6 ms     7 ms     7 ms  xxxx.xxxxx-xxxxx-xxx.verizon-gni.net [173.55.xxx.xxx]
  3   960 ms   959 ms   967 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
  4  1016 ms  1039 ms   984 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  5  1070 ms  1047 ms  1019 ms  130.81.17.27
  6    46 ms    47 ms    46 ms  ge-3-1-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.17.68]
  7   126 ms    50 ms    47 ms  so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
  8    48 ms    47 ms    62 ms  po1.ctn-border1.vzlink.com [206.46.225.85]
  9    46 ms    46 ms    47 ms  po121.ctn-core1.vzlink.com [206.46.225.18]
 10    51 ms    47 ms    47 ms  206.46.228.130
 11  1108 ms  1067 ms  1110 ms  206.46.232.39

Trace complete.

 

 

Nickel Contributor
Nickel Contributor
Posts: 31
Registered: ‎10-25-2009
Message 13 of 46
(4,741 Views)

Tracing route to verizon.com [192.76.85.245]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]
  2     4 ms     5 ms     5 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
  3    10 ms     7 ms     9 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.140.122]
  4     7 ms     6 ms     8 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.29.244]
  5    10 ms     9 ms     8 ms  0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
  6    21 ms    21 ms    20 ms  0.ge-7-0-0.XT1.SAC1.ALTER.NET [152.63.49.89]
  7   885 ms   821 ms   904 ms  GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.
55.73]
  8   921 ms   900 ms   861 ms  verizon-gw.customer.alter.net [157.130.203.246]

  9   907 ms   874 ms   833 ms  192.76.84.5
 10     *        *        *     Request timed out.

Nickel Contributor
Nickel Contributor
Posts: 25
Registered: ‎10-26-2009
Message 14 of 46
(4,735 Views)

 

yup, same latency issue again. called it in and the FIOS support person wants to send me a new router... how funny or rather illogical is that. i told him a bunch of people in chino hills is having the same exact problem from days/weeks before.  he said 'maybe a bunch of us have bad routers'.  That just raised my blood pressure!!! 

anyway, here's my trace....

 

C:\>tracert www.google.com

 

Tracing route to www.l.google.com [74.125.19.147]

over a maximum of 30 hops:

 

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]

  2     5 ms     4 ms     4 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]

  3  1076 ms  1094 ms  1104 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]

  4  1109 ms  1147 ms  1164 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]

  5  1127 ms  1140 ms  1112 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]

  6     9 ms     9 ms     9 ms  0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]

  7  1107 ms  1082 ms  1067 ms  xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]

  8  1104 ms  1092 ms  1089 ms  ae-73-70.ebr3.LosAngeles1.Level3.net [4.69.144.116]

  9    19 ms    17 ms    17 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]

 10  1153 ms  1089 ms  1084 ms  ae-63-63.csw1.SanJose1.Level3.net [4.69.134.226]

 11    24 ms    24 ms    27 ms  ae-1-69.edge1.SanJose1.Level3.net [4.68.18.14]

 12    18 ms    17 ms    17 ms  GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]

 13    16 ms    17 ms    17 ms  209.85.251.98

 14    16 ms    17 ms  1082 ms  nuq04s01-in-f147.1e100.net [74.125.19.147]

 

Trace complete.

 

Copper Contributor dwoo
Copper Contributor
Posts: 18
Registered: ‎10-27-2009
Message 15 of 46
(4,735 Views)

1500ms ping !!!!

 

C:\>tracert www.google.com

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

  1    24 ms    28 ms   119 ms  L300.LSANCA-VFTTP-142.verizon-gni.net [71.254.182.1]
  2     6 ms     4 ms     4 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
  3     6 ms     4 ms     4 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
  4     7 ms     5 ms     4 ms  0.so-1-2-0.XL3.LAX15.ALTER.NET [152.63.10.133]
  5     8 ms  1693 ms     6 ms  0.ge-6-0-0.BR2.LAX15.ALTER.NET [152.63.116.149]
  6     7 ms     6 ms  1744 ms  xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
  7  1725 ms  1740 ms  1638 ms  ae-83-80.ebr3.LosAngeles1.Level3.net [4.69.144.180]
  8    25 ms    19 ms    15 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
  9  1614 ms  1740 ms  1740 ms  ae-83-83.csw3.SanJose1.Level3.net [4.69.134.234]
 10  1638 ms  1637 ms  1638 ms  ae-3-89.edge1.SanJose1.Level3.net [4.68.18.142]
 11    15 ms    15 ms    15 ms  GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
 12    25 ms    17 ms    18 ms  209.85.251.98
 13  1680 ms  1635 ms  1531 ms  nuq04s01-in-f147.1e100.net [74.125.19.147]

Trace complete.

Copper Contributor Osler
Copper Contributor
Posts: 11
Registered: ‎10-25-2009
Message 16 of 46
(4,719 Views)

Still with bad latency. I spoke with a guy named Oliver at support, who at least knew what a tracert was and asked me which hop I was having trouble with! A ticket was opened for me as well. Here's my latest tracert: As before, anything going through G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162] is bad.

 

 

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

  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]
  2     7 ms     7 ms     7 ms  L100.LSANCA-VFTTP-142.verizon-gni.net
  3   556 ms   504 ms   535 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
  4   541 ms   549 ms   562 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  5   597 ms   562 ms   564 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  6    21 ms    19 ms    17 ms  0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]
  7   550 ms   544 ms   551 ms  192.205.35.161
  8   640 ms   649 ms   604 ms  cr2.la2ca.ip.att.net [12.123.30.134]
  9    66 ms    67 ms    64 ms  cr2.dlstx.ip.att.net [12.122.28.177]
 10    67 ms    74 ms    70 ms  cr1.attga.ip.att.net [12.122.28.173]
 11   713 ms   654 ms   661 ms  12.123.22.5
 12    63 ms    67 ms    64 ms  12.88.97.6
 13    65 ms    65 ms    64 ms  72.14.233.56
 14   681 ms   126 ms    67 ms  209.85.254.243
 15   731 ms   752 ms   748 ms  209.85.253.145
 16    68 ms    67 ms    66 ms  yx-in-f100.1e100.net [74.125.45.100]

Trace complete.


Tracing route to verizon.net [206.46.232.39]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]
  2     8 ms     6 ms     7 ms  L100.LSANCA-VFTTP-142.verizon-gni.net
  3     8 ms     9 ms    10 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
  4     9 ms    10 ms    10 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
  5    48 ms    46 ms    47 ms  so-7-3-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.19.125]
  6    47 ms    47 ms    47 ms  so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
  7    46 ms    47 ms    46 ms  po1.ctn-border1.vzlink.com [206.46.225.85]
  8    47 ms    47 ms    47 ms  po121.ctn-core1.vzlink.com [206.46.225.18]
  9    46 ms    47 ms    47 ms  206.46.228.130
 10    46 ms    46 ms    47 ms  206.46.232.39

Trace complete.

Employee Emeritus Employee Emeritus
Employee Emeritus
Posts: 110
Registered: ‎09-08-2009
Message 17 of 46
(4,686 Views)

Whats up everybody! I did get your private messages & will escalate this issue again today! If you could keep posting some more trace routes to verizon.net also that would be helpful. & I beleive Misterjefferson you mentioned you opened up a group ticket? If you could private message me that ticket # . I would apprciate it Thanks All! will update shortly!

Brett
Verizon Telecom
Fiber Solution Center


Notice: Content posted by Verizon employees is meant to be informational and does not supercede or change the Verizon Forums User Guidelines or Terms or Service, or your Customer Agreement Terms and Conditions or Plan.

Nickel Contributor
Nickel Contributor
Posts: 40
Registered: ‎12-10-2008
Message 18 of 46
(4,673 Views)

I am also in Chino Hills and have recently noticed the VERY poor internet speeds.  I am glad it isn't just me.  I will try some of the trace routes when I get home from work today.  Speed tests show less than 1Mbps up or down !!!!

 

What number should I call to report the problem.  Maybe the more reports Vz gets they will begin to realize this is a system problem and not a bunch of bad routers....

 

 

Thanks

 

Nickel Contributor
Nickel Contributor
Posts: 25
Registered: ‎10-26-2009
Message 19 of 46
(4,655 Views)

as usual, in the morning, things are fine since it doesn't go thru the troubled router... have to wait till tonight to post trace routes again...

Nickel Contributor
Nickel Contributor
Posts: 25
Registered: ‎10-26-2009
Message 20 of 46
(4,649 Views)

 

n the morning, traffic doesn't seem to go thru  130.81.140.162 but rather to 130.81.140.122 as you can see in the trace below so can't see any issues yet.... some load balancing happening at night and we're getting re-routed to a bad router?

 

we'll see tonight....

 

$ tracert www.verizon.net

 

Tracing route to e3002.b.akamaiedge.net [96.6.236.79]

over a maximum of 30 hops:

 

  1     4 ms     3 ms     3 ms  Wireless_Broadband_Router.home [192.168.1.1]

  2     8 ms     7 ms     9 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]

  3    14 ms    12 ms    12 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]

 

  4    13 ms    12 ms    12 ms  P14-0-0.LSANCA-LCR-12.verizon-gni.net [130.81.27.31]

  5    14 ms    14 ms    14 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]

  6    14 ms    14 ms    14 ms  0.so-6-0-0.XT2.LAX9.ALTER.NET [152.63.10.157]

  7    14 ms    14 ms    14 ms  0.so-6-3-0.XT2.LAX7.ALTER.NET [152.63.112.69]

  8    14 ms    14 ms    14 ms  POS7-0.BR2.LAX7.ALTER.NET [152.63.112.149]

  9    14 ms    14 ms    14 ms  p64-5-0-1.r20.lsanca03.us.bb.gin.ntt.net [129.250.8.69]

 10    25 ms    24 ms    24 ms  as-0.r21.snjsca04.us.bb.gin.ntt.net [129.250.4.96]

 11    28 ms    27 ms    24 ms  po-4.r03.snjsca04.us.bb.gin.ntt.net [129.250.4.78]

 12    26 ms    27 ms    27 ms  a96-6-236-79.deploy.akamaitechnologies.com [96.6.236.79]

 

Trace complete.

 

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.


Browse Categories
Categories:
Posts

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