dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
4305
share rss forum feed


FutureX2001

join:2000-10-25
Perris, CA
reply to andyjai

Re: [Southwest] Problem with Fios

I got 7mbps down 23mbps on that test on the 75/35 package. Also noticed the CSR stopped responding on the Verizon Direct forum for me...

spliffmaster

join:2000-09-19
Costa Mesa, CA
reply to andyjai
I have had issues for the last 2 weeks between 7pm-11pm EVERY night. I live in Long Beach, CA and have a 75/35 Verizon FIOS line.

During those times, I get at best 10/35. My upload is never affected..however I cannot game, or do much of anything with the 1000ms pings and major packet loss.

I have had it with Verizon and their terrible techs and unwillingness to admit there is a problem.

andyjai

join:2001-09-12
Rowland Heights, CA
reply to andyjai
Click for full size
Seems like Verizon fixed it on Tuesday night. All Los Angels Speedtest.net servers give me around 60-80Mbps Down and 30up. Http downloads maxed out my connection and youtube is able to stream fine now. But I still wonder why the Verzion standard speedtest still give me poor result, while their 100Mb test give me full speed.


Lloyd

@verizon.net
reply to andyjai
@VerizonSupport on Twitter mentioned last night that the ETA for the fix was 10:58 AM this morning. Things look a lot better now and I'm not seeing any significant packet loss on the sites that were having the problem last week.

andyjai

join:2001-09-12
Rowland Heights, CA
reply to andyjai
I did some googling and found that a few Los Angeles WoW players are having high ping issue. I don't play WoW, but i ran tracert and pathping to their server, and I think it is the same issue.

Tracing route to 12.129.209.68 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-113.verizon-gni.net [98.119.77.1]
  3     9 ms     7 ms     8 ms  G0-5-1-5.LSANCA-LCR-21.verizon-gni.net [130.81.182.224]
  4     7 ms     7 ms     9 ms  so-6-0-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.124]
  5    42 ms     *       42 ms  0.xe-9-0-0.BR3.LAX15.ALTER.NET [152.63.114.245]
  6     *        *       38 ms  204.255.168.134
  7    10 ms    34 ms     *     cr1.la2ca.ip.att.net [12.123.132.129]
  8   106 ms    31 ms     *     gar29.la2ca.ip.att.net [12.122.129.241]
  9    41 ms     9 ms     *     12-122-254-234.attens.net [12.122.254.234]
 10     9 ms    10 ms     8 ms  mdf001c7613r0002.lax1.attens.net [206.16.68.54]
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 
Tracing route to 12.129.209.68 over a maximum of 30 hops
 
  0  Win7-PC.home [192.168.1.168]
  1  Wireless_Broadband_Router.home [192.168.1.1]
  2  L100.LSANCA-VFTTP-113.verizon-gni.net [98.119.77.1]
  3  G0-5-1-5.LSANCA-LCR-21.verizon-gni.net [130.81.182.224]
  4  so-6-0-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.124]
  5  0.xe-9-0-0.BR3.LAX15.ALTER.NET [152.63.114.245]
  6     *     204.255.168.134
  7  cr2.la2ca.ip.att.net [12.123.30.134]
  8  gar29.la2ca.ip.att.net [12.122.129.241]
  9     *     12-122-254-234.attens.net [12.122.254.234]
 10  mdf001c7613r0002.lax1.attens.net [206.16.68.54]
 11     *        *        *
Computing statistics for 250 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Win7-PC.home [192.168.1.168]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  Wireless_Broadband_Router.home [192.168.1.1]
                                0/ 100 =  0%   |
  2    5ms     0/ 100 =  0%     0/ 100 =  0%  L100.LSANCA-VFTTP-113.verizon-gni.net [98.119.77.1]
                                0/ 100 =  0%   |
  3    8ms     0/ 100 =  0%     0/ 100 =  0%  G0-5-1-5.LSANCA-LCR-21.verizon-gni.net [130.81.182.224]
                                0/ 100 =  0%   |
  4   10ms     0/ 100 =  0%     0/ 100 =  0%  so-6-0-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.124]
                               14/ 100 = 14%   |
  5   22ms    14/ 100 = 14%     0/ 100 =  0%  0.xe-9-0-0.BR3.LAX15.ALTER.NET [152.63.114.245]
                               15/ 100 = 15%   |
  6   36ms    29/ 100 = 29%     0/ 100 =  0%  204.255.168.134
                               71/ 100 = 71%   |
  7  ---     100/ 100 =100%     0/ 100 =  0%  cr2.la2ca.ip.att.net [12.123.30.134]
                                0/ 100 =  0%   |
  8  ---     100/ 100 =100%     0/ 100 =  0%  gar29.la2ca.ip.att.net [12.122.129.241]
                                0/ 100 =  0%   |
  9  ---     100/ 100 =100%     0/ 100 =  0%  12-122-254-234.attens.net [12.122.254.234]
                                0/ 100 =  0%   |
 10  ---     100/ 100 =100%     0/ 100 =  0%  mdf001c7613r0002.lax1.attens.net [206.16.68.54]
 

serge87

join:2009-11-29
Reviews:
·Verizon FiOS
reply to Xtreme2damax
said by Xtreme2damax:

Same issues on the east coast. Not just you guys. A bit frustrating since I am an online gamer but not much I can do. Want to know something weird? I am in Central NY and I make a hop all the way to Culpeper, VA just to connect to a game server in NY/NJ.

I wouldn't worry too much about the hop going to Virginia, if it is at all. There's no way to find its true location but it is pinging at 10-12ms for you so it's not all bad.

Xtreme2damax

join:2007-03-21
Port Byron, NY
reply to andyjai
Same issues on the east coast. Not just you guys. A bit frustrating since I am an online gamer but not much I can do. Want to know something weird? I am in Central NY and I make a hop all the way to Culpeper, VA just to connect to a game server in NY/NJ.


kansh

@verizon.net
reply to fiberd

Re: Problem with Fios

This is beyond ridiculous. I've done what other people here have done as well for the past few days - I called Verizon and reported and asked when is the fix going to happen... all they do is give us bull$hit answers and fake ETAs.

This is obviously bad business and customer service by Verizon, They should have a network status page that updates every minute letting their customers know what is going on...but instead they give you all this crap letting you believe that your own router has a problem and they ship you a replacement and still the same issue only to find out that there's an outage...

Its been more than a week and still the same issue - this is unacceptable

fiberd

join:2005-04-15
Redondo Beach, CA
reply to kansh
Redondo Beach has been really bad this entire week.

I can resolve most websites, but things such as transactions (purchases) can take up to 30 seconds or more to process.

Last Night (2/1):




Today (2/2):




I've spoken to a friend who lives in Lakewood, CA and he's getting 22/15 on a 75/50 plan.

andyjai

join:2001-09-12
Rowland Heights, CA
reply to andyjai

Re: [Southwest] Problem with Fios

Atlantic metro


Internode


Race


Dreamhost



Have you try other servers on Speedtest.net? I am still having connection issue with two servers. But my speed haven't slow down today. I am able to stream HD video from youtube at 30-80Mbps.

A Tech was schedule to come to my house today, but he didn't show up so I called Verizon. They say the tech didn't come because there is an outage in this area, something to do with the GPON. ETA fix time is today at 7pm.


Shirke

@verizon.net
reply to andyjai

Re: Problem with Fios

I still have a same speed result as above my post


kansh

@verizon.net
reply to Shirke
I'm in Redondo Beach and FIOS is still down.. this is frustrating



Shirke

@verizon.net
reply to andyjai
Click for full size
I'm In Redondo Beach my speed results:

andyjai

join:2001-09-12
Rowland Heights, CA
reply to andyjai
I hope it will also fix my problem in Rowland Heights.


dave49er

join:2004-05-05
Walnut, CA
reply to andyjai
I just called again tonight. The Tech Support person logged my call and had a supervisor call me back. He said that the reason for the slow speeds was that we were being transferred to an alternate FiOS line because of the problem. He said that they have had a group working on it, and they are replacing some equipment at the CO in Walnut. Estimated ETA is 3:00 am.
Since everything goes fine after 2:00 am, I suppose that we won't know until tomorrow.


FutureX2001

join:2000-10-25
Perris, CA
Reviews:
·Verizon FiOS
reply to andyjai
My problem is almost identical; my connection speed, packet loss and latency seem to vary greatly from server to server. I'm seeing things occur I've never seen in the past, even when I bypassed my router and hooked straight into the ONT via ethernet.

It's almost as if some routes to different servers are heavily congested on Verizon's side.

Took this just now 75/35mbps package:

Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [65536]
running 10s outbound test (client to server) . . . . . 6.21Mb/s
running 10s inbound test (server to client) . . . . . . 8.93Mb/s
Packet size is preserved End-to-End
Server IP addresses are preserved End-to-End

andyjai

join:2001-09-12
Rowland Heights, CA

1 edit
reply to andyjai
Thanks for the info. I am still having problems at night, but this couple nights not as bad as last Friday to Wednesday.

How accurate is verizon's speedtest? For those that have no problem with their fios, do you guys always see full speed from their speedtest? I always get slower speed from the standard 75Mbps test than the 100Mbps test, and I hardly ever see full speed with either test.

Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [261360]
running 10s outbound test (client to server) . . . . . 38.87Mb/s
running 10s inbound test (server to client) . . . . . . 7.64Mb/s

------ Client System Details ------
OS data: Name = Windows 7, Architecture = x86, Version = 6.1
Java data: Vendor = Oracle Corporation, Version = 1.7.0_11

------ Web100 Detailed Analysis ------
Client Receive Window detected at 261360 bytes.
100 Mbps FastEthernet link found.
Link set to Full Duplex mode
Information: throughput is limited by other network traffic.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 11.21 msec; the Packet size = 1452 Bytes; and
There were 464 packets retransmitted, 487 duplicate acks received, and 856 SACK blocks received
The connection stalled 5 times due to packet loss
The connection was idle 1.06 seconds (9.63%) of the time
This connection is sender limited 42.78% of the time.
This connection is network limited 56.03% of the time.

Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: OFF
RFC 1323 Window Scaling: ON
Information: Network Middlebox is modifying MSS variable
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address

Dreamhost



Race Communication



Speedtest.net - Atlantic Metro, Internode, Charter all can't connect for testing.

Nvidia 2400KB/s
ATI 800KB/s
Microsoft 2800KB/s
Apple 7KB/s

I don't even know how to explain the issue to the tech that is suppose to come tomorrow.


Lloyd

@verizon.net
reply to andyjai
I sent message to @VerizonSupport on Twitter and they said there is an outage in this area, but no ETA as to when it will get fixed.


Lloyd

@verizon.net
reply to mkaishar
I got so frustrated that I had to call customer service. I got the poor rep to transfer me to someone in Escalations and I told him that these problems have been going on for a week now with no resolution in sight. I told him that this is affecting a number of people in Walnut, Diamond Bar, and Rowland Heights, and some people are business users. He said he was going to create a "ROC" ticket, which would hold more weight than anything generated by Tech Support. Hopefully this will get the ball rolling and get someone to fix this problem.

mkaishar

join:2000-12-20
united state
Reviews:
·Verizon FiOS
reply to andyjai
Email: ca.fsc.customer.experience@verizon.com

: host
fldsmtpe01.verizon.com[140.108.26.140] said: 550 #5.1.0 Address rejected.
(in reply to RCPT TO command)

I guess that didn't work, will have to try a different avenue to try and communicate with VZ other than helpdesk support.

mkaishar

join:2000-12-20
united state
Reviews:
·Verizon FiOS
reply to andyjai
Look at that, it's the daytime and everything is working OK, surprise surprise

Speed Test #103923279 by dslreports.com
Run: 2013-01-30 12:41:05 EST
Download: 29995 (Kbps)
Upload: 24892 (Kbps)
In kilobytes per second: 3661.5 down 3038.5 up

I will send an email to them and see what they say, because this is now starting to cost me money and loss of productivity at night.

smrtech

join:2009-09-21
Springfield, PA
reply to andyjai
Yea, same problem exists on east coast too, not just CA.
Slows down alot at night especially. And for me, it's gotten
a bit better last few days, I can stream, but still erratic
download speeds. I did notice the routing 2 hops out from
me changed in last couple days, but core problem still there.

Funny thing, I have an open case on this and a very nice support
person calls me every day to see how things are doing. I
repeat that this is in their network or CO, not at my house
(please don't send another tech!). Have sent him the
traceroutes and explanations via email. I told him, I want
him to call the local manager and get me an answer about
what they think it is - but so far nothing. I just wanted
them to say anything, but get zero response. Network
Techs say it's all fine...(they told me that once). He'll
call tonight and ask me if I have heard anything more about
this problem!

It's either bad routing or over-subscription or both.
I do get decent performance in general, but there are
sites that either hang or I download a PDF and get 1MB/s
- this should not be (where I did not have this with Comcast).

FYI - if you are interested, lob and email to the following
address and yell, this is what I got from the support person.
Change first 2 letters to your state abbrev.

Email: pa.fsc.customer.experience@verizon.com

Go ahead try that, opening a case with support is a total
waste of time. Not only will nothing ever get fixed by that,
it just wastes everybody's time.

jk111

join:2013-01-27
reply to andyjai
It clears up at night because during the day and evening (at peak times) the backbone gets way over taxed. When traffic slows down at night, things appear normal. At least this is what I believe is going on.

andyjai

join:2001-09-12
Rowland Heights, CA
reply to andyjai
2AM and speed is back. I am able to stream youtube 60-80Mbps.

Verizon standard speedtest

Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [261360]
running 10s outbound test (client to server) . . . . . 39.03Mb/s
running 10s inbound test (server to client) . . . . . . 45.81Mb/s

------ Client System Details ------
OS data: Name = Windows 7, Architecture = x86, Version = 6.1
Java data: Vendor = Oracle Corporation, Version = 1.7.0_11

------ Web100 Detailed Analysis ------
Client Receive Window detected at 261360 bytes.
100 Mbps FastEthernet link found.
Link set to Half Duplex mode
No network congestion discovered.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 9.95 msec; the Packet size = 1452 Bytes; and
There were 587 packets retransmitted, 2405 duplicate acks received, and 2941 SACK blocks received
The connection stalled 2 times due to packet loss
The connection was idle 0.42 seconds (4.19%) of the time
This connection is sender limited 72.41% of the time.
This connection is network limited 27.08% of the time.

Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: OFF
RFC 1323 Window Scaling: ON
Information: Network Middlebox is modifying MSS variable
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address
Server says [71.104.67.209] but Client says [192.168.1.168]

Verizon 100Mb test 6ms 84.1Down 39.32Up
Speakeasy 73.09Down 27.94Up
Speedtest.net 4servers all around 80Down 30Up

Nvidia 8000KB/s
ATI 5500KB/s
Microsoft 6000KB/s
Apple 6000KB/s

Does Verizon reboot their equipments at 2 am or something? I just don't get how things get clear up after certain time and then get clog up again next day.


AC11111

@verizon.net
reply to jk111
Click for full size
dfw area 75/35 plan - this sux


aonacoward

@verizon.net
reply to andyjai
Click for full size
dallas area:


FutureX2001

join:2000-10-25
Perris, CA
reply to andyjai
I made a similar post a few weeks back, I have the same exact issue. It seems to come and go...

jk111

join:2013-01-27
reply to andyjai
I realize it's not an issue that can be fixed with the push of a button, but Verizon does need to stop sending out techs for issues that obviously have nothing to do with equipment at the homes. They need to "own up" and resolve the issue.

mkaishar

join:2000-12-20
united state
Reviews:
·Verizon FiOS
reply to andyjai
3 6 ms 6 ms 7 ms 130.81.182.226
4 32 ms * 33 ms 130.81.29.126
5 41 ms 31 ms * 152.63.10.157
6 * 77 ms * 152.63.18.241
7 * 77 ms 76 ms 152.63.21.65
8 122 ms 122 ms 118 ms 152.179.72.66
9 80 ms 76 ms 76 ms 209.85.255.68
10 80 ms 76 ms 78 ms 209.85.252.242
11 81 ms 87 ms 83 ms 209.85.249.11
12 82 ms 85 ms 81 ms 72.14.238.16
13 82 ms 88 ms 94 ms 216.239.49.145
14 88 ms 85 ms 84 ms 8.8.8.8

these problems have been occurring for me since december and all they are doing is wasting people's time, no reason to have a tech out to a home when the issues are clearly on verizon's transport and backbone.

these problems go away during the dawn hours and day when most people are sleeping or not at home.

they just need to fix their network, damn it, hate wasting time with B.S. crap


Lloyd

@verizon.net
reply to andyjai
Yes, I've been having this problem, too. It first started happening on the evening of January 28th, went away around 1 AM and the issue is now back in full force this evening. I tried calling Verizon tech support and they reset my router to factory defaults without me telling them! It looks like there's a router somewhere at the 4th hop where the packet loss starts. The router's IP Address is:

130.81.29.124
130.81.151.246