Hmmmm, those traceroutes are interesting, if they're really from the two different connections than I don't see why one would work and the other not.
Here's a portion of a Traceroute form a RoadRunner [TWC] cable network:
7 10 ms 10 ms 11 ms ae-5-0.cr0.chi30.tbone.rr.com [66.109.6.112]
8 9 ms 9 ms 9 ms ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
9 34 ms 35 ms 33 ms 66.109.9.202
10 135 ms 135 ms 135 ms PLUSLINE-AG-IP-SERVICES.ge-1-2-0.408.ar2.FRA2.gb
lx.net [208.49.181.90]
11 273 ms 204 ms 207 ms 82.98.65.222
12 129 ms 129 ms 129 ms 213.83.9.254
13 136 ms 132 ms 133 ms ae0-0.ts-r6.6861.ip.teresto.net [217.24.235.41]
14 133 ms 130 ms 129 ms ge-0.cr.wnd.de.manitu.net [212.88.130.82]
15 135 ms 133 ms 133 ms
www.safer-networking.org [89.238.64.39]
Trace complete.
Note that the last few hops are the same with only the last hop dropping out for you. I don't see a good explanation yet, though I'd guess it might be a peering issue of some sort. Traditionally I've seen most traffic to Safer Networking pass through Amsterdam with most Telco (e.g. AT&T) based connections, though I think they recently changed their hosting, so this may have changed to.
I really don't like going through France to get to Germany since they're normally badly peered in Southern Europe, but the actual times here are reasonable for a hop over the pond, so that's why I suspect an issue with peering for Comcast or Global Crossing (gblx.net)
Bitman