Hello Sphinx,
I don't really understand why there's a time constraint in this challenge.
I mean, of course you want us to solve it programatically, but the server's response time is really bad depending on where you're... :-/
Just an example, my current average time to solve it is 32s, the best shot was 20s and the worst 78s... :-(
If the time constrait was related to the client side (as it's for 6/7 Traversal) it would make sense, but as I said, I can't see why make it in the server side...