Just a little update, I also recieved a new router; however, I am still recieving 1 - 3 Mbps on my 25 mbps plan. I have contacted Verizon a numerous of times with no luck. I also live in the Long Beach area.
Could you guys who are seeing issues post some Traceroutes to Google or youtube.com for us to see? This might be what we see on the Northeast part of Verizon's network every now and again with Google's peering in New York City getting saturated at night.
Here's the Trace Route
Tracing route to www.l.google.com [74.125.239.20] over a maximum of 30 hops: 1 <1 ms 2 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1] 2 141 ms 7 ms 4 ms L100.LSANCA-VFTTP-118.verizon-gni.net [edited for privacy] .1] 3 11 ms 8 ms 8 ms G0-5-3-2.LSANCA-LCR-22.verizon-gni.net [130.81.5 5.25] 4 8 ms 7 ms 8 ms so-3-1-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81 .199.40] 5 9 ms 8 ms 8 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125] 6 9 ms 9 ms 11 ms TenGigE0-5-0-0.GW4.LAX15.ALTER.NET [152.63.112.7 7] 7 56 ms 59 ms 59 ms google-gw.customer.alter.net [63.125.112.154] 8 11 ms 13 ms 15 ms 64.233.174.238 9 9 ms 9 ms 10 ms 216.239.43.148 10 9 ms 9 ms 8 ms lax04s09-in-f20.1e100.net [74.125.239.20] Trace complete.
Tracing route to www.l.google.com [74.125.224.244] over a maximum of 30 hops: 1 2 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1] 2 53 ms 65 ms 72 ms L100.LSANCA-VFTTP-118.verizon-gni.net [edited for privacy] 3 68 ms * 72 ms G0-5-3-2.LSANCA-LCR-22.verizon-gni.net [130.81.5 5.25] 4 58 ms 15 ms * so-6-0-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81 .29.126] 5 64 ms 74 ms 75 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125] 6 104 ms 47 ms 25 ms TenGigE0-5-2-0.GW4.LAX15.ALTER.NET [152.63.115.1 90] 7 28 ms 67 ms 88 ms google-gw.customer.alter.net [63.125.112.154] 8 64 ms 90 ms 15 ms 216.239.46.40 9 45 ms 60 ms 62 ms 216.239.43.76 10 35 ms 51 ms 11 ms lax04s08-in-f20.1e100.net [74.125.224.244] Trace complete.
I am also in the long beach area, my service was just installed about 3 weeks ago, I have a new router new everything it worked great at first, now its slow slow slow 😞
Tracing route to www.l.google.com [74.125.224.244]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms myrouter.home [192.168.1.1]
2 121 ms 4 ms 4 ms L100.LSANCA-VFTTP-118.verizon-gni.net Privacy
3 7 ms 7 ms 7 ms G0-5-3-2.LSANCA-LCR-22.verizon-gni.net [130.81.5
5.25]
4 7 ms 8 ms 8 ms so-3-1-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81
.199.40]
5 8 ms 8 ms 8 ms 0.so-2-1-0.XT2.LAX7.ALTER.NET [152.63.10.149]
6 8 ms * 8 ms 0.ge-2-0-0.XL4.LAX15.ALTER.NET [152.63.2.86]
7 9 ms 9 ms 9 ms TenGigE0-7-4-0.GW4.LAX15.ALTER.NET [152.63.114.2
33]
8 59 ms 59 ms 59 ms google-gw.customer.alter.net [63.125.112.154]
9 23 ms * 8 ms 216.239.46.40
10 11 ms 8 ms 8 ms 216.239.43.76
11 8 ms 8 ms 8 ms lax04s08-in-f20.1e100.net [74.125.224.244]
Trace complete.
So I guess no one from Verizon gives a **bleep** about our problem. I'll just switch back to Charter for my internet.
@lilpenny911 wrote:So I guess no one from Verizon gives a **bleep** about our problem. I'll just switch back to Charter for my internet.
This forum isn't exactly intended by Verizon for Customer to Verizon support. That's what phone and live chat is for, as much as Verizon does offer some support here.
Your traces are showing up just fine. Pretty much solid, minus the blip at the edge router which can be normal, up until you get the peering router between Google and Verizon where the latency suggests that router is under load (but it might also be on low priority too). There is some packet loss showing up on ALTER.NET which would be Verizon's Backbone when you arrive at the Los Angeles Internet Exchange, however without running a WinMTR or MTR trace I can't say for sure if those hops are problematic or if there's something else causing issues. I'm betting you this is an issue with Google's peering being shoddy again as it was in the Northeast for quite some time on many providers. Keep in mind, Google does run their own network but their properties are among the most visited in the world. It's not uncommon for peering to be saturated with them. It's just like how common it is to see Facebook running slow (and it really does away from all of their Javascript). Huge site, just not enough capacity.
As far as the trace for BiggRed12, it looks like his FiOS connection is being saturated by something so I cannot pick out a good indication with that kind of traceroute. For as far as I'm concerned, unless the trace looks a lot cleaner there's something on his end or more local to him than something out on Google's end or the handoff to Google from Verizon.
After talking to a few more workers in tech support, I've come to understand that there is a line cut in the Chino area which I believe is near San Bernadino. As a result, all of the people who would have lost service have been piggy backed onto other servers normally used by those in the LA and Long Beach areas. Given the setup of FIOS, every "line" can only hold a certain amount of people so it seems it was a decision to have many people with slow internet than some without Internet while they continue to work on repairs.
However for some if not most of us, this has nearly been going on for 2 weeks and makes me wonder how much damage there actually is. I plan on calling again to find out more information, but I was placed in an "outtage" group they are managing. I shall inform with any new information I receive about this issue.
Tracing route to www.l.google.com [74.125.224.209] over a maximum of 30 hops: 1 2 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1] 2 5 ms 3 ms 3 ms L100.LSANCA-VFTTP-118.verizon-gni.net [Edited for privacy] 3 9 ms 9 ms 9 ms G0-5-3-3.LSANCA-LCR-21.verizon-gni.net [130.81.1 82.138] 4 132 ms 59 ms 9 ms so-6-0-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81 .29.124] 5 10 ms 9 ms 9 ms 0.so-7-3-0.XT1.LAX7.ALTER.NET [152.63.10.145] 6 10 ms 9 ms 9 ms 0.xe-3-0-3.XL3.LAX15.ALTER.NET [152.63.114.66] 7 9 ms 9 ms 9 ms TenGigE0-6-0-0.GW4.LAX15.ALTER.NET [152.63.114.2 05] 8 10 ms 9 ms 10 ms google-gw.customer.alter.net [63.125.112.154] 9 21 ms 8 ms 8 ms 216.239.46.40 10 11 ms 10 ms 10 ms 72.14.236.13 11 9 ms 10 ms 11 ms lax02s02-in-f17.1e100.net [74.125.224.209] Trace complete.
Don't know if this helps, but I ran another tracer test.
That does make some sense. The new trace you posted is a bit better. Besides the spike in the Alter.net link that trace is pretty clean all the way to Google's web server farm for your region. With a trace like that the problem would be due to video server cache replication or load issues at that point.
Start a new topic or ask questions in the open forum.
