Very Urgent - Mapquest api issue - blacklisted

11 posts / 0 new
Last post
support.59
Very Urgent - Mapquest api issue - blacklisted

Hello,

We have had major problems with our applications connecting to the mapquest api starting roughly between 9am and 10am GMT. We are still getting these problems at 2:24pm GMT. It was working earlier before encountered this problem and was working yesterday as well.

We believe that our server’s IP address has been blacklisted.

I have sent an email to support@mapquest.com and sales@mapquest.com with the IP address in question

We have tried accessing open.mapquestapi.com via the server however we get a page cannot be displayed. This has worked properly before, and works on any other sever/machine.

There has been no changes to our network/firewall or server

Could you advise if our IP address has been blacklisted and how we can get this issue resolved so we can continue using the service.

This is currently a system down for us and is causing us major problems. I would highly appreciate it if this issue could be looked into swiftly.

 


MQBrianCoakley
Have you been able to run any
Have you been able to run any traceroutes?

support.59
To add. We have 3 servers all

To add. We have 3 servers all sharing the same DNS with different IP addresses. The api and url works on 2 of those servers, but does not work on the server which we need it to work on. The IP address affected is: 185.8.109.106  the traceroute results are the same on all 3 servers.

See below the tracert:

tracert open.mapquestapi.com

Tracing route to mapquest-02.dn.apigee.net [52.4.164.253]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  10.10.100.254
  2    <1 ms    <1 ms    <1 ms  185.8.108.3
  3    <1 ms    <1 ms    <1 ms  ge-0-1-0-5.cr01.tv2-rdg.pulsant.net [89.151.95.2
38]
  4     2 ms     2 ms     2 ms  te-0-0-0-0.cr01.hex-lon.pulsant.net [89.151.95.1
77]
  5     2 ms     2 ms     2 ms  te-0-0-0-2.cr02.the-lon.pulsant.net [89.151.95.8
6]
  6     5 ms     1 ms     1 ms  xe-7-2-3.mpr1.lhr15.uk.zip.zayo.com [94.31.32.20
9]
  7     2 ms     2 ms     2 ms  ae4.mpr3.lhr3.uk.zip.zayo.com [64.125.21.1]
  8    78 ms    77 ms    77 ms  ae27.cs1.lhr15.uk.eth.zayo.com [64.125.30.234]
  9    77 ms    78 ms   117 ms  ae5.cs1.dca2.us.eth.zayo.com [64.125.29.131]
 10    77 ms    77 ms   112 ms  ae0.cs2.dca2.us.eth.zayo.com [64.125.29.229]
 11    77 ms    77 ms    77 ms  ae27.cr2.dca2.us.zip.zayo.com [64.125.30.249]
 12    77 ms    77 ms    77 ms  ae15.er5.iad10.us.zip.zayo.com [64.125.31.42]
 13    77 ms    77 ms    77 ms  zayo-amazon.iad10.us.zip.zayo.com [64.125.12.30]

 14    96 ms   104 ms   101 ms  54.239.108.142
 15    80 ms    78 ms    78 ms  54.239.108.161
 16    78 ms    78 ms    78 ms  205.251.245.174
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.


support.59
Hi Brian,

Hi Brian,

I can confirm we are able to run traceroutes, we have sent the results to the support email. We have run the traceroutes on both working and non-working servers with both bringing back the same results


MQBrianCoakley
We are working with our
We are working with our authentication layer team to find out if anything changed today. Please stand by...

MQBrianCoakley
We are seeing requests from
We are seeing requests from the ip above in our logs so they are getting to us and being responded to as expected. 

support.59
It has just this second

It has just this second started working again. Could you find out what would have happened to cause these problems to occur. It would really help us to understand for future reference so that we can attempt to get it resolve in a more timely manner.


MQBrianCoakley
Unfortunately, no. There were
Unfortunately, no. There were no changes on our end. Changes are made during the regular Tuesday and Thursday 4-6 am ET maintenance window. Nothing new was done during this morning's window.

support.59
Many thanks for your time and

Many thanks for your time and swift responses Brian. Have a great day!


MQBrianCoakley
This just came in from 185.8
This just came in from 185.8.109.106.   /directions/v1/route?key=KEY&outFormat=xml&from=51.7136442076449%2C-3.03738484989756&to=51.6430843530967%2C-3.03877932666604&callback=renderNarrative&routeType=shortest   The response sent back was   <?xml version="1.0" encoding="UTF-8"?> <response><info><statusCode>0</statusCode><messages/><copyright><imageUrl>http://api.mqcdn.com/res/mqlogo.gif</imageUrl><imageAltText>© 2015 MapQuest, Inc.</imageAltText><text>© 2015 MapQuest, Inc.</text></copyright></info><routeError><errorCode>-400</errorCode><message></message></routeError><route><sessionId>56bca948-013f-000e-02b7-1078-00163eb64fa8</sessionId><options><shapeFormat>raw</shapeFormat><generalize>-1.0</generalize><maxLinkId>0</maxLinkId><nar...  So all looks great on our side.

MQBrianCoakley
We see this ip in both
We see this ip in both directions/v1 and directions/v2.