Many time out errors getting directions

19 posts / 0 new
Last post
LogMyDriveAdmin
Many time out errors getting directions

For the past week or so we have been seeing many time out errors from directions API (20 second timeout limit). Usually the response is fast, but now we get missing routes when the query fails.


MQBrianCoakley
There were two issues that
There were two issues that caused some slow response times from the geocoder last week. Geocoder issues can affect other requests, like directions, that rely on the geocoder. There were some long response times but many 20 second responses may be an issue outside of the MapQuest APIs. Are you still seeing these issues?

LogMyDriveAdmin
Yes, we do still get timeout

Yes, we do still get timeout errors. The problems are specifically with directions API, geocoding and reverse geocoding requests are working.


stefan.barfred
Response time really went bad over the last month.

As seen on this table the response time have gotten really bad over the last 7 days. Before Jan 16 average response time was subsecond, but now the same type of requests easily takes more than 7 seconds?  So I will just say that there are still something wrong.

Date
 Response
time mS 

2021-01-02
                         158

2021-01-04
                         238

2021-01-05
                         248

2021-01-06
                         340

2021-01-07
                         275

2021-01-08
                         332

2021-01-11
                         380

2021-01-12
                         476

2021-01-13
                         401

2021-01-14
                     2.299

2021-01-15
                         552

2021-01-17
                         317

2021-01-18
                         630

2021-01-19
                         626

2021-01-20
                     1.746

2021-01-21
                         975

2021-01-23
                         614

2021-01-24
                         663

2021-01-25
                     1.016

2021-01-26
                     1.390

2021-01-27
                     1.877

2021-01-28
                     3.733

2021-01-29
                     7.336

2021-01-30
                     9.481

2021-02-01
                     8.948

2021-02-02
                     8.600

 


MQBrianCoakley
Are these figures average or
Are these figures average or max response time? Do you have sample requests to www.mapquestapi.com that are taking 8+ seconds?

MQBrianCoakley
Monitors on our side show max
Monitors on our side show max average response times spiked to 500ms during off-peak hours for directions/v2.

stefan.barfred
I have included some examples response times feb 1 & 2

The response time is in mS as stated and measured from our end. Our server is in Azure West-Europe region.

These are the complete request and response , please note the missing http and secretkey:

2021-02-01 14:42:09 [20] DEBUG - MapQuest ResponseTime #10401# mS on #open.mapquestapi.com/directions/v2/route?key=SECRETKEY&outFormat=json&routeType=fastest&timeType=1&enhancedNarrative=false&shapeFormat=raw&generalize=0&locale=en_US&unit=k&from=55.69812157,12.45591365&to=55.66775100,12.42125900&drivingStyle=2&highwayEfficiency=21.0
2021-02-01 14:46:00 [13] DEBUG - MapQuest ResponseTime #20364# mS on #open.mapquestapi.com/directions/v2/route?key=SECRETKEY&outFormat=json&routeType=fastest&timeType=1&enhancedNarrative=false&shapeFormat=raw&generalize=0&locale=en_US&unit=k&from=55.66775100,12.42125900&to=55.66079708,12.35807127&drivingStyle=2&highwayEfficiency=21.0
2021-02-01 15:09:38 [28] DEBUG - MapQuest ResponseTime #20479# mS on #open.mapquestapi.com/directions/v2/route?key=SECRETKEY&outFormat=json&routeType=fastest&timeType=1&enhancedNarrative=false&shapeFormat=raw&generalize=0&locale=en_US&unit=k&from=55.68542906,12.58901706&to=55.69039953,12.53388756&drivingStyle=2&highwayEfficiency=21.0
2021-02-01 15:17:23 [20] DEBUG - MapQuest ResponseTime #557# mS on #open.mapquestapi.com/directions/v2/route?key=SECRETKEY&outFormat=json&routeType=fastest&timeType=1&enhancedNarrative=false&shapeFormat=raw&generalize=0&locale=en_US&unit=k&from=55.72950500,12.49793900&to=55.74400925,12.50030851&drivingStyle=2&highwayEfficiency=21.0

2021-02-02 15:13:19 [8] DEBUG - MapQuest ResponseTime #1212# mS on #open.mapquestapi.com/directions/v2/route?key=SECRETKEY&outFormat=json&routeType=fastest&timeType=1&enhancedNarrative=false&shapeFormat=raw&generalize=0&locale=en_US&unit=k&from=55.71114892,12.42232938&to=55.67677179,12.56529121&drivingStyle=2&highwayEfficiency=21.0
2021-02-02 15:29:36 [8] DEBUG - MapQuest ResponseTime #20861# mS on #open.mapquestapi.com/directions/v2/route?key=SECRETKEY&outFormat=json&routeType=fastest&timeType=1&enhancedNarrative=false&shapeFormat=raw&generalize=0&locale=en_US&unit=k&from=55.70070400,12.50077500&to=55.98989562,11.90888235&drivingStyle=2&highwayEfficiency=21.0
2021-02-02 15:31:42 [8] DEBUG - MapQuest ResponseTime #10654# mS on #open.mapquestapi.com/directions/v2/route?key=SECRETKEY&outFormat=json&routeType=fastest&timeType=1&enhancedNarrative=false&shapeFormat=raw&generalize=0&locale=en_US&unit=k&from=55.70070400,12.50077500&to=56.11112554,12.35823287&drivingStyle=2&highwayEfficiency=21.0
2021-02-02 15:32:07 [25] DEBUG - MapQuest ResponseTime #361# mS on #open.mapquestapi.com/directions/v2/route?key=SECRETKEY&outFormat=json&routeType=fastest&timeType=1&enhancedNarrative=false&shapeFormat=raw&generalize=0&locale=en_US&unit=k&from=55.61362304,12.61463802&to=55.68403541,12.49270702&drivingStyle=2&highwayEfficiency=21.0
2021-02-02 15:33:27 [18] DEBUG - MapQuest ResponseTime #20515# mS on #open.mapquestapi.com/directions/v2/route?key=SECRETKEY&outFormat=json&routeType=fastest&timeType=1&enhancedNarrative=false&shapeFormat=raw&generalize=0&locale=en_US&unit=k&from=55.70070400,12.50077500&to=56.11112554,12.35823287&drivingStyle=2&highwayEfficiency=21.0


stefan.barfred
Responsetime table

The response time in my first table is from developer.mapquest website "App performance" under manage keys.

 


stefan.barfred
responsetime

Please note that my server is running with European customer, so I am not sure what you mean with offpeak hours?


MQBrianCoakley
The vast majority of MapQuest
The vast majority of MapQuest users are in the US so off-peak is outside of US office hours.

stefan.barfred
Spam message

This forum is very fast to complain about my posts being spam. This is why they have been split over multiple posts. I did not like the word "a.n.y.w.a.y".


MQBrianCoakley
That's odd. "anyway" is not
That's odd. "anyway" is not in the list of protected words for the forum.

LogMyDriveAdmin
Much better today

Directions are working much better today for us, last error was just after midnight. Yesterday was bad but now things seem to be working.


LogMyDriveAdmin
I have problems with spam

I have problems with spam filter as well.


LogMyDriveAdmin
Well, I spoke too soon. Since

Well, I spoke too soon. Since 11:30+0 today we get constant timeout errors.


MQBrianCoakley
Are you also using open
Are you also using open.mapquestapi.com/directions/v2/route or are you using a different base URL?

stefan.barfred
Should I use another URL?

Should I use another URL?


LogMyDriveAdmin
We use open.mapquestapi.com

We use open.mapquestapi.com/directions/v2/route, yes.

We are based in Europe and the issue yesterday was less severe outside US business hours.


MQBrianCoakley
Response times should, and
Response times should, and look like they have, returned to normal levels. Sorry for any inconvenience.