See no issues from here in the Denver area. Can't ping or trace to it either, but figure that is by design. Site is coming up here fine though...
Chris On 07/28/2014 09:23 AM, James Wininger via Outages wrote: > From the IND area (looks down to me). > > [root@copper ~]# traceroute www.ebay.com > traceroute to www.ebay.com (66.135.210.181), 30 hops max, 40 byte packets > 1 host1.indianafiber.net (64.184.1.1) 0.594 ms 0.531 ms 0.468 ms > 2 208.103.3.185 (208.103.3.185) 1.010 ms 0.952 ms 0.896 ms > 3 (69.160.211.29) 1.223 ms 1.888 ms 1.078 ms > 4 xe-10-3-0.bar2.Cincinnati1.Level3.net (4.59.42.17) 3.622 ms 3.592 ms > 3.708 ms > 5 ae-0-11.bar1.Cincinnati1.Level3.net (4.69.136.209) 3.724 ms 4.040 ms > 3.880 ms > 6 ae-10-10.ebr2.Chicago1.Level3.net (4.69.136.214) 10.051 ms 9.985 ms > 9.911 ms > 7 ae-5-5.ebr2.Chicago2.Level3.net (4.69.140.194) 9.844 ms 9.780 ms > 10.369 ms > 8 ae-2-52.edge3.Chicago3.Level3.net (4.69.138.168) 10.311 ms 10.249 ms > 10.136 ms > 9 sl-st20-chi-10-0-0.sprintlink.net (144.232.8.113) 9.989 ms > sl-st20-chi-14-0-0.sprintlink.net (144.232.19.173) 10.251 ms 10.186 ms > 10 sl-crs2-chi-0-12-2-0.sprintlink.net (144.232.19.145) 15.594 ms > 13.142 ms 12.631 ms > 11 144.232.11.234 (144.232.11.234) 22.400 ms 21.405 ms 22.623 ms > 12 144.232.12.139 (144.232.12.139) 38.565 ms 38.472 ms 37.537 ms > 13 144.232.11.178 (144.232.11.178) 37.476 ms 37.420 ms 37.206 ms > 14 * * * > 15 * * * > 16 * * * > 17 * * * > 18 * * * > 19 * > [root@copper ~]# ping www.ebay.com > PING www.g.ebay.com (66.135.210.61) 56(84) bytes of data. > > --- www.g.ebay.com ping statistics --- > 23 packets transmitted, 0 received, 100% packet loss, time 22103ms > > [root@copper ~]# > > > > _______________________________________________ Outages mailing list [email protected] https://puck.nether.net/mailman/listinfo/outages
