[outages] BlueHost having/had some issues

[Steven Raymond]

Should find this resolved, please contact me directly if issues are found outstanding.
Thanks


On Dec 7, 2015, at 9:23 AM, Frank Bulk via Outages <outages at outages.org> wrote:

> Looks like access to BlueHost is/was down for some - first tweet was at 8:28
> am U.S. Central.  We have a financial services customer who alerted me as of
> 9:13 am.  Source-pinged 90+ interfaces from our router and most of our
> address space works, but there are/were a few smaller prefixes that
> don't/didn't.  
> 
> While composting this email it seems to be back up at 10:21 am.
> 
> Frank
> 
> 
> Good from 96.31.0.5
> 
> root at nagios:/tmp# tcptraceroute 162.144.113.182 80
> Selected device eth0.3, address 96.31.0.5, port 35906 for outgoing packets
> Tracing the path to 162.144.113.182 on TCP port 80 (www), 30 hops max
> 1  router-core-inside.mtcnet.net (96.31.0.254)  0.279 ms  0.220 ms  0.192
> ms
> 2  sxct.spnc.mtcnet.net (167.142.156.194)  0.273 ms  0.150 ms  0.139 ms
> 3  premier.spnc-mlx.fbnt.netins.net (173.215.60.1)  4.794 ms  4.758 ms
> 11.906 ms
> 4  ins-kb1-te-12-2-3031.kmrr.netins.net (167.142.64.253)  8.750 ms  8.576
> ms  8.616 ms
> 5  ins-kc2-et-po101.kmrr.netins.net (167.142.67.49)  8.567 ms  9.677 ms
> 8.612 ms
> 6  v504.core1.oma1.he.net (184.105.18.169)  44.144 ms  33.762 ms  41.165 ms
> 7  10ge3-11.core1.mci3.he.net (184.105.81.61)  33.960 ms  39.610 ms  33.904
> ms
> 8  100ge8-1.core2.chi1.he.net (184.105.81.210)  33.012 ms  24.417 ms
> 25.219 ms
> 9  100ge5-2.core1.chi1.he.net (184.105.81.98)  23.813 ms  23.590 ms  23.684
> ms
> 10  tg1-2.br01.chcg.acedc.NET (206.223.119.174)  23.855 ms  23.774 ms
> 23.823 ms
> 11  ve58.ar04.prov.acedc.net (199.58.196.85)  58.743 ms  60.124 ms  58.773
> ms
> 12  prv-211-1-1-2.unifiedlayer.com (69.27.175.147)  58.858 ms  58.830 ms
> 58.682 ms
> 13  162-144-240-139.unifiedlayer.com (162.144.240.139)  58.818 ms  58.872 ms
> 58.821 ms
> 14  162-144-240-51.unifiedlayer.com (162.144.240.51)  58.839 ms  58.783 ms
> 58.874 ms
> 15  162.144.113.182 [open]  59.315 ms  59.872 ms  59.338 ms
> root at nagios:/tmp#
> 
> 
> Was not working at one time from 199.120.69.4:
> 
> C:\Users\fbulk>tracetcp 162.144.113.182:443
> 
> Tracing route to 162.144.113.182 on port 443
> Over a maximum of 30 hops.
> 1       1 ms    1 ms    1 ms    192.168.0.254
> 2       1 ms    1 ms    1 ms    172.16.10.254
> 3       3 ms    9 ms    2 ms    199.120.69.254
> [router-core-inside.mtcnet.net]
> 4       2 ms    3 ms    9 ms    167.142.156.194 [sxct.spnc.mtcnet.net]
> 5       3 ms    6 ms    6 ms    173.215.60.1
> [premier.spnc-mlx.fbnt.netins.net]
> 6       6 ms    8 ms    8 ms    173.215.60.1
> [premier.spnc-mlx.fbnt.netins.net]
> 7       11 ms   10 ms   10 ms   167.142.64.253
> [ins-kb1-te-12-2-3031.kmrr.netins.net]
> 8       23 ms   10 ms   11 ms   167.142.67.49
> [ins-kc2-et-po101.kmrr.netins.net]
> 9       23 ms   22 ms   32 ms   184.105.81.61   [10ge3-11.core1.mci3.he.net]
> 10      35 ms   33 ms   32 ms   184.105.81.61   [10ge3-11.core1.mci3.he.net]
> 11      45 ms   36 ms   44 ms   184.105.81.210  [100ge8-1.core2.chi1.he.net]
> 12      48 ms   47 ms   45 ms   184.105.81.98   [100ge5-2.core1.chi1.he.net]
> 13      38 ms   72 ms   37 ms   206.223.119.174 [tg1-2.br01.chcg.acedc.net]
> 14      72 ms   70 ms   72 ms   199.58.196.85   [ve58.ar04.prov.acedc.net]
> 15      72 ms   70 ms   73 ms   162.144.240.155
> [162-144-240-155.unifiedlayer.com]
> 16      74 ms   72 ms   70 ms   162.144.240.157
> [162-144-240-157.unifiedlayer.com]
> 17      73 ms   Destination Reached in 73 ms. Connection established to
> 162.144.113.182
> Trace Complete.
> 
> C:\Users\fbulk>
> 
> _______________________________________________
> Outages mailing list
> Outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages