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 6 months now. In recent history, the data provider seems to be sending a data file 1 time per day.

total
159
Modification Events
reported last modified content length (bytes) http status hash
1,090,601 (1.04 MB) 200 f14c114e24bc885e13f175902c1f42b68970269f
1,095,013 (1.04 MB) 200 164b60cf5f5e7343a33a6cc6d10a5d166c253e65
1,080,913 (1.03 MB) 200 5dfbc33628d0bbb2a315d04baa8ea6cd40ed1bf9
1,077,375 (1.03 MB) 200 4dedd0ace7af8a16c36acbc578e7d67e1f61f343
1,086,402 (1.04 MB) 200 a382d26807d219327aa7b9eab8f354bbf9de8776
1,094,483 (1.04 MB) 200 74ea9b5f13b26c87987b7b74cd3e77d480520ea8
1,118,734 (1.07 MB) 200 a31286c4c001a5952b1034947a681e0e669a7c7a
1,125,457 (1.07 MB) 200 b7d1b925b1312859ac91d62138c3a1df3de06e50
1,065,159 (1.02 MB) 200 bb5ce4b81a0f846da45501aacfbddd40682584d8
1,058,739 (1.01 MB) 200 6af5a1a1e181bc81030afd9ecf019ffae76ada53
1,049,637 (1 MB) 200 7ebec477c2848e33e8efd60401ca09bd7b9f8e47
1,054,272 (1.01 MB) 200 273487447c139a60e4dda7721ddc7fcaa6df5a41
1,058,351 (1.01 MB) 200 1632a6d442ea396ab36b890e626af508d4b8ac32
1,042,147 (1020 KB) 200 42b0d8687310e2a3cde47fea889e26b12eb61af8
1,036,050 (1010 KB) 200 ae9202987ffb127b71b6c079d710f3d5abefb418
997,382 (974 KB) 200 590dbfc7eb2f75eb0dc633f5157f18fe80cd2c69
989,300 (966 KB) 200 2a8c18a54b5383334a21e02758572ff3aee07d47
968,828 (946 KB) 200 e06b87b55637bdaa6f1b5334cc1bd272c7b0cb16
991,822 (969 KB) 200 7470424c188211b9aeaad85be9d4ce85676c469c
1,007,193 (984 KB) 200 6b6ce3d7010203f7e8a142a60f0593de3708a27e
986,708 (964 KB) 200 1dd81d0153f68708e6236ea178d43192d126ce8f
972,635 (950 KB) 200 2c05e4d083b8535df20c8a04d9d89454b6d55394
972,337 (950 KB) 200 ba61dec1e6c2ab4857c7496985b4433301b54057
959,320 (937 KB) 200 d155ae1bce718029cf35fafc827671a06ac5020c
946,513 (924 KB) 200 c6a60b20c916c8f6393657cc2d1910c8cce06107

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.