Quantcast
Channel: All Fios Internet posts
Viewing all articles
Browse latest Browse all 39554

Poor Fios Connectivity in the greater Boston area

$
0
0

Am I the only one?

 

We're in Dunstable, MA - just south of Nashua, NH. We have had fios from the start and its been fine. Sometime around June 21st, we started having issues.

 

At first I thought it was wifi, but its wired as well. The browser is waiting to make that initial connection. Speedtest is up to 85/35 - if it will connect.  Traceroute and ping to google.com below. Tried verizon DNS and google. no help.

 

Called version customer support. Insisted on getting to someone that understood networking. Got to premeier? support and we seemed to finally start understanding each other (that we might both be competent). They asked me for my phone number MULTIPLE times. We were disconnected and NO CALL BACK. I could not waster more time today. It took my 4 tries of refreshing to get to this page....

 

Is anyone else in the area having issues? I read some other posts about peering problems in NYC. I saw those hops in an earlier traceroute.  Even more important, does anyone know how to get to the right support person to figure out if this is on my end (doubtful) or if its fixable. If not, I'm done with FIOS.

 

C:\Users\>tracert google.com

Tracing route to google.com [173.194.43.32]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.mshome [192.168.1.1]
2 5 ms * 4 ms L100.BSTNMA-VFTTP-99.verizon-gni.net [98.110.248.1]
3 11 ms 4 ms 4 ms G4-1-799.BSTNMA-LCR-07.verizon-gni.net [130.81.109.66]
4 10 ms 7 ms 9 ms so-0-0-2-0.BOS-BB-RTR1.verizon-gni.net [130.81.29.252]
5 12 ms 12 ms * 0.xe-2-1-1.XT1.NYC4.ALTER.NET [152.63.20.237]
6 17 ms 16 ms 15 ms TenGigE0-4-1-0.GW8.NYC4.ALTER.NET [152.63.21.69]

7 * * * Request timed out.
8 15 ms 14 ms 44 ms 72.14.238.232
9 14 ms 36 ms 14 ms 72.14.237.254
10 * * 14 ms lga15s35-in-f0.1e100.net [173.194.43.32]

Trace complete.

 

C:\Users\>ping google.com

Pinging google.com [173.194.43.0] with 32 bytes of data&colon;
Reply from 173.194.43.0: bytes=32 time=14ms TTL=250
Reply from 173.194.43.0: bytes=32 time=14ms TTL=250
Request timed out.
Reply from 173.194.43.0: bytes=32 time=14ms TTL=250

Ping statistics for 173.194.43.0:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 14ms, Average = 14ms


Viewing all articles
Browse latest Browse all 39554

Trending Articles