Thank you David.

Not your problem but...unfortunately for me, Wolfram fixing it "in the next release" is not good enough. I rely on the function in code I just wrote for a charity fundraiser happening next week (my scout troop will collect Christmas trees from 500+ homes in one day).

I'm further frustrated and disappointed because I purchased the last upgrade because of the new geographic information functions. Now I have to write my own TravelDirections function, just as I had to write my own version of FindGeoLocation for street addresses. To be fair, the Mathematica Documentation states only that FindGeoLocation["address"] "attempts to find the geo location associated with the street address given"

I'm having this problem too. TravelDirections worked for me two weeks ago. Now it doesn't. I tried updating to 10.3.1 but issue persists. I just sent a "feedback" message about the issue to Wolfram and will post any interesting response.

Hi @Ilian Gachevski , just kidding!

In the end, I don't care! The major.minor.patch updates are bigger than the major update of Matlab ;) In the end, the numbers doesn't really matter of course, the only big difference is a new logo or not ;)

In addition: it's strange because the 10.3.1 update specifically fixed some bugs with TravelDirections...

I am experiencing that problem quite regularly, e.g. in the context of AnatomicalStructure. My interpretation is that this timeout were due to my slow internet connection. I then have to try several times before I eventually get all the data. It would be interesting to know if this is the real reason.

This is not (I believe) a calculation that involves alpha calls: TravelDirections is a part of the Wolfram Language itself, though it requires cloud access to function.

However, I notice that the first example in the Documentation Center for TravelDirections,

TravelDirections[{Entity[ "City", {"Miami", "Florida", "UnitedStates"}], 
  Entity["City", {"NewYork", "NewYork", "UnitedStates"}]}]

also fails with $Failed["ComputationTimeout"] so something must be amiss with the server.

Something for the developers to attend to, I think!

I suspect that TravelDirections is simply broken at the current time.