Our monitoring system alerted me to HTTP load failures for www.ebay.com, starting at 10:05 pm Central until 10:12 pm Central. Port 80 was open, but wget reveals the issue. I think my test was just as it was coming back up: ================================================ nagios:# tcptraceroute www.ebay.com Selected device eth0.3, address 96.31.0.5, port 55761 for outgoing packets Tracing the path to www.ebay.com (66.211.181.181) on TCP port 80 (www), 30 hops max 1 router-core-inside.mtcnet.net (96.31.0.254) 0.227 ms 0.214 ms 0.190 ms 2 sxct.movl.mtcnet.net (167.142.156.194) 0.183 ms 0.123 ms 0.130 ms 3 premier.movl-mlx.fbnt.netins.net (173.215.60.1) 1.921 ms 1.947 ms 1.914 ms 4 ins-kb1-te-13-2-220.kmrr.netins.net (167.142.64.253) 6.341 ms 6.308 ms 6.273 ms 5 ins-kc1-et-9-2.kmrr.netins.net (167.142.67.53) 6.392 ms 6.353 ms 6.370 ms 6 144.223.35.225 15.738 ms 15.669 ms 15.700 ms 7 144.232.11.234 26.464 ms 26.378 ms 26.283 ms 8 144.232.12.139 37.491 ms 39.168 ms 37.276 ms 9 144.232.1.163 37.554 ms 37.658 ms 37.713 ms 10 144.232.11.178 39.910 ms 40.120 ms 40.316 ms 11 sl-payp2-414020-0.sprintlink.net (144.223.244.134) 63.182 ms 63.093 ms 63.175 ms 12 * * * 13 * * * 14 www.ebay.com (66.211.181.181) [open] 63.582 ms 63.533 ms 63.467 ms nagios:# ================================================ nagios:# wget www.ebay.com --2013-06-12 22:12:10-- http://www.ebay.com/ Resolving www.ebay.com... 66.211.181.181, 66.135.200.161, 66.135.200.181, ... Connecting to www.ebay.com|66.211.181.181|:80... connected. HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers. Retrying. --2013-06-12 22:12:11-- (try: 2) http://www.ebay.com/ Connecting to www.ebay.com|66.211.181.181|:80... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: âindex.html.1â [ <=> ] 49,778 --.-K/s in 0.1s 2013-06-12 22:12:12 (408 KB/s) - âindex.html.1â nagios:# ================================================ Frank