Choose your cart
Choose your cart
Receive up to $504 promo credit ($180 w/Welcome Unlimited, $360 w/ 5G Start, or $504 w/5G Do More, 5G Play More, 5G Get More or One Unlimited for iPhone plan (Welcome Unlimited and One Unlimited for iPhone plans can't be mixed w/other Unlimited plans; all lines on the account req'd on respective plans)) when you add a new smartphone line with your own 4G/5G smartphone on an eligible postpaid plan between 2/10/23 and 4/5/23. Promo credit applied over 36 months; promo credits end if eligibility requirements are no longer met.
$699.99 (128 GB only) device payment purchase or full retail purchase w/ new smartphone line on One Unlimited for iPhone (all lines on account req'd on plan), 5G Start, 5G Do More, 5G Play More or 5G Get More plan req'd. Less $699.99 promo credit applied over 36 mos.; promo credit ends if eligibility req’s are no longer met; 0% APR.
Well looks like it's back again(at least on my end). Nothing has changed on my end, was good for awhile, but starting around 4pm today it's getting out of hand again.
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 239 ms 433 ms 287 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
3 31 ms 6 ms 9 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.140.122]
4 249 ms 158 ms 134 ms so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.29.244]
5 256 ms 363 ms 342 ms 0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
6 357 ms 295 ms 307 ms 0.ge-7-0-0.XT1.SAC1.ALTER.NET [152.63.49.89]
7 334 ms 320 ms 318 ms GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.
55.73]
8 170 ms 187 ms 176 ms verizon-gw.customer.alter.net [157.130.203.246]
9 296 ms 241 ms 266 ms 192.76.84.5
10 * * * Request timed out.
6:45pm
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 3 ms 4 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
3 22 ms 17 ms 6 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.140.122]
4 555 ms 422 ms 147 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 20 ms 20 ms 21 ms 0.ge-7-0-0.XT1.SAC1.ALTER.NET [152.63.49.89]
7 22 ms 22 ms 22 ms GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.
55.73]
8 70 ms 39 ms 24 ms verizon-gw.customer.alter.net [157.130.203.246]
9 70 ms 27 ms 77 ms 192.76.84.5
10 * * * Request timed out.
7:45pm
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 689 ms 816 ms 782 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
3 805 ms 746 ms 805 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.140.122]
4 825 ms 683 ms 800 ms so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.29.244]
5 527 ms 767 ms 641 ms 0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
6 790 ms 793 ms 802 ms 0.ge-7-0-0.XT1.SAC1.ALTER.NET [152.63.49.89]
7 867 ms 922 ms 879 ms GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.
55.73]
8 896 ms 904 ms 924 ms verizon-gw.customer.alter.net [157.130.203.246]
9 983 ms 773 ms 675 ms 192.76.84.5
10 * * * Request timed out.
I seem to be getting much better numbers. You still having trouble?
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 6 ms 7 ms 7 ms L100.LSANCA-VFTTP-142.verizon-gni.net
3 9 ms 9 ms 10 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
4 10 ms 12 ms 9 ms so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
5 10 ms 9 ms 10 ms 0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
6 22 ms 22 ms 21 ms 0.ge-7-0-0.XT1.SAC1.ALTER.NET [152.63.49.89]
7 24 ms 27 ms 24 ms GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.55.73]
8 28 ms 23 ms 27 ms verizon-gw.customer.alter.net [157.130.203.246]
9 27 ms 27 ms 27 ms 192.76.84.5
10 * * * Request timed out.
Bad here also -- note that this is only an issue for LSANCA-LCR-12, which is at hop #3. Osler, you are luckily showing LCR-11 and not LCR-12, I wonder what is causing the route to choose one or the other.
Here's my traceroute as of 3:45pm today (Thurs. Nov 5):
1 myrouter (192.168.1.1) 0.927 ms 0.369 ms 0.479 ms
2 l100.lsanca-vfttp-142.verizon-gni.net (173.55.53.1) 8.485 ms 6.646 ms 7.227 ms
3 g4-0-6-1242.lsanca-lcr-12.verizon-gni.net (130.81.140.162) 575.924 ms 566.769 ms 557.9ms
4 so-4-3-0-0.lax01-bb-rtr2.verizon-gni.net (130.81.29.246) 580.083 ms 562.069 ms 577.920 ms
5 0.so-1-2-0.xl4.lax15.alter.net (152.63.10.125) 569.840 ms 544.338 ms 547.380 ms
6 0.ge-6-1-0.br2.lax15.alter.net (152.63.116.153) 9.706 ms 9.621 ms 9.724 ms
7 xe-10-1-0.edge1.losangeles9.level3.net (4.68.63.129) 559.940 ms 539.299 ms 552.916 ms
8 ae-73-70.ebr3.losangeles1.level3.net (4.69.144.116) 567.159 ms
ae-93-90.ebr3.losangeles1.level3.net (4.69.144.244) 9.608 ms
ae-63-60.ebr3.losangeles1.level3.net (4.69.144.52) 14.141 ms
9 * ae-2.ebr3.sanjose1.level3.net (4.69.132.9) 559.428 ms 537.061 ms
10 ae-83-83.csw3.sanjose1.level3.net (4.69.134.234) 29.698 ms 19.134 ms 19.976 ms
11 ae-3-89.edge1.sanjose1.level3.net (4.68.18.142) 20.224 ms
ae-4-99.edge1.sanjose1.level3.net (4.68.18.206) 19.368 ms 17.132 ms
12 google-inc.edge1.sanjose1.level3.net (4.79.43.146) 522.965 ms 529.839 ms 535.237 ms
13 209.85.251.98 (209.85.251.98) 557.310 ms 564.551 ms 571.903 ms
14 nuq04s01-in-f103.1e100.net (74.125.19.103) 545.158 ms 536.577 ms 524.903 ms
I've highlighted the bad hop in red.
I was experiencing great speed again, but it only lasted for a few days.... maybe in the late evening the route uses LCR-11 only. Something tells me, they need to retire LCR-12 instead of simply rebooting it.
Verizon/Brett - if you're monitoring the boards, HELP!
Neil
The high latency is back again...sigh
tracert www.verizon.com
Tracing route to a1280.g.akamai.net [63.80.138.75]
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 538 ms 534 ms 537 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.8
1.140.162]
4 551 ms 534 ms 517 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81
.29.246]
5 551 ms 584 ms 574 ms 0.so-6-2-0.XT2.LAX7.ALTER.NET [152.63.112.49]
6 575 ms 554 ms 557 ms 0.so-5-2-0.XL4.SJC7.ALTER.NET [152.63.48.2]
7 526 ms 524 ms 19 ms TenGigE0-7-2-0.GW3.SJC7.ALTER.NET [152.63.50.57]
8 531 ms 549 ms 567 ms 63.80.138.75
Trace complete.
same here,
5:25pm 11/5/2009 Chino Hills
lag is very bad
tracert to google.com and verizon.com as following:
Tracing route to www.l.google.com [74.125.19.103]
over a maximum of 30 hops:
1 4 ms 2 ms 2 ms L300.LSANCA-VFTTP-142.verizon-gni.net [71.254.182.1]
2 5 ms 4 ms 4 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.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 5 ms 4 ms 4 ms 0.so-1-2-0.XL3.LAX15.ALTER.NET [152.63.10.133]
5 8 ms 824 ms 6 ms 0.ge-6-0-0.BR2.LAX15.ALTER.NET [152.63.116.149]
6 853 ms 821 ms 6 ms xe-11-0-0.edge1.SanJose3.level3.net [4.68.111.249]
7 18 ms 812 ms 818 ms ae-83-80.ebr3.LosAngeles1.Level3.net [4.69.144.180]
8 16 ms 15 ms 17 ms ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
9 925 ms 921 ms 818 ms ae-83-83.csw3.SanJose1.Level3.net [4.69.134.234]
10 831 ms 819 ms 818 ms ae-3-89.edge1.SanJose1.Level3.net [4.68.18.142]
11 17 ms 16 ms 15 ms GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
12 21 ms 20 ms 15 ms 209.85.251.98
13 858 ms 818 ms 819 ms nuq04s01-in-f103.1e100.net [74.125.19.103]
Trace complete.
C:\>tracert www.verizon.com
Tracing route to a1280.g.akamai.net [63.80.4.59]
over a maximum of 30 hops:
1 25 ms 23 ms 27 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 8 ms 6 ms 5 ms 0.so-6-3-0.XT1.LAX9.ALTER.NET [152.63.10.153]
5 18 ms 15 ms 16 ms 0.ge-7-1-0.XL3.SJC7.ALTER.NET [152.63.48.254]
6 937 ms 919 ms 921 ms TenGigE0-6-1-0.GW3.SJC7.ALTER.NET [152.63.50.25]
7 856 ms 921 ms 921 ms 63.80.4.59
Trace complete.
Well, I had a couple of days of good speed, but now seeing the same problem again. I guess I got lucky on my routing for a short time. My tracert to verizon.com and google.com follow, as well as to the World of Warcraft / battle.net server, which shows terrible latency!
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 33 ms 34 ms 27 ms L100.LSANCA-VFTTP-142.verizon-gni.net
3 9 ms 9 ms 10 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
4 10 ms 10 ms 9 ms so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
5 8 ms 10 ms 9 ms 0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
6 21 ms 21 ms 23 ms 0.ge-7-0-0.XT1.SAC1.ALTER.NET [152.63.49.89]
7 584 ms 607 ms 555 ms GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.55.73]
8 566 ms 592 ms 590 ms verizon-gw.customer.alter.net [157.130.203.246]
9 602 ms 584 ms 602 ms 192.76.84.5
10 * * * Request timed out.
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 6 ms 6 ms 10 ms L100.LSANCA-VFTTP-142.verizon-gni.net
3 532 ms 546 ms 527 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 567 ms 552 ms 564 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 585 ms 559 ms 567 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 13 ms 12 ms 12 ms 0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
7 577 ms 580 ms 589 ms 192.205.35.161
8 702 ms 663 ms 665 ms cr2.la2ca.ip.att.net [12.123.30.134]
9 68 ms 77 ms 64 ms cr2.dlstx.ip.att.net [12.122.28.177]
10 66 ms 67 ms 66 ms cr1.attga.ip.att.net [12.122.28.173]
11 637 ms 663 ms 645 ms 12.123.22.5
12 78 ms 76 ms 74 ms 12.88.97.6
13 76 ms 71 ms 72 ms 72.14.233.56
14 692 ms 714 ms 711 ms 209.85.254.247
15 761 ms 719 ms 724 ms 209.85.255.190
16 67 ms 67 ms 67 ms gw-in-f100.1e100.net [74.125.67.100]
Trace complete.
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 6 ms 8 ms 6 ms L100.LSANCA-VFTTP-142.verizon-gni.net
3 603 ms 607 ms 626 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 593 ms 622 ms 647 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 646 ms 636 ms 612 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 12 ms 12 ms 12 ms 0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
7 635 ms 604 ms 619 ms 192.205.35.161
8 639 ms 17 ms 619 ms cr2.la2ca.ip.att.net [12.123.30.134]
9 592 ms 564 ms 19 ms cr84.la2ca.ip.att.net [12.123.30.249]
10 8 ms 12 ms 12 ms gar5.la2ca.ip.att.net [12.122.129.25]
11 22 ms 24 ms 19 ms 12.122.255.74
12 547 ms 549 ms 557 ms 12.129.193.246
13 12.129.211.36 reports: Destination net unreachable.
Trace complete.
... not LSANCA-LCR-12, which is also bad per the above posts, but a SECOND bad switch:
1 myrouter (192.168.1.1) 0.827 ms 0.383 ms 0.483 ms
2 l100.lsanca-vfttp-142.verizon-gni.net (173.55.53.1) 8.235 ms 6.726 ms 7.478 ms
3 g4-0-6-1142.lsanca-lcr-11.verizon-gni.net (130.81.140.122) 9.733 ms 9.104 ms 10.234 ms
4 so-4-3-0-0.lax01-bb-rtr1.verizon-gni.net (130.81.29.244) 9.751 ms 9.355 ms 9.754 ms
5 0.so-1-2-0.xl3.lax15.alter.net (152.63.10.133) 12.454 ms 9.080 ms 10.234 ms
6 0.ge-6-0-0.br2.lax15.alter.net (152.63.116.149) 866.997 ms
0.ge-7-0-0.br2.lax15.alter.net (152.63.116.157) 876.384 ms 886.868 ms
7 xe-10-1-0.edge1.losangeles9.level3.net (4.68.63.129) 914.650 ms
xe-11-0-0.edge1.sanjose3.level3.net (4.68.111.249) 9.117 ms
xe-10-1-0.edge1.losangeles9.level3.net (4.68.63.129) 911.654 ms
8 ae-93-90.ebr3.losangeles1.level3.net (4.69.144.244) 8.963 ms 14.790 ms
ae-83-80.ebr3.losangeles1.level3.net (4.69.144.180) 912.969 ms
9 ae-2.ebr3.sanjose1.level3.net (4.69.132.9) 872.139 ms 826.294 ms 795.012 ms
10 ae-83-83.csw3.sanjose1.level3.net (4.69.134.234) 20.164 ms 31.286 ms 19.969 ms
11 ae-3-89.edge1.sanjose1.level3.net (4.68.18.142) 19.980 ms 19.381 ms 19.976 ms
12 google-inc.edge1.sanjose1.level3.net (4.79.43.146) 838.029 ms 852.378 ms 844.716 ms
13 209.85.251.98 (209.85.251.98) 817.189 ms 861.354 ms 820.013 ms
14 nuq04s01-in-f106.1e100.net (74.125.19.106) 820.000 ms 786.438 ms 803.271 ms
So check your traceroutes, it will be a problem on Hop #3 (earlier posts by others), or Hope #5 (the one in this post).
Neil
It's BACK!!!!
Chino Hills, Ca. 6:40 PM.
Very frustrating...
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 9 ms 7 ms 7 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
3 1040 ms 999 ms 967 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 921 ms 932 ms 929 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 926 ms 959 ms 919 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 13 ms 12 ms 11 ms 0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
7 13 ms 12 ms 12 ms xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
8 20 ms 17 ms 16 ms ae-73-70.ebr3.LosAngeles1.Level3.net [4.69.144.116]
9 19 ms 32 ms 34 ms ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
10 29 ms 19 ms 19 ms ae-73-73.csw2.SanJose1.Level3.net [4.69.134.230]
11 983 ms 1009 ms 1070 ms ae-2-79.edge1.SanJose1.Level3.net [4.68.18.78]
12 1054 ms 1049 ms 1017 ms GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
13 28 ms 19 ms 19 ms 209.85.251.98
14 973 ms 987 ms 979 ms nuq04s01-in-f147.1e100.net [74.125.19.147]
Trace complete.
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 8 ms 7 ms 7 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
3 936 ms 945 ms 952 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 983 ms 1050 ms 989 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 1019 ms 1044 ms 1052 ms 130.81.17.27
6 49 ms 47 ms 47 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 47 ms 47 ms po1.ctn-border1.vzlink.com [206.46.225.85]
9 997 ms 970 ms 979 ms po121.ctn-core1.vzlink.com [206.46.225.18]
10 47 ms 47 ms 49 ms 206.46.228.130
11 84 ms 46 ms 47 ms 206.46.232.39
Trace complete.
Please fix permanently!