Working just fine for me C:\Users\jluthman>tracert -d www.amazon.com
Tracing route to www.amazon.com [54.239.17.7] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 10.10.10.1 2 2 ms 1 ms 1 ms 192.149.254.1 3 5 ms 5 ms 5 ms 45.52.8.205 4 20 ms 20 ms 20 ms 74.40.5.58 5 20 ms 19 ms 20 ms 74.42.149.189 6 20 ms 19 ms 20 ms 74.40.4.138 7 20 ms 19 ms 20 ms 206.223.119.98 8 37 ms 37 ms 36 ms 52.95.62.84 9 33 ms 30 ms 30 ms 52.95.62.97 10 30 ms 30 ms 34 ms 54.239.42.63 11 30 ms 30 ms 33 ms 54.239.42.69 12 46 ms 47 ms 48 ms 54.239.109.200 13 31 ms 30 ms 30 ms 54.239.109.217 14 30 ms 30 ms 30 ms 205.251.245.121 15 * * * Request timed out. 16 * * * Request timed out. 17 * ^C C:\Users\jluthman>host www.amazon.com www.amazon.com has address 54.239.17.7 Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Fri, Apr 22, 2016 at 1:34 PM, Filip Hruska via Outages < [email protected]> wrote: > I saw some weirdness from my home connection here in the Czech Republic > (my ISP is AS39761, really small). Routes that were supposed to be local > were routed via HE.NET Zurich POP for some reason. Also saw some mentions > of "init7.net" in the traceroute (which I of course forgot to save). > > Everything seems alright now. > > So it was probably a global issue. > > > Best Regards, > Filip Hruska > > > > On 04/22/2016 07:22 PM, Frank Bulk via Outages wrote: > >> How seeing a new IP address, and so now HTTP loads give us a 503: >> >> root@nagios:/# wget -4 www.amazon.com >> --2016-04-22 12:21:03-- http://www.amazon.com/ >> Resolving www.amazon.com... 54.239.25.192 >> Connecting to www.amazon.com|54.239.25.192|:80... connected. >> HTTP request sent, awaiting response... 503 Service Unavailable >> 2016-04-22 12:21:03 ERROR 503: Service Unavailable. >> >> root@nagios:/# >> >> This IP address now goes via ZAYO rather than HE, but at least completes. >> >> Frank >> >> -----Original Message----- >> From: Outages [mailto:[email protected]] On Behalf Of Frank >> Bulk >> via Outages >> Sent: Friday, April 22, 2016 12:21 PM >> To: [email protected] >> Subject: [outages] HTTP access to www.amazon.com is down for us >> >> Anyone else see the same? >> >> root@nagios:/# wget -4 www.amazon.com >> --2016-04-22 12:19:00-- http://www.amazon.com/ >> Resolving www.amazon.com... 54.239.26.128 >> Connecting to www.amazon.com|54.239.26.128|:80... failed: Connection >> timed >> out. >> Retrying. >> >> --2016-04-22 12:19:22-- (try: 2) http://www.amazon.com/ >> Connecting to www.amazon.com|54.239.26.128|:80... failed: Connection >> timed >> out. >> Retrying. >> >> --2016-04-22 12:19:45-- (try: 3) http://www.amazon.com/ >> Connecting to www.amazon.com|54.239.26.128|:80... ^C >> root@nagios:/# >> >> >> root@nagios:/etc/cron.weekly# tcptraceroute www.amazon.com >> Selected device eth0.3, address 96.31.0.5, port 41361 for outgoing packets >> Tracing the path to www.amazon.com (54.239.26.128) on TCP port 80 (www), >> 30 >> hops max >> 1 router-core-inside.mtcnet.net (96.31.0.254) 0.258 ms 0.366 ms >> 0.356 >> ms >> 2 sxct.sxcy.mtcnet.net (167.142.156.197) 0.274 ms 0.173 ms 0.150 ms >> 3 premier.sxcy-mlx.fbnt.netins.net (173.215.60.5) 2.131 ms 1.453 ms >> 1.448 ms >> 4 ins-db4-te-0-6-0-4.219.desm.netins.net (167.142.60.157) 7.797 ms >> 7.594 >> ms 7.592 ms >> 5 ins-dc1-po200.desm.netins.net (167.142.67.193) 9.304 ms 9.177 ms >> 9.219 ms >> 6 ins-kc2-po20.kmrr.netins.net (167.142.67.30) 9.407 ms 10.021 ms >> 9.228 >> ms >> 7 v504.core1.oma1.he.net (184.105.18.169) 39.532 ms 32.855 ms >> 41.492 ms >> 8 10ge11-15.core2.chi1.he.net (184.105.81.229) 20.037 ms 20.076 ms >> 21.987 ms >> 9 100ge5-2.core1.chi1.he.net (184.105.81.98) 20.034 ms 20.106 ms >> 19.997 >> ms >> 10 100ge5-2.core1.nyc4.he.net (184.105.223.162) 40.097 ms 47.921 ms >> 38.699 ms >> 11 100ge11-1.core1.par2.he.net (184.105.81.78) 121.681 ms 113.899 ms * >> 12 10ge3-2.core1.zrh1.he.net (184.105.222.50) 140.341 ms 131.058 ms >> 139.553 ms >> 13 * * * >> 14 * * * >> 15 * * * >> 16 * * * >> 17 * * * >> 18 * * * >> ^C >> root@nagios:/etc/cron.weekly# >> >> >> >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] >> Sent: Friday, April 22, 2016 12:18 PM >> Subject: PROBLEM: Host amazon is DOWN! >> >> ***** Nagios ***** >> >> Host: This is a PROBLEM notice that Amazon is DOWN >> >> Date/Time: Fri Apr 22 12:18:06 CDT 2016 >> >> CRITICAL - Socket timeout after 10 seconds >> >> _______________________________________________ >> Outages mailing list >> [email protected] >> https://puck.nether.net/mailman/listinfo/outages >> >> >> _______________________________________________ >> Outages mailing list >> [email protected] >> https://puck.nether.net/mailman/listinfo/outages >> >> _______________________________________________ > Outages mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/outages >
_______________________________________________ Outages mailing list [email protected] https://puck.nether.net/mailman/listinfo/outages
