- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Haha, thanks for the good news Brett! Hope this gets solved very soon!
However, it seems that a lot of people from Chino Hills are getting this issue.... is this significant to the problem?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Following are new tracert to the 2 servers I posted earlier. The numbers have improved but I am still getting average in-game latency of ~400ms in World of Warcraft. A definite improvement from the last 2 weeks but still nowhere as good as previous to that.
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{edited for privacy}
3 242 ms 254 ms 257 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 271 ms 284 ms 294 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 316 ms 344 ms 317 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 11 ms 12 ms 10 ms 0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
7 338 ms 329 ms 314 ms 192.205.35.161
8 296 ms 299 ms 12 ms cr1.la2ca.ip.att.net [12.123.30.6]
9 11 ms 10 ms 9 ms gar4.la2ca.ip.att.net [12.122.128.169]
10 11 ms 12 ms 12 ms 12.122.255.70
11 351 ms 339 ms 352 ms 12.129.193.254
12 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 12 ms 8 ms 6 ms L100.LSANCA-VFTTP-142.verizon-gni.net {edited for privacy}
3 276 ms 289 ms 294 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 264 ms 259 ms 274 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 318 ms 317 ms 317 ms 0.so-6-0-0.XT2.LAX9.ALTER.NET [152.63.10.157]
6 299 ms 307 ms 308 ms 0.so-6-3-0.XT2.LAX7.ALTER.NET [152.63.112.69]
7 272 ms 272 ms 263 ms GigabitEthernet7-0-0.GW7.LAX7.ALTER.NET [152.63.118.53]
8 14 ms 17 ms 16 ms pvhmc-gw.customer.alter.net [157.130.233.98]
9 16 ms 17 ms 16 ms vpn.pvhmc.org [65.218.207.68]
Trace complete.
Tracert for verizon.net and google.com also, in case they help:
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 9 ms 24 ms 8 ms L100.LSANCA-VFTTP-142.verizon-gni.net {edited for privacy}
3 20 ms 9 ms 23 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
4 10 ms 10 ms 20 ms so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
5 48 ms 54 ms 47 ms so-3-3-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.19.18]
6 48 ms 55 ms 48 ms so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
7 47 ms 50 ms 51 ms po1.ctn-border1.vzlink.com [206.46.225.85]
8 47 ms 52 ms 66 ms po121.ctn-core1.vzlink.com [206.46.225.18]
9 52 ms 53 ms 46 ms 206.46.228.130
10 58 ms 61 ms 47 ms 206.46.232.39
Trace complete.
Tracing route to google.com [74.125.45.100]
over a maximum of 30 hops:
1 17 ms <1 ms <1 ms myrouter.home [192.168.1.1]
2 15 ms 6 ms 25 ms L100.LSANCA-VFTTP-142.verizon-gni.net{edited for privacy}
3 203 ms 221 ms 198 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 217 ms 235 ms 226 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 250 ms 242 ms 252 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 17 ms 12 ms 20 ms 0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]
7 237 ms 221 ms 219 ms 192.205.35.161
8 260 ms 268 ms 285 ms cr2.la2ca.ip.att.net [12.123.30.134]
9 70 ms 87 ms 66 ms cr2.dlstx.ip.att.net [12.122.28.177]
10 94 ms 93 ms 97 ms cr1.attga.ip.att.net [12.122.28.173]
11 256 ms 259 ms 286 ms 12.123.22.5
12 68 ms 69 ms 70 ms 12.88.97.6
13 97 ms 70 ms 76 ms 72.14.233.56
14 106 ms 291 ms 294 ms 209.85.254.241
15 68 ms 288 ms 71 ms 209.85.253.137
16 75 ms 85 ms 85 ms yx-in-f100.1e100.net [74.125.45.100]
Trace complete.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4:00pm
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 5 ms 4 ms 5 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
3 6 ms 8 ms 7 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.140.122]
4 8 ms 6 ms 7 ms so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.29.244]
5 9 ms 8 ms 7 ms 0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
6 21 ms 21 ms 19 ms 0.ge-7-0-0.XT1.SAC1.ALTER.NET [152.63.49.89]
7 192 ms 181 ms 182 ms GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.
55.73]
8 163 ms 220 ms 236 ms verizon-gw.customer.alter.net [157.130.203.246]
9 194 ms 211 ms 213 ms 192.76.84.5
10 * * * Request timed out.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Things are horrible again. Surfing is slow, son is telling me that online games are unplayable because of the "lag"
Hope this helps getting this issue fixed.
5:00p
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 5 ms 4 ms 5 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
3 8 ms 7 ms 6 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.140.122]
4 6 ms 7 ms 7 ms so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.29.244]
5 7 ms 7 ms 8 ms 0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
6 35 ms 22 ms 20 ms 0.ge-7-0-0.XT1.SAC1.ALTER.NET [152.63.49.89]
7 501 ms 504 ms 519 ms GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.
55.73]
8 521 ms 523 ms 518 ms verizon-gw.customer.alter.net [157.130.203.246]
9 520 ms 484 ms 464 ms 192.76.84.5
10 * * * Request timed out.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I was hopeful this morning since things seemed better but unfortunately the problem has returned again this evening. Makes me think this is due to load / congestion.
Tracing route to e3002.b.akamaiedge.net [96.6.60.79]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 7 ms 8 ms 7 ms l100.lsanca-vfttp-142.verizon-gni.net [173.55.53.1]
3 284 ms 295 ms 281 ms g4-0-6-1242.lsanca-lcr-12.verizon-gni.net [130.81.140.162]
4 293 ms 309 ms 292 ms so-4-3-0-0.lax01-bb-rtr2.verizon-gni.net [130.81.29.246]
5 304 ms 297 ms 292 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 317 ms 330 ms 319 ms 0.so-7-3-0.XT2.LAX7.ALTER.NET [152.63.112.62]
7 314 ms 294 ms 302 ms 0.so-7-0-0.BR1.LAX7.ALTER.NET [152.63.112.153]
8 35 ms 34 ms 37 ms 204.255.168.34
9 247 ms 243 ms 271 ms los-core-02.inet.qwest.net [205.171.32.13]
10 53 ms 54 ms 79 ms los-edge-01.inet.qwest.net [205.171.32.46]
11 41 ms 41 ms 42 ms a96-6-60-79.deploy.akamaitechnologies.com [96.6.60.79]
Trace complete.
Also, I get bad lag for servers back east (LOTRO.COM). But the latency spike is **bleep**her down stream.
Tracing route to gls.lotro.com [206.16.13.82]
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 7 ms l100.lsanca-vfttp-142.verizon-gni.net [173.55..1]
3 10 ms 10 ms 9 ms g4-0-6-1142.lsanca-lcr-11.verizon-gni.net [1301.140.122]
4 9 ms 10 ms 9 ms so-4-3-0-0.lax01-bb-rtr1.verizon-gni.net [130..29.244]
5 9 ms 12 ms 10 ms 0.so-1-2-0.XL3.LAX15.ALTER.NET [152.63.10.133]
6 13 ms 12 ms 12 ms 0.ge-7-0-0.BR2.LAX15.ALTER.NET [152.63.116.157
7 11 ms 12 ms 11 ms 192.205.35.161
8 415 ms 429 ms 422 ms cr2.la2ca.ip.att.net [12.123.30.134]
9 416 ms 435 ms 442 ms cr1.slkut.ip.att.net [12.122.30.29]
10 437 ms 430 ms 459 ms cr2.dvmco.ip.att.net [12.122.30.26]
11 490 ms 451 ms 439 ms cr1.cgcil.ip.att.net [12.122.31.86]
12 464 ms 449 ms 447 ms cr2.cgcil.ip.att.net [12.122.2.54]
13 463 ms 467 ms 426 ms cr1.n54ny.ip.att.net [12.122.1.1]
14 421 ms 417 ms 432 ms cr2.n54ny.ip.att.net [12.122.2.14]
15 432 ms 447 ms 459 ms cr1.cb1ma.ip.att.net [12.122.31.126]
16 455 ms 454 ms 439 ms gar5.cb1ma.ip.att.net [12.122.145.29]
17 461 ms 447 ms 419 ms 12-122-254-14.attens.net [12.122.254.14]
18 459 ms 447 ms 424 ms mdf001c7613r0004-gig-12-1.bos1.attens.net [12.
0.0.174]
19 458 ms 472 ms 450 ms 12.130.10.69
20 440 ms 465 ms 459 ms 206.16.13.82
Trace complete.
Please help us and resolve this as soon as possible. .
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi gang,
As promised, here's the result of the evening traceroute at 5:30pm PST. Predictably, lsanca-lcr-12.verizon-gni.net (130.81.140.162) has returned and is wreaking havoc with latency: 430ms ping times.
......
1 myrouter (192.168.1.1) 0.629 ms 0.375 ms 0.488 ms
2 l100.lsanca-vfttp-142.verizon-gni.net (173.55.53.1) 6.995 ms 6.877 ms 7.219 ms
3 g4-0-6-1242.lsanca-lcr-12.verizon-gni.net (130.81.140.162) 437.784 ms 429.885 ms 416.979 ms
4 so-4-3-0-0.lax01-bb-rtr2.verizon-gni.net (130.81.29.246) 424.980 ms 422.137 ms 421.965 ms
5 0.so-1-2-0.xl4.lax15.alter.net (152.63.10.125) 430.175 ms 444.371 ms 409.696 ms
6 0.ge-6-1-0.br2.lax15.alter.net (152.63.116.153) 37.936 ms 39.381 ms 41.933 ms
7 xe-10-1-0.edge1.losangeles9.level3.net (4.68.63.129) 402.519 ms 428.860 ms 408.240 ms
8 ae-83-80.ebr3.losangeles1.level3.net (4.69.144.180) 429.469 ms
ae-63-60.ebr3.losangeles1.level3.net (4.69.144.52) 31.800 ms
ae-73-70.ebr3.losangeles1.level3.net (4.69.144.116) 424.073 ms
9 ae-2.ebr3.sanjose1.level3.net (4.69.132.9) 452.389 ms 433.865 ms 410.502 ms
10 ae-63-63.csw1.sanjose1.level3.net (4.69.134.226) 407.252 ms 417.010 ms 420.001 ms
11 ae-1-69.edge1.sanjose1.level3.net (4.68.18.14) 397.239 ms 371.884 ms 404.529 ms
12 google-inc.edge1.sanjose1.level3.net (4.79.43.146) 402.939 ms 394.159 ms 394.988 ms
13 209.85.251.98 (209.85.251.98) 399.983 ms 424.657 ms 419.952 ms
14 nuq04s01-in-f103.1e100.net (74.125.19.103) 454.476 ms 437.089 ms 449.736 ms
......
- Before 5pm: LCR-11 is active at Hop #3: this switch works (ping is acceptable)
- After 5pm: LCR-12 instead at Hop #3: this switch is NOT working
The equipment activated at Hop #3 in the morning is DIFFERENT from the equipment being used in the route at Hop #3 in the evening.
The morning route has its own issue, namely LAX15.ALTER.NET (152.63.116.157) at Hop #6, which increases ping to ~200ms and higher.
Brett, if you're addressing one thing at a time, here's the suggestion: 1) fix LCR-12 first; then 2) fix LAX15 next.
Neil
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
6:00pm
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 5 ms 4 ms 5 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
3 7 ms 7 ms 7 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.140.122]
4 7 ms 8 ms 7 ms so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.29.244]
5 8 ms 9 ms 9 ms 0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
6 20 ms 22 ms 20 ms 0.ge-7-0-0.XT1.SAC1.ALTER.NET [152.63.49.89]
7 426 ms 430 ms 452 ms GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.
55.73]
8 423 ms 407 ms 418 ms verizon-gw.customer.alter.net [157.130.203.246]
9 392 ms 377 ms 364 ms 192.76.84.5
10 * * * Request timed out.
=/
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well I called verizon technical support to see if there was any update on my ticket and as expected they are telling me I don't have a problem, and that I need to have my RWIN increased (meaning I need to install their new optimization software in order to improve my network performance). This is a complete load of garbage as we all know.
I'm EXTREMELY disastisfied with verizon technical support (Brett and team are excluded of course you've been very helpful). I have been very patient up until tonight, I have not yelled or complained. But tonight I had enough and demanded to speak with a supervisor. They transfered me to an excalation manager who answered and then hung up on me. This is the second time I have been hung up on by someone at Verizon. I find it hard to believe that Verizon employees are that incompetent with the operation of a telephone so I can only conclude that i'm being intentionally hung up on.
I'm now looking for alternative ISPs to resolve this problem. It will take a long time to select and setup new service so if this gets resolved in a relatively short time then I'll probably stay since up until now I have been very satisfied with FIOS.
What frustrates me is I was trying to direct the Verizon technician to this support forum to try and prove this is not a problem that is isoloated to me but he just refused and kept repeating my RWIN should be at 9000 and I need to install software in order to get good performance with FIOS.
I then said "Are you telling me that in order for me to recieved broadband service with FIOS I know need to install this software?" and he said "Yes"!
That's when I escalated...
Sorry for the rant...I'm just **bleep**, this impacts my ability to work from home and the online classes I'm taking.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
From chino hills... this is my latest trace. as you can see, the network latency issue is NOT FIXED. It is getting very frustrating dealing with this and talking to FIOS support coz they don't seem to want to do anything about it. Not sure what part of ' several Chino Hills resident's are having the same problem' don't they understand. It's not a PC, router, config on our side but it's their so called 'FIBER' optic network that is messed up. It's been 2 weeks now and nothing!!!
$ tracert latimes.com
Tracing route to latimes.com [144.142.224.43]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 3 ms 3 ms 3 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
3 501 ms 518 ms 537 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 548 ms 556 ms 535 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 506 ms 532 ms 537 ms 0.so-6-2-0.XT2.LAX7.ALTER.NET [152.63.112.49]
6 507 ms 513 ms 516 ms 0.so-7-0-0.XL4.LAX15.ALTER.NET [152.63.112.61]
7 516 ms 508 ms 511 ms POS7-0-0.GW3.LAX15.ALTER.NET [152.63.112.109]
8 11 ms 11 ms 11 ms internapGIGE-gw.customer.alter.net [157.130.236.110]
9 21 ms 22 ms 22 ms border21.po1-20g-bbnet1.lax.pnap.net [216.52.255.38]
10 * * * Request timed out.
11 484 ms 469 ms 491 ms secure.latimes.com [144.142.224.43]
Trace complete.
$ 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 3 ms 3 ms 3 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
3 431 ms 458 ms 435 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 459 ms 441 ms 423 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 488 ms 421 ms 412 ms 130.81.17.27
6 61 ms 56 ms 51 ms so-7-0-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.19.12]
7 42 ms 44 ms 37 ms so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
8 65 ms 57 ms 61 ms po1.ctn-border1.vzlink.com [206.46.225.85]
9 413 ms 417 ms 418 ms po121.ctn-core1.vzlink.com [206.46.225.18]
10 390 ms 406 ms 387 ms 206.46.228.130
11 53 ms 59 ms 57 ms 206.46.232.39
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
7:00pm
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 5 ms 7 ms 5 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
3 7 ms 6 ms 7 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.140.122]
4 9 ms 9 ms 9 ms so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.29.244]
5 7 ms 8 ms 7 ms 0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
6 20 ms 20 ms 20 ms 0.ge-7-0-0.XT1.SAC1.ALTER.NET [152.63.49.89]
7 651 ms 639 ms 633 ms GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.
55.73]
8 660 ms 675 ms 690 ms verizon-gw.customer.alter.net [157.130.203.246]
9 622 ms 627 ms 599 ms 192.76.84.5
10 * * * Request timed out.