Data Feed Report

data provider: vauto

We have been tracking https://s3.amazonaws.com/sftp.dealertrend.com/users/vauto/3048.csv for at least 10 months now. In recent history, the data provider seems to be sending a data file 7 times per day.

Historical Data
Data Feed Analysis

days: 7 30 60 90 180 365

Number of exports over time grouped by 12 hr blocks

HTTP Content-Length over time

total: 2036

Modification Events
reported	last modified	content length (bytes)	http status	hash
about 23 hours	about 23 hours	3,433,921 (3.27 MB)	200	2429501bb5b9a978f502a10bcaf2c4511474dfd3
about 23 hours	about 23 hours	3,433,921 (3.27 MB)	200	2429501bb5b9a978f502a10bcaf2c4511474dfd3
about 23 hours	about 23 hours	3,433,921 (3.27 MB)	200	2429501bb5b9a978f502a10bcaf2c4511474dfd3
about 23 hours	about 23 hours	3,489,829 (3.33 MB)	200	9cde123f8d4794f7421c0b2b804ce259115198bb
about 23 hours	about 23 hours	3,489,829 (3.33 MB)	200	9cde123f8d4794f7421c0b2b804ce259115198bb
about 23 hours	about 23 hours	3,527,730 (3.36 MB)	200	ce91b75abfe0e10e90622e44fe473c2572bbd35a
2 days	2 days	3,527,794 (3.36 MB)	200	da6d3bc442696141d8060b3d3e406ecb4ef3b5b5
2 days	2 days	3,524,880 (3.36 MB)	200	0b17fefa93acdd7d80aa19df7af86c28122782ef
2 days	2 days	3,535,690 (3.37 MB)	200	6bcc56869836e828f8db7767d682addfbebd7472
2 days	2 days	3,535,690 (3.37 MB)	200	6bcc56869836e828f8db7767d682addfbebd7472
2 days	2 days	3,562,913 (3.4 MB)	200	1e1dcf5f3b63bec09a44bb7c515139fef397d9ac
2 days	2 days	3,562,913 (3.4 MB)	200	1e1dcf5f3b63bec09a44bb7c515139fef397d9ac
2 days	2 days	3,545,877 (3.38 MB)	200	da9e15d6e73770fb1afdac77019aee269112380c
3 days	3 days	3,541,639 (3.38 MB)	200	5c1e4ca77dd6ecc537f24635b6cafa81998e47a8
3 days	3 days	3,531,880 (3.37 MB)	200	4165144f44372a0902c1c9239df36690fd353ec5
3 days	3 days	3,527,857 (3.36 MB)	200	94b671859d0788050c56490c588d39cd7497d8d7
3 days	3 days	3,527,857 (3.36 MB)	200	94b671859d0788050c56490c588d39cd7497d8d7
3 days	3 days	3,592,751 (3.43 MB)	200	546162871d93cca44beab61f670f91b6a096ea5f
3 days	3 days	3,592,751 (3.43 MB)	200	546162871d93cca44beab61f670f91b6a096ea5f
3 days	3 days	3,586,184 (3.42 MB)	200	e29d8f8b2c1537d43ffb075bff6aa7e034697874
4 days	4 days	3,586,273 (3.42 MB)	200	97c022db67973739e2c5b546db1d99d36a6f4708
4 days	4 days	3,578,705 (3.41 MB)	200	0dc13f1a25ae71320f7e8587e665ef6e9fc2334d
4 days	4 days	3,481,440 (3.32 MB)	200	db163ce171b265785ef8a77586dee4168e00f9a5
4 days	4 days	3,481,440 (3.32 MB)	200	88fae2a4f1c28ea11954a84584099e1520554c32
4 days	4 days	3,511,861 (3.35 MB)	200	8cd5007735d25ae66419c1b704c2d3e9cbfa569b

Normality have there been any abrupt file status changes?

Good News!

We have determined that the size of this data feed looks like what we would consider 'normal'.

Last-Modified

We do know that the resource itself says it was modified about 23 hours .

We have determined that the resource was actually modified about 23 hours , so the last data file has not been scheduled for processing.

Last Request by data processor

The data processor (TEA-pot) last checked if there was an update 6 days . There may be a configuration change that has caused this file to stop being watched.