Data Feed Report

data provider: dealerslink

We have been tracking https://s3.us-east-1.amazonaws.com/sftp.dealertrend.com/users/dealerslink/DFGRecon... for at least 8 months now. In recent history, the data provider seems to be sending a data file 3 times per day.

total
722
Modification Events
reported last modified content length (bytes) http status hash
204,672 (200 KB) 200 ef90ffca03adb6d6d96463232aeed802bca52714
204,672 (200 KB) 200 f7216ce9b1629338a43979a1cd1717aa6c12d42e
204,672 (200 KB) 200 f7216ce9b1629338a43979a1cd1717aa6c12d42e
204,672 (200 KB) 200 f7216ce9b1629338a43979a1cd1717aa6c12d42e
204,672 (200 KB) 200 24f33e06d817a41febcbcdeedaaef0bae3c3dcda
207,299 (202 KB) 200 84c27ab1690ae3f21cdc3baf6e3d3f6117c9d700
207,299 (202 KB) 200 84c27ab1690ae3f21cdc3baf6e3d3f6117c9d700
207,299 (202 KB) 200 cf42882ee5e282a0b3f9c599075cbce80b9dded9
207,299 (202 KB) 200 cf42882ee5e282a0b3f9c599075cbce80b9dded9
207,299 (202 KB) 200 cf42882ee5e282a0b3f9c599075cbce80b9dded9
207,299 (202 KB) 200 001ef0315c3ea5a94e4f384063c4e53f256af90f
207,299 (202 KB) 200 001ef0315c3ea5a94e4f384063c4e53f256af90f
207,299 (202 KB) 200 001ef0315c3ea5a94e4f384063c4e53f256af90f
207,299 (202 KB) 200 c25ac67a31e3359a1f1505ba8fe63d0a64073ca6
207,299 (202 KB) 200 c25ac67a31e3359a1f1505ba8fe63d0a64073ca6
209,750 (205 KB) 200 2f8bfb3e7f4a6ece73e4e61af5c7cc2ca5863f8d
209,750 (205 KB) 200 ec31678ad56b08a227254d0f76fe344e758c929a
209,750 (205 KB) 200 ec31678ad56b08a227254d0f76fe344e758c929a
209,750 (205 KB) 200 ec31678ad56b08a227254d0f76fe344e758c929a
209,750 (205 KB) 200 bcba4b3abb9d8d28bc94ce1b5d4503f29f73b754
209,750 (205 KB) 200 bcba4b3abb9d8d28bc94ce1b5d4503f29f73b754
209,750 (205 KB) 200 bcba4b3abb9d8d28bc94ce1b5d4503f29f73b754
209,750 (205 KB) 200 ed808abed1d75d9ed6972a41f6e01e9bd22196a6
218,461 (213 KB) 200 dda156f4ef32d348a03abc1869ceb1f9becf2b88
218,461 (213 KB) 200 dda156f4ef32d348a03abc1869ceb1f9becf2b88

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 .

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

Last Request by data processor

It is unknown when our data processors (what we call TEA-pot) made the last request for this resource.

But... since this feed has been configured for a while now, it's possible this resource isn't being processed directly by TEA-pot, but that it is an ancillary resource (it's not the only one being 'watched'), or that it needs further pre-processing before it can be used.

For example, if CSV column headers need to be added or remapped — this slows down the processing latency.