Transaction Count just doesn't make sense

9 posts / 0 new
Last post
eantar@nyc.rr.com
Transaction Count just doesn't make sense

I looked at the database table that stores the number of distrance transactions and new address. Each one has TEN records, since I reverted back to my Free Plan of 15,000 transactions. Yet I got an email saying we've used 80% of our transactions. This just doesn't make sense. I looked at the transaction report show a rediculous amount of transactions on 1/19 and 1/22, totalling 6,155 direction transactions and 11,979 Geocoding Transactions for the period.

I don't know for sure, but some of this might have been during the period where my plan was to revert back to the Free Plan, but it did not.

Can you please tell me what's going on? This system is live and we need to address this ASAP.

 

Thank you.

Eddie


MQBrianCoakley
If the table has 10 records,
If the table has 10 records, How many directions requests are expected?  How many geocode requests are expected?

eantar@nyc.rr.com
Each record only has a

Each record only has a starting location, an ending location and a distance. AND most most transactions don't have to lookup the Geocodes as they are already established and saved. 

I'm worried about this. this is the second time this has happened. 

Any thoughts?

Thanks,

Eddie

 

 


MQBrianCoakley
The MapQuest api Terms &
The MapQuest api Terms & Conditions 3.a.vi says, "Customer shall not store or cache any MapQuest Data".   If a lat/lng is used for routing, is the doReverseGeocode parameter set to false?   Does the application or the network log outgoing requests? We have not had any issues with the reporting over indicating any users' usage. We've seen several cases of an application either not optimally set up or unknowing run multiple times. I suspect the reporting numbers are correct.

MQBrianCoakley
Looking at the log from 1/22,
Looking at the log from 1/22, I first see 17 routes from 183.82.68.167 (ras.beamtele.net), then 3 (the only ones with lat/lng instead of addresses) from 66.112.206.3 (host3-206.matrixconsulting.net). After that there are batches of up to 123 repeats of the same requests from 64.62.46.131 (remote.ltcmn.org). All of the requests have the same format, parameters, and key. A sample repeated request was from=2603 19TH AVE SE, ROCHESTER, MN  55904&to=1848 Second Ave SE, Rochester, MN  55904. 685 of the repeats were to=1323 E Front Ave #2, Bismarck, ND  58504 and 1666 to=1848 Second Ave SE, Rochester, MN  55904.

eantar@nyc.rr.com
Hi, I'm just not sure what's

Hi, I'm just not sure what's going on.

ALL of the mileage that's retrived is done so by sending the Lat, Long. ALL of the addresses are in the New York City region. None of that makes any sense.

 

I will try and see if those IP Addresses are correct.

 

 

 


MQBrianCoakley
The 3 routes that use lat/lng
The 3 routes that use lat/lng are in the NY area. If needed you can create a new key in the Keys & Reporting page and we can shut off the old key on our end once you're ready.

eantar@nyc.rr.com
Hey, sorry I haven't

Hey, sorry I haven't responded in a while.

Of the three IP addresses that you've listed, only one is recognizeable. The one that had 3 requests. The other two are a total mystery. So I believe that my Key code has been hacked. Please shut down my application. There should be no one else using this key.

 

Thanks,

Eddie

 

 

 


MQBrianCoakley
The key is now revoked and
The key is now revoked and you can create a new key in the Keys & Reporting section to go forward with.