Data Feed Report

data provider: carfax

We have been tracking https://s3.amazonaws.com/sftp.dealertrend.com/users/carfax/carfax-out.txt for at least 7 months now. In recent history, the data provider seems to be sending a data file 1 time per day.

total
202
Modification Events
reported last modified content length (bytes) http status hash
926,992 (905 KB) 200 0ab3b713c87749efd7ea6c01afda9f2151b90b2b
935,343 (913 KB) 200 c11f436147be61e7f968aa8783e39f45eac3d857
933,005 (911 KB) 200 34ee40679ca5f7f668cc75f814846743011106d0
935,257 (913 KB) 200 001ba47dd4569b0fa8e5e41c9ae6cc53d2fe9737
928,774 (907 KB) 200 353aae88688e278063023dc4a64bd9a3afd9d77a
missing
missing
missing
missing
missing
missing
missing
missing
missing
missing
missing
missing
missing
missing
missing
missing
missing
missing
missing
missing

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 .

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.