My Frontier DSL went down sometime around 11:30 Central. Went to VZW card to contact support, and found page down also. DSL modem reports PPP down. Tail of VZW traceroute: 14 51 ms 49 ms 53 ms ae2---0.cor01.chcg.il.frontiernet.net [74.40.4.1 37] 15 70 ms 69 ms 69 ms ae1---0.cor02.roch.ny.ny.frontiernet.net [74.40. 5.21] 16 69 ms 76 ms 72 ms ge--0-1-0---0.car01.roch.ny.frontiernet.net [74. 40.5.182] 17 92 ms 80 ms 82 ms te5-4.br5.roch.ny.frontiernet.net [74.45.102.6] 18 86 ms 81 ms 80 ms frontier.com [66.133.172.205] Trace complete. Mark -----Original Message----- From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Frank Bulk Sent: Friday, June 21, 2013 12:33 PM To: outages@outages.org Subject: Re: [outages] Frontier.com homepage unaccessible Looks like Frontier having home page load issues over v4 and v6 again, this time since 12:21 pm Central or so. Traceroutes are the same, but I've included fresh wget results. nagios:/# wget -6 www.frontier.com --2013-06-21 12:30:15-- 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-06-21 12:30:16-- (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-06-21 12:30:18-- (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. --2013-06-21 12:30:21-- (try: 4) 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-06-21 12:30:26-- (try: 5) 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-06-21 12:30:31-- (try: 6) 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:/# wget -4 www.frontier.com --2013-06-21 12:30:38-- 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... Read error (Connection reset by peer) in headers. Retrying. --2013-06-21 12:30:39-- (try: 2) http://www.frontier.com/ Connecting to www.frontier.com|66.133.172.205|:80... connected. HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers. Retrying. --2013-06-21 12:30:42-- (try: 3) http://www.frontier.com/ Connecting to www.frontier.com|66.133.172.205|:80... connected. HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers. Retrying. --2013-06-21 12:30:45-- (try: 4) http://www.frontier.com/ Connecting to www.frontier.com|66.133.172.205|:80... connected. HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers. Retrying. --2013-06-21 12:30:49-- (try: 5) http://www.frontier.com/ Connecting to www.frontier.com|66.133.172.205|:80... connected. HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers. Retrying. ^C nagios:/# -----Original Message----- From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Frank Bulk Sent: Thursday, May 09, 2013 1:32 PM To: outages@outages.org Subject: [outages] Frontier.com homepage unaccessible 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@outages.org https://puck.nether.net/mailman/listinfo/outages _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages Confidentiality Statement: The documents accompanying this transmission contain confidential information that is legally privileged. This information is intended only for the use of the individuals or entities listed above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or action taken in reliance on the contents of these documents is strictly prohibited. If you have received this information in error, please notify the sender immediately and arrange for the return or destruction of these documents.