[outages] Frontier.com homepage unaccessible

Thu May 9 15:14:47 EDT 2013

works fine from PHX. Webpage loads fine 

[posiedon at hoppoint ~]$ traceroute frontier.com 
traceroute to frontier.com (66.133.172.205), 30 hops max, 60 byte packets 
1 172.16.8.1 (172.16.8.1) 1.871 ms 1.977 ms 1.639 ms 
2 ar1.as54049.com (199.66.112.129) 2.493 ms 2.462 ms 2.398 ms 
3 * * * 
4 bb2.cwie.10.2.phx0.cwie.net (64.38.200.2) 5.131 ms 5.086 ms 5.023 ms 
5 * * * 
6 ae-4-4.ebr2.LosAngeles1.Level3.net (4.69.133.38) 22.704 ms 23.707 ms 22.150 ms 
7 ae-6-6.ebr2.SanJose5.Level3.net (4.69.148.202) 21.076 ms 20.947 ms 20.932 ms 
8 ae-2-2.ebr2.SanJose1.Level3.net (4.69.148.142) 21.977 ms 21.808 ms ae-1-100.ebr1.SanJose5.Level3.net (4.69.148.109) 21.770 ms 
9 ae-5-5.ebr1.SanJose1.Level3.net (4.69.148.138) 23.361 ms ae-92-92.csw4.SanJose1.Level3.net (4.69.153.30) 23.262 ms ae-5-5.ebr1.sanjose1.level3.net (4.69.148.138) 24.610 ms 
10 ae-32-90.car2.SanJose2.Level3.net (4.69.152.204) 23.192 ms ae-12-70.car2.SanJose2.Level3.net (4.69.152.76) 21.582 ms ae-81-81.csw3.SanJose1.Level3.net (4.69.153.10) 21.547 ms 
11 ae-42-80.car2.SanJose2.Level3.net (4.69.152.140) 21.742 ms CITIZENS-CO.car2.SanJose2.Level3.net (4.59.4.82) 21.798 ms 22.806 ms 
12 citizens-co.car2.sanjose2.level3.net (4.59.4.82) 21.725 ms ae2---0.cor02.plal.ca.frontiernet.net (74.40.3.169) 22.009 ms 21.975 ms 
13 ae1---0.cor01.slkc.ut.frontiernet.net (74.40.5.62) 38.597 ms 48.070 ms 38.278 ms 
14 ae3---0.cor02.chcg.il.frontiernet.net (74.40.5.57) 62.738 ms ae1---0.cor01.slkc.ut.frontiernet.net (74.40.5.62) 38.070 ms ae3---0.cor02.chcg.il.frontiernet.net (74.40.5.57) 118.283 ms 
15 ae3---0.cor02.chcg.il.frontiernet.net (74.40.5.57) 61.473 ms ae0---0.cor01.chcg.il.frontiernet.net (74.40.3.241) 83.100 ms 59.357 ms 
16 ae0---0.cor01.chcg.il.frontiernet.net (74.40.3.241) 59.320 ms 65.324 ms ae1---0.cor02.roch.ny.ny.frontiernet.net (74.40.5.21) 79.708 ms 
17 ge--0-1-0---0.car01.roch.ny.frontiernet.net (74.40.5.182) 81.659 ms ae1---0.cor02.roch.ny.ny.frontiernet.net (74.40.5.21) 79.755 ms 81.272 ms 
18 te5-4.br5.roch.ny.frontiernet.net (74.45.102.6) 80.355 ms 80.236 ms ge--0-1-0---0.car01.roch.ny.frontiernet.net (74.40.5.182) 79.578 ms 
19 * te5-4.br5.roch.ny.frontiernet.net (74.45.102.6) 79.570 ms 79.473 ms 
20 * * * 
21 * * * 
22 * * * 
23 * * * 
24 * * * 
25 * * * 
26 * * * 

============= 
Best Regards 

Raman Sud 
Sr. VP of Engineering 
Mojohost 
Toll Free: 888-345-MOJO x808 
Cell: +1 480.206.0211 
PGP Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x26BDA015F2DCF135 

THIS MESSAGE IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL OR ENTITY TO WHICH IT IS ADDRESSED, AND MAY CONTAIN INFORMATION THAT IS PRIVILEGED, CONFIDENTIAL AND EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW. IF THE READER OF THIS MESSAGE IS NOT THE INTENDED RECIPIENT, YOU ARE HEREBY NOTIFIED THAT ANY DISSEMINATION, DISTRIBUTION OR COPYING OF THIS COMMUNICATION IS STRICTLY PROHIBITED, AND THAT THIS EMAIL AND ALL COPIES AND ATTACHMENTS SHOULD BE IMMEDIATELY DESTROYED. 

----- Original Message -----

From: "Mike" <miketheman at gmail.com> 
To: "Frank Bulk" <frnkblk at iname.com> 
Cc: "outages" <outages at outages.org> 
Sent: Thursday, May 9, 2013 11:54:45 AM 
Subject: Re: [outages] Frontier.com homepage unaccessible 

Works fine from VZW FiOS NYC: 

$ wget www.frontier.com 
--2013-05-09 14:53:39-- http://www.frontier.com/ 
Resolving www.frontier.com... 66.133.172.205, 2001:1960:21:1::92 
Connecting to www.frontier.com|66.133.172.205|:80... connected. 
HTTP request sent, awaiting response... 200 OK 
Length: 59798 (58K) [text/html] 

-Mike 

On Thu, May 9, 2013 at 2:32 PM, Frank Bulk <frnkblk at iname.com> wrote: 
> It's seems Frontier Communications home page has been down over IPv4 and 
> IPv6 since 12:34 pm Central. Port 80 is open over v4 and v6, just the page 
> doesn't load. 
> 
> =========================================================== 
> nagios:/# wget -4 www.frontier.com 
> --2013-05-09 13:24:53-- http://www.frontier.com/ 
> Resolving www.frontier.com... 66.133.172.205 
> Connecting to www.frontier.com|66.133.172.205|:80... connected. 
> HTTP request sent, awaiting response... ^C 
> =========================================================== 
> nagios:/# wget -6 www.frontier.com 
> --2013-05-09 13:25:07-- http://www.frontier.com/ 
> Resolving www.frontier.com... 2001:1960:21:1::92 
> Connecting to www.frontier.com|2001:1960:21:1::92|:80... connected. 
> HTTP request sent, awaiting response... Read error (Connection reset by 
> peer) in headers. 
> Retrying. 
> 
> --2013-05-09 13:25:08-- (try: 2) http://www.frontier.com/ 
> Connecting to www.frontier.com|2001:1960:21:1::92|:80... connected. 
> HTTP request sent, awaiting response... Read error (Connection reset by 
> peer) in headers. 
> Retrying. 
> 
> --2013-05-09 13:25:10-- (try: 3) http://www.frontier.com/ 
> Connecting to www.frontier.com|2001:1960:21:1::92|:80... connected. 
> HTTP request sent, awaiting response... Read error (Connection reset by 
> peer) in headers. 
> Retrying. ^C 
> =========================================================== 
> nagios:/# tcptraceroute www.frontier.com 
> Selected device eth0.3, address 96.31.0.5, port 50820 for outgoing packets 
> Tracing the path to www.frontier.com (66.133.172.205) on TCP port 80 (www), 
> 30 hops max 
> 1 router-core-inside.mtcnet.net (96.31.0.254) 0.248 ms 0.194 ms 0.184 
> ms 
> 2 sxct.movl.mtcnet.net (167.142.156.194) 0.195 ms 0.131 ms 0.116 ms 
> 3 premier.movl-mlx.fbnt.netins.net (173.215.60.1) 1.932 ms 1.914 ms 
> 1.922 ms 
> 4 ins-kb1-te-13-2-220.kmrr.netins.net (167.142.64.253) 7.582 ms 7.513 ms 
> 7.483 ms 
> 5 ins-kc2-et-8-3.kmrr.netins.net (167.142.67.37) 9.148 ms 9.180 ms 
> 9.126 ms 
> 6 ins-dc1-po20.desm.netins.net (167.142.67.29) 9.327 ms 9.437 ms 9.139 
> ms 
> 7 te-3-3.car2.KansasCity1.Level3.net (4.53.34.113) 15.643 ms 15.800 ms 
> 15.647 ms 
> 8 ae-11-11.car1.KansasCity1.Level3.net (4.69.135.233) 44.503 ms 44.517 
> ms 44.595 ms 
> 9 ae-5-5.ebr2.Dallas1.Level3.net (4.69.135.230) 44.475 ms 44.443 ms 
> 44.420 ms 
> 10 ae-62-62.csw1.Dallas1.Level3.net (4.69.151.129) 56.816 ms 50.240 ms 
> 44.854 ms 
> 11 ae-63-63.ebr3.Dallas1.Level3.net (4.69.151.134) 44.511 ms 44.640 ms 
> 44.660 ms 
> 12 ae-7-7.ebr3.Atlanta2.Level3.net (4.69.134.22) 44.635 ms 44.603 ms 
> 44.463 ms 
> 13 ae-73-73.ebr2.Atlanta2.Level3.net (4.69.148.254) 44.559 ms 44.565 ms 
> 44.595 ms 
> 14 ae-2-52.edge1.Atlanta4.Level3.net (4.69.150.79) 44.627 ms 44.418 ms 
> 44.442 ms 
> 15 4.53.232.34 44.695 ms 76.316 ms 44.644 ms 
> 16 ae2---0.cor02.atln.ga.frontiernet.net (74.40.2.81) 44.794 ms 44.675 ms 
> 44.624 ms 
> 17 ae1---0.cor02.asbn.va.frontiernet.net (74.40.2.198) 58.282 ms 144.739 
> ms 58.297 ms 
> 18 ae3---0.cor01.roch.ny.frontiernet.net (74.40.5.17) 71.606 ms 71.562 ms 
> 71.494 ms 
> 19 ge--0-0-0---0.car01.roch.ny.frontiernet.net (74.40.5.74) 70.920 ms 
> 70.830 ms 70.909 ms 
> 20 te5-4.br5.roch.ny.frontiernet.net (74.45.102.6) 404.081 ms 71.598 ms 
> 71.562 ms 
> 21 * frontier.com (66.133.172.205) [open] 68.823 ms 71.625 ms 
> nagios:/# 
> =========================================================== 
> 
> nagios:/# tcptraceroute6 www.frontier.com 
> traceroute to frontier.com (2001:1960:21:1::92) from 2607:fe28:0:1000::5, 
> port 80, from port 59200, 30 hops max, 60 bytes packets 
> 1 router-core.mtcnet.net (2607:fe28:0:1000::1) 0.250 ms 0.194 ms 0.201 
> ms 
> 2 sxct.movl.mtcnet.net (2607:fe28:11:1002::194) 0.181 ms 0.125 ms 0.130 
> ms 
> 3 v6-premier.movl-mlx.fbnt.netins.net (2001:5f8:7f0a:1::1) 1.967 ms 
> 1.887 ms 1.909 ms 
> 4 v6-ins-kb1-te-13-2-220.kmrr.netins.net (2001:5f8:2:2::1) 7.595 ms 
> 7.477 ms 7.512 ms 
> 5 v6-ins-kc2-te-8-3.kmrr.netins.net (2001:5f8::11:1) 7.568 ms 7.494 ms 
> 7.584 ms 
> 6 v6-ins-dc1-po20.desm.netins.net (2001:5f8::8:1) 9.210 ms 9.202 ms 
> 9.148 ms 
> 7 te-3-3.car2.KansasCity1.Level3.net (2001:1900:2100::e2d) 15.738 ms 
> 15.912 ms 15.657 ms 
> 8 vl-11.car1.KansasCity1.Level3.net (2001:1900:4:1::37d) 15.632 ms 
> 15.751 ms 15.632 ms 
> 9 vl-4049.edge2.Dallas1.Level3.net (2001:1900:4:1::379) 24.750 ms 24.706 
> ms 24.654 ms 
> 10 vl-4080.edge3.Dallas1.Level3.net (2001:1900:4:1::82) 24.780 ms 24.713 
> ms 24.751 ms 
> 11 vl-4061.car1.Atlanta2.Level3.net (2001:1900:4:1::96) 44.731 ms 44.774 
> ms 44.759 ms 
> 12 vl-51.edge1.Atlanta4.Level3.net (2001:1900:1c:1::10) 44.866 ms 44.896 
> ms 44.806 ms 
> 13 2001:1900:2100::1a (2001:1900:2100::1a) 71.300 ms 44.481 ms 44.571 ms 
> 14 ae2---0.cor02.atln.ga.frontiernet.net (2001:1960:c:1f::) 52.316 ms 
> 44.854 ms 44.776 ms 
> 15 ae1---0.cor02.asbn.va.frontiernet.net (2001:1960:c:3c::1) 58.473 ms 
> 58.343 ms 58.461 ms 
> 16 ae3---0.cor01.roch.ny.frontiernet.net (2001:1960:c:3d::) 124.867 ms 
> 71.000 ms 70.933 ms 
> 17 ge--0-1-0---0.car02.roch.ny.frontiernet.net (2001:1960:c:28::1) 69.445 
> ms 69.408 ms 69.299 ms 
> 18 frontier.com (2001:1960:21:1::92) 69.200 ms [open] 69.149 ms 69.079 
> ms 
> nagios:/# 
> =========================================================== 
> 
> Frank 
> 
> _______________________________________________ 
> Outages mailing list 
> Outages at outages.org 
> https://puck.nether.net/mailman/listinfo/outages 
_______________________________________________ 
Outages mailing list 
Outages at outages.org 
https://puck.nether.net/mailman/listinfo/outages 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20130509/a5a303f2/attachment.htm>