OT: Whats with e-bay?

Could just mean that the hop after 12.122.85.85 doesn't accept ICMP packets.

--
"Electricity is of two kinds, positive and negative. The difference 
is, I presume, that one comes a little more expensive, but is more 
durable; the other is a cheaper thing, but the moths get into it." 
                                             (Stephen Leacock)

It's Comcast's issue. Lots of packet loss in this area today; I couldn't even reach Google reliably.

-- john

Site is essentially useless:

Tracing route to ebay.com [66.135.205.14] over a maximum of 30 hops:

1 * * * Request timed out. 2 7 ms 7 ms 8 ms te-7-2-ur03.olympia.wa.seattle.comcast.net [68.87.205.97] 3 10 ms 9 ms 9 ms ae-25-0-ar03.burien.wa.seattle.comcast.net [69.139.164.173] 4 16 ms 12 ms 11 ms ae-2-0-ar03.seattle.wa.seattle.comcast.net [68.86.177.146] 5 11 ms 12 ms 15 ms he-1-6-0-0-10-cr01.seattle.wa.ibone.comcast.net [68.86.94.69] 6 12 ms 11 ms 13 ms be-17-pe03.seattle.wa.ibone.comcast.net [68.86.83.14] 7 62 ms 25 ms * as7018.seattle.wa.ibone.comcast.net [66.208.229.98] 8 39 ms 37 ms 36 ms cr82.st0wa.ip.att.net [12.122.84.18] 9 40 ms 35 ms 36 ms cr2.ptdor.ip.att.net [12.122.5.230] 10 38 ms 39 ms 38 ms cr1.ptdor.ip.att.net [12.122.30.141] 11 39 ms 35 ms 36 ms cr1.sffca.ip.att.net [12.122.30.146] 12 40 ms 35 ms 40 ms cr83.sffca.ip.att.net [12.123.15.110] 13 43 ms 36 ms 35 ms gar8.sn1ca.ip.att.net [12.122.85.85] 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out.

Trace complete.

Excellent! I think I saw something that indicated that there was a provider problem. Anyway, I'm glad you were successful.

probably a backlog at the NSA...

Mark

• I did that then, a number of hours ago; see below.

• Yup! Works now.

Funny thing is, that Google and many other sites worked fine. The trace seemed to indicate a problem in the SF area (then).