504 gateway timeout on large tours

starting around 8/27/15, I’ve been getting a gateway timeout on large routes (up toward 80 addresses) when using the tour API.

Steps taken:
Tried a route with 4 addresses, it worked
Tried a route with 14 addresses to make sure the api wasn’t imposing a free-tier limit on me, that worked
Tried different PCs and different internet connections, no improvement

Please help, it seems to be due to a server change and I need this urgently

The server control panel was automatically updated and our custom timeout settings were overwritten. We’ve updated and they will be applied in 15 minutes.

Works great!

Hi, the problem returned, a route matrix with 100 address get a timeout. A tiny 5 address route is slower than normal but works. Is there anything I can do when facing these issues?