×

Switch Account

Website connection issues

Website connection issues

Reply
Contributor RC3
Contributor
Posts: 3
Registered: ‎08-16-2018
Message 1 of 16
(1,202 Views)

I'm seeing a problem connecting to flightaware.com and a few other sites from any computer on my LAN.  I ran a curl and I'm not getting a TLS server hello response back.  I've tried a few different router MTU settings (all lower than 1500), but no improvement.  It does work if I use a VPN, so I'm pretty confident it's nothing on my LAN.  Anyone else seeing this?

 

Broswer error:

 

 This site can’t be reached

flightaware.com took too long to respond.

 

Here's a traceroute:

 

Tracing route to flightaware.com [70.42.6.250]
over a maximum of 30 hops:

2 6 ms 8 ms 8 ms lo0-100.BSTNMA-VFTTP-373.verizon-gni.net [71.184.97.1]
3 8 ms 7 ms 15 ms B3373.BSTNMA-LCR-22.verizon-gni.net [100.41.131.80]
4 * * * Request timed out.
5 * * * Request timed out.
6 12 ms 8 ms 8 ms 0.et-11-0-2.BR2.NYC4.ALTER.NET [140.222.239.35]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

 

15 REPLIES 15
Gold Contributor VII
Gold Contributor VII
Posts: 4,776
Registered: ‎10-18-2016
Message 2 of 16
(1,201 Views)

Page loads for me from NY

 

Contributor RC3
Contributor
Posts: 3
Registered: ‎08-16-2018
Message 3 of 16
(1,196 Views)

Thanks- could you post a traceroute to compare?

Copper Contributor trace_route
Copper Contributor
Posts: 7
Registered: ‎08-14-2018
Message 4 of 16
(1,180 Views)

I see the same thing.  I've had a ticket in for a few days, but no luck with Verizon.

I can ping that site from work (with comcast internet) just fine.

 

traceroute to 70.42.6.250 (70.42.6.250), 30 hops max, 60 byte packets

 1  FIOS_Quantum_Gateway.fios-router.home (192.168.1.1)  0.713 ms  0.813 ms  0.766 ms

 2  lo0-100.BSTNMA-VFTTP-373.verizon-gni.net (71.184.97.1)  7.698 ms  9.239 ms  9.206 ms

 3  B3373.BSTNMA-LCR-21.verizon-gni.net (100.41.131.78)  13.642 ms B3373.BSTNMA-LCR-22.verizon-gni.net (100.41.131.80)  11.243 ms  11.231 ms

 4  * * *

 5  * * *

 6  0.et-5-1-2.BR2.NYC4.ALTER.NET (140.222.231.129)  18.147 ms 0.et-11-0-2.BR2.NYC4.ALTER.NET (140.222.239.35)  16.458 ms  16.412 ms

 7  * * *

 8  * * *

 9  * * *

10  * * *

11  * * *

12  * * *

13  * * *

14  * * *

 

Contributor FiosDood
Contributor
Posts: 4
Registered: ‎08-16-2018
Message 5 of 16
(1,162 Views)

I'm seeing the same issue. I can't reach flightaware.com or nba.com and some others. In my case it seems when I get an IP from their 100.0 pool(several different ones) it does not work. Putting my laptop in line and getting a 96.x address works fine. 

 

I have a case open with the network team and they say it's 24-48 hours to get an answer. 

Copper Contributor trace_route
Copper Contributor
Posts: 7
Registered: ‎08-14-2018
Message 6 of 16
(1,158 Views)

My issues also arose when I got a 100.0.x.x address.

 

Gold Contributor VII
Gold Contributor VII
Posts: 4,776
Registered: ‎10-18-2016
Message 7 of 16
(1,158 Views)

Sorry for the gif image but I am using a tablet.00FB16A1-F712-455E-BE21-4D062B9FD81F.png

 

 

 

Gold Contributor VII
Gold Contributor VII
Posts: 4,776
Registered: ‎10-18-2016
Message 8 of 16
(1,154 Views)

Log by iNetTools - Best Network Diagnose Tools on iPhone and iPad.

 

traceroute to flightaware.com (70.42.6.250) , 5 relative hops max, 52 byte packets

   1 192.168.1.1 (192.168.1.1) 9.127 ms 1018.103 ms 1019.651 ms

   2  * * *

   3 100.41.129.44 (100.41.129.44) 12.821 ms 119.093 ms 124.037 ms

   4  * * *

   5 140.222.239.35 (140.222.239.35) 15.249 ms 56.792 ms 74.698 ms

   6 204.255.168.114 (204.255.168.114) 13.610 ms 30.770 ms 32.960 ms

   7 be3496.ccr42.jfk02.atlas.cogentco.com (154.54.0.141) 14.173 ms 59.435 ms 79.135 ms

   8 be2807.ccr42.dca01.atlas.cogentco.com (154.54.40.110) 16.722 ms 71.790 ms 73.231 ms

   9 be2113.ccr42.atl01.atlas.cogentco.com (154.54.24.222) 28.892 ms 68.567 ms 70.947 ms

 10 be2690.ccr42.iah01.atlas.cogentco.com (154.54.28.130) 48.824 ms 102.909 ms 113.273 ms

 11 te0-0-1-3.agr14.iah01.atlas.cogentco.com (154.54.25.230) 51.700 ms 177.383 ms 186.316 ms

 12 154.24.0.242 (154.24.0.242) 49.397 ms 117.606 ms 122.838 ms

 13 38.142.28.186 (38.142.28.186) 50.959 ms 84.208 ms 87.351 ms

 14 border3.ae2-bbnet2.hou.pnap.net (216.52.168.65) 49.381 ms 301.952 ms 309.463 ms

 15 edge1.ae1-edgenet.hou.pnap.net (23.92.181.18) 50.315 ms 249.279 ms 262.059 ms

 16 superconnect-7.edge1.hou.pnap.net (64.95.211.202) 48.604 ms * *

 17  * * *

 18 webfarm.flightaware.com (70.42.6.250) 56.573 ms 237.780 ms *

 19 webfarm.flightaware.com (70.42.6.250) 51.239 ms 63.561 ms 85.983 ms

Copper Contributor trace_route
Copper Contributor
Posts: 7
Registered: ‎08-14-2018
Message 9 of 16
(1,137 Views)

According to a helpful customer rep, this whole issue is the subject of a group ticket and has been escalated to tier 2 support.  According to the rep, it is a problem with Verizon's main router and they claim it will be fixed sometime today.

 

Contributor paultreny
Contributor
Posts: 2
Registered: ‎08-16-2018
Message 10 of 16
(1,104 Views)

Having the same issues since yesterday morning, connecting through a VPN or Proxy is fine, and local DNS resolution is fine, but traceroute and ping fail for certain sites.

( www.git-tower.com ) is the one I've been testing with, but flightaware.com also doesn't work for me, it's definitely some routing issue at 0.et-11-0-2.br2.nyc4.alter.net 

 

Had issues yesterday with Amazon and NBA.com as well, but it looks like those sites have changed their routing (they're not just a single server, after all) to work around the issue, but smaller sites aren't going to be able to do that.

 

https://twitter.com/paultreny/status/1029789541648019464

 

https://twitter.com/paultreny/status/1029781952377827330

 

traceroute to www.git-tower.com (134.119.78.97), 64 hops max, 52 byte packets
 1  edgerouter (192.168.1.1)  1.885 ms  2.147 ms  4.640 ms
 2  lo0-100.bstnma-vfttp-308.verizon-gni.net (100.0.[REDACTED])  3.892 ms  4.669 ms  3.768 ms
 3  b3308.bstnma-lcr-22.verizon-gni.net (100.41.214.180)  7.132 ms  6.855 ms  7.965 ms
 4  * * *
 5  * * *
 6  0.et-11-0-2.br2.nyc4.alter.net (140.222.239.35)  12.275 ms
    0.et-5-1-2.br2.nyc4.alter.net (140.222.231.129)  11.739 ms
    0.et-11-0-2.br2.nyc4.alter.net (140.222.239.35)  10.934 ms
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *

 

traceroute to flightaware.com (70.42.6.250), 64 hops max, 52 byte packets
 1  edgerouter (192.168.1.1)  1341.243 ms  1.923 ms  2.117 ms
 2  lo0-100.bstnma-vfttp-308.verizon-gni.net (100.0.[REDACTED])  8.804 ms  4.847 ms  2.186 ms
 3  b3308.bstnma-lcr-21.verizon-gni.net (100.41.214.178)  5.466 ms  12.654 ms
    b3308.bstnma-lcr-22.verizon-gni.net (100.41.214.180)  7.070 ms
 4  * * *
 5  * * *
 6  0.et-11-0-2.br2.nyc4.alter.net (140.222.239.35)  13.323 ms
    0.et-5-1-2.br2.nyc4.alter.net (140.222.231.129)  10.711 ms  10.407 ms
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
How-To Videos
 
The following videos were produced by users like you!
   
Videos are subject to the Verizon Fios Community Terms of Service and User Guidelines and contains content that is not created by Verizon.


Browse Categories
Categories:
Posts

Verizon Troubleshooters
Unable to find your answer here? Try searching Verizon Troubleshooters for more options.