- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's not just chino hills, Like I said earlier, I'm in Portland, Oregon, same problem. {please keep your posts courteous}. This has been going on for way too long. Fix the fracken network already. I'm not calling tech support again. If I hear one more **bleep** tell me to push the reset button on that {edit} router verizon supplies, I am going to puke.
If I wanted DSL speeds, I would have ordered DSL.
Additionaly, Verizon needs to hire people for tech support that can read above a third grade level, and have a strong command of the english language. When a tech support person says, "I'mma putch ya through ta billin' soze you can axe em' what ta do", it doesn't inspire confidence, both in the person that said that, and the person that hired him.
Billing can not fix this, and twice now, Tech support has tried to transfer me to billing.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok all, again if you could please confirm if issue it resolved tonight just got an update that it should & if you could again paste trace routes & times which is very helpful. Thanks again Brett
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Aravoth, your problem has nothing to do with what is being talked about here. The trace route you posted....
@aravoth wrote:
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 8 ms 6 ms 8 ms **.***.***.1
3 7 ms 7 ms 7 ms ***.**.***.10
4 13 ms 14 ms 15 ms P12-0.PTLDOR-LCR-01.verizon-gni.net [130.81.27.1
72]
5 14 ms 14 ms 14 ms so-7-3-0-0.SEA01-BB-RTR1.verizon-gni.net [130.81
.28.160]
6 13 ms 14 ms 14 ms 0.so-7-1-0.XT1.SEA7.ALTER.NET [152.63.105.57]
7 15 ms 14 ms 15 ms 0.so-2-0-0.XT1.SEA1.ALTER.NET [152.63.104.225]
8 14 ms 14 ms 14 ms POS4-0.BR2.SEA1.ALTER.NET [152.63.106.9]
9 13 ms 14 ms 14 ms 204.255.169.22
10 20 ms 16 ms 20 ms ae-32-52.ebr2.Seattle1.Level3.net [4.68.105.62]
11 69 ms 72 ms 69 ms ae-2.ebr2.Denver1.Level3.net [4.69.132.54]
12 75 ms 72 ms 72 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37]
13 68 ms 72 ms 69 ms ae-2.ebr2.Dallas1.Level3.net [4.69.132.106]
14 70 ms 70 ms 72 ms ae-93-98.ebr3.Dallas1.Level3.net [4.69.146.92]
15 101 ms * * ae-7.ebr3.Atlanta2.Level3.net [4.69.134.22]
16 97 ms 97 ms 97 ms ae-21-52.car1.Atlanta1.Level3.net [4.68.103.34]
17 88 ms 89 ms 90 ms GOOGLE-INC.car1.Atlanta1.Level3.net [4.71.20.22]
18 89 ms 90 ms 112 ms 209.85.254.241
19 101 ms 92 ms 89 ms 209.85.253.137
20 97 ms 98 ms 97 ms yx-in-f100.1e100.net [74.125.45.100]
Trace complete.
shows no obvious network related issues. The only problem I see on this particular trace route is a possible problem on hop 15 in Atlanta GA. This is out on the internet and there is nothing that Verizon or you can do about that one. But for the most part your trace route looks perfectly normal. Unlike the ones being discussed on this thread.
No, if you are having speed issues. It is something different that what is being talked about here. If I were you, I'd start another thread, give a description of your problem and let the VZ guys start looking into it, and provide suggestions on your particular issue.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
the latest tracert (10-28-2009, 2:15pm) from Chino Hills,
to google.com
Tracing route to google.com {edited for privacy}
over a maximum of 30 hops:
1 2 ms 2 ms 1 ms L101.VFTTP-142.LSANCA.verizon-gni.net [71.254.18
2.1]
2 279 ms 205 ms 203 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.8
1.140.162]
3 216 ms 199 ms 204 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81
.29.246]
4 220 ms 307 ms 305 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
5 7 ms 5 ms 6 ms 0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]
6 7 ms 5 ms 5 ms 192.205.35.161
7 62 ms 60 ms 63 ms cr2.la2ca.ip.att.net [12.123.30.134]
8 63 ms 61 ms 61 ms cr2.dlstx.ip.att.net [12.122.28.177]
9 201 ms 304 ms 306 ms cr1.attga.ip.att.net [12.122.28.173]
10 190 ms 197 ms 270 ms 12.123.22.5
11 394 ms 408 ms 306 ms 12.88.97.6
12 64 ms 60 ms 61 ms 72.14.233.56
13 394 ms 304 ms 409 ms 209.85.254.249
14 64 ms 61 ms 71 ms 64.233.174.46
15 300 ms 307 ms 306 ms gw-in-f100.1e100.net [74.125.67.100]
Trace complete.
to verizon.com
Tracing route to verizon.com [192.76.85.245]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms L101.VFTTP-142.LSANCA.verizon-gni.net [71.254.18
2.1]
2 6 ms 4 ms 5 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.140.122]
3 6 ms 5 ms 4 ms so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.29.244]
4 8 ms 6 ms 6 ms 0.so-6-3-0.XT1.LAX9.ALTER.NET [152.63.10.153]
5 18 ms 17 ms 17 ms 0.so-5-0-0.XT1.SAC1.ALTER.NET [152.63.0.98]
6 270 ms 204 ms 204 ms GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.
55.73]
7 241 ms 204 ms 205 ms verizon-gw.customer.alter.net [157.130.203.246]
8 22 ms 17 ms 18 ms 192.76.84.5
9 * * * Request timed out.
10 * ^C
****** much much better than yesterday, good job ******
(well, if LCR-12 can lower to 100 ping that will be better 😛 )
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello all.... Well to keep consistent i am another user/subscriber here in the Chino/Chino hills area. and as like everyone else i have severe latency while surfing the net or playing online game. below are some of my tracert print outs.....
Target Name: www.download.com
IP: 216.239.122.164
Date/Time: 10/28/2009 3:18:16 PM
1 1 ms 3 ms 3 ms Wireless_Broadband_Router.home [192.168.1.1]
2 7 ms 10 ms 9 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
3 511 ms 507 ms 424 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 507 ms 519 ms 430 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 500 ms 517 ms 426 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 495 ms 524 ms 429 ms 0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
7 18 ms 11 ms 14 ms [192.205.35.161]
8 50 ms 46 ms 46 ms cr2.la2ca.ip.att.net [12.123.30.134]
9 530 ms 562 ms 460 ms cr2.dlstx.ip.att.net [12.122.28.177]
10 561 ms 561 ms 468 ms gar10.dlstx.ip.att.net [12.122.138.125]
11 542 ms 557 ms 473 ms [12.87.121.22]
12 533 ms 551 ms 476 ms c18-rb-gtm1-tron-xw-lb.cnet.com [216.239.122.164]
Ping statistics for www.download.com
Packets: Sent = 3, Received = 3, Lost = 0 (0.0%)
Round Trip Times: Minimum = 476ms, Maximum = 551ms, Average = 520ms
Target Name: www.download.com
IP: 216.239.122.176
Date/Time: 10/28/2009 3:34:06 PM
1 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 8 ms 9 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
3 336 ms 340 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 334 ms 342 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 330 ms 336 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 332 ms 336 ms 0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]
7 11 ms 16 ms [192.205.35.161]
8 49 ms 50 ms cr2.la2ca.ip.att.net [12.123.30.134]
9 329 ms 373 ms cr2.dlstx.ip.att.net [12.122.28.177]
10 334 ms 352 ms gar10.dlstx.ip.att.net [12.122.138.117]
11 341 ms 346 ms [12.87.121.22]
12 334 ms 343 ms c18-rb-gtm3-tron-xw-lb.cnet.com [216.239.122.176]
Ping statistics for www.download.com
Packets: Sent = 2, Received = 2, Lost = 0 (0.0%)
Round Trip Times: Minimum = 334ms, Maximum = 343ms, Average = 338ms
When playing online games my latency starts at about 400ms...... and by 9pm...it will be near 5000ms....
Hopefully another person posting here will help.....
thanks
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4:50pm can't believe lag is back !! (10/28/2009)
Tracing route to google.com [74.125.45.100]
over a maximum of 30 hops:
1 2 ms 1 ms 2 ms L101.VFTTP-142.LSANCA.verizon-gni.net{edited for privacy}
2 563 ms 513 ms 510 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
3 533 ms 511 ms 511 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
4 534 ms 511 ms 511 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
5 431 ms 512 ms 411 ms 0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
6 9 ms 5 ms 5 ms 192.205.35.161
7 63 ms 61 ms 61 ms cr2.la2ca.ip.att.net [12.123.30.134]
8 105 ms 60 ms 61 ms cr2.dlstx.ip.att.net [12.122.28.177]
9 490 ms 408 ms 410 ms cr1.attga.ip.att.net [12.122.28.173]
10 442 ms 409 ms 409 ms 12.123.22.5
11 432 ms 409 ms 409 ms 12.88.97.6
12 532 ms 513 ms 511 ms 72.14.233.54
13 535 ms 513 ms 509 ms 72.14.232.215
14 532 ms 511 ms 514 ms 209.85.253.145
15 639 ms 716 ms 616 ms yx-in-f100.1e100.net [74.125.45.100]
Trace complete.
Tracing route to verizon.com [192.76.85.245]
over a maximum of 30 hops:
1 7 ms 2 ms 2 ms L101.VFTTP-142.LSANCA.verizon-gni.net [71.254.182.1]
2 6 ms 3 ms 4 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
3 9 ms 4 ms 4 ms so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
4 7 ms 6 ms 6 ms 0.so-6-3-0.XT1.LAX9.ALTER.NET [152.63.10.153]
5 19 ms 17 ms 21 ms 0.so-5-0-0.XT1.SAC1.ALTER.NET [152.63.0.98]
6 459 ms 409 ms 408 ms GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.55.73]
7 433 ms 406 ms 409 ms verizon-gw.customer.alter.net [157.130.203.246]
8 20 ms 17 ms 18 ms 192.76.84.5
9 * * * Request timed out.
10 * ^C
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My current tracerts are below. Practically speaking (i.e. in-game and downloading), connection remains very poor.
Tracing route to us.logon.battle.net [12.129.206.130]
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 246 ms 254 ms 247 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 287 ms 287 ms 297 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 329 ms 324 ms 337 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 12 ms 12 ms 22 ms 0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
7 305 ms 302 ms 292 ms 192.205.35.161
8 11 ms 12 ms 294 ms cr2.la2ca.ip.att.net [12.123.30.134]
9 9 ms 12 ms 12 ms gar4.la2ca.ip.att.net [12.122.129.169]
10 12 ms 12 ms 12 ms 12.122.255.70
11 283 ms 281 ms 292 ms 12.129.193.254
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 12.129.211.36 reports: Destination net unreachable.
Trace complete.
Tracing route to vpn.pvhmc.org [65.218.207.68]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms myrouter.home [192.168.1.1]
2 5 ms 7 ms 7 ms L100.LSANCA-VFTTP-142.verizon-gni.net
3 351 ms 334 ms 347 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 351 ms 352 ms 349 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 371 ms 357 ms 394 ms 0.so-6-0-0.XT2.LAX9.ALTER.NET [152.63.10.157]
6 424 ms 409 ms 416 ms 0.so-6-3-0.XT2.LAX7.ALTER.NET [152.63.112.69]
7 438 ms 422 ms 399 ms GigabitEthernet7-0-0.GW7.LAX7.ALTER.NET [152.63.118.53]
8 15 ms 15 ms 14 ms pvhmc-gw.customer.alter.net [157.130.233.98]
9 21 ms 16 ms 19 ms vpn.pvhmc.org [65.218.207.68]
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 7 ms 6 ms 7 ms L100.LSANCA-VFTTP-142.verizon-gni.net
3 10 ms 10 ms 9 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
4 10 ms 9 ms 10 ms so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
5 47 ms 47 ms 48 ms so-3-3-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.19.18]
6 129 ms 84 ms 46 ms so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
7 48 ms 47 ms 47 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 45 ms 47 ms 47 ms 206.46.232.39
Trace complete.
Tracing route to google.com [74.125.67.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 6 ms L100.LSANCA-VFTTP-142.verizon-gni.net
3 473 ms 469 ms 455 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 391 ms 396 ms 402 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 377 ms 392 ms 362 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 10 ms 12 ms 12 ms 0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
7 380 ms * 418 ms 192.205.35.161
8 389 ms 397 ms 424 ms cr2.la2ca.ip.att.net [12.123.30.134]
9 63 ms 65 ms 67 ms cr2.dlstx.ip.att.net [12.122.28.177]
10 65 ms 64 ms 65 ms cr1.attga.ip.att.net [12.122.28.173]
11 376 ms 379 ms 390 ms 12.123.22.5
12 66 ms 64 ms 65 ms 12.88.97.6
13 480 ms 481 ms 527 ms 72.14.233.54
14 * 71 ms 77 ms 72.14.239.127
15 80 ms 72 ms 72 ms 64.233.174.46
16 70 ms 66 ms 67 ms gw-in-f100.1e100.net [74.125.67.100]
Trace complete.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
6:00 PM 10/28/2009 problem still continues in Chino Hills, Ca.
Tracing route to www.l.google.com [74.125.19.99]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 8 ms 6 ms 7 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
3 286 ms 282 ms 281 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 303 ms 305 ms 266 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 236 ms 236 ms 239 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 11 ms 12 ms 12 ms 0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
7 24 ms 24 ms 29 ms xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
8 250 ms 239 ms 252 ms ae-93-90.ebr3.LosAngeles1.Level3.net [4.69.144.244]
9 29 ms 34 ms 37 ms ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
10 250 ms 256 ms 245 ms ae-63-63.csw1.SanJose1.Level3.net [4.69.134.226]
11 251 ms 254 ms 252 ms ae-1-69.edge1.SanJose1.Level3.net [4.68.18.14]
12 299 ms 270 ms 314 ms GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
13 31 ms 19 ms 34 ms 209.85.251.98
14 282 ms 316 ms 327 ms nuq04s01-in-f99.1e100.net [74.125.19.99]
Trace complete.
Tracing route to e3002.b.akamaiedge.net [96.6.236.79]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 8 ms 7 ms 14 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
3 366 ms 359 ms 355 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 342 ms 330 ms 327 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 322 ms 424 ms 350 ms 0.so-6-0-0.XT2.LAX9.ALTER.NET [152.63.10.157]
6 369 ms 367 ms 359 ms 0.so-6-3-0.XT2.LAX7.ALTER.NET [152.63.112.69]
7 380 ms 372 ms 367 ms POS7-0.BR2.LAX7.ALTER.NET [152.63.112.149]
8 362 ms 361 ms 355 ms p64-6-1-3.r20.lsanca03.us.bb.gin.ntt.net [129.250.8.205]
9 361 ms 372 ms 402 ms as-0.r21.snjsca04.us.bb.gin.ntt.net [129.250.4.96]
10 405 ms 396 ms 375 ms po-4.r03.snjsca04.us.bb.gin.ntt.net [129.250.4.78]
11 400 ms 392 ms 429 ms a96-6-236-79.deploy.akamaitechnologies.com [96.6.236.79]
Trace complete.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello again... Here is another latency report from Chino/Chino Hills.... Test done at approx 8pm
Target Name: www.google.com
IP: 74.125.19.104
Date/Time: 10/28/2009 8:02:32 PM
1 3 ms 3 ms Wireless_Broadband_Router.home [192.168.1.1]
2 8 ms 8 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
3 471 ms 495 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 471 ms 498 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 475 ms 503 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 468 ms 523 ms 0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]
7 16 ms 10 ms xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
8 13 ms 15 ms ae-73-70.ebr3.LosAngeles1.Level3.net [4.69.144.116]
9 27 ms 30 ms ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
10 498 ms 538 ms ae-63-63.csw1.SanJose1.Level3.net [4.69.134.226]
11 19 ms 20 ms ae-1-69.edge1.SanJose1.Level3.net [4.68.18.14]
12 24 ms 18 ms GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
13 21 ms 524 ms [209.85.251.98]
14 494 ms 20 ms nuq04s01-in-f104.1e100.net [74.125.19.104]
Ping statistics for www.google.com
Packets: Sent = 2, Received = 2, Lost = 0 (0.0%)
Round Trip Times: Minimum = 20ms, Maximum = 494ms, Average = 257ms
SIGH!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!