Data Feed Report

data provider: pixelmotion

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

days: 7 30 60 90 180 365

Number of exports over time grouped by 12 hr blocks

HTTP Content-Length over time

total
140
Modification Events
reported last modified content length (bytes) http status hash
11,344 (11.1 KB) 200 27631d013525919e425bfe50e2babbcd3ee21ee7
11,486 (11.2 KB) 200 0cd94b27139f57a974dd9e5ef3fef45a5fe1b435
11,486 (11.2 KB) 200 0cd94b27139f57a974dd9e5ef3fef45a5fe1b435
11,486 (11.2 KB) 200 c13c5a3e5ac2bb2767ec3674efd25119c1005b96
11,526 (11.3 KB) 200 e2cbed50b1b1abd226ffde9df64f1e773d6a2714
11,511 (11.2 KB) 200 8fd4d3e08855971c8b4a29b2e472b28c1840fdc1
11,726 (11.5 KB) 200 95a8b067d8796ce9d8a2f56b4e59380c9e9e0390
11,843 (11.6 KB) 200 e35e7a8c60497332d12a17f0d8ab98814cee13a3
11,843 (11.6 KB) 200 0a4ce67458838ffecb87ab43f71f94e42de8bfe7
12,024 (11.7 KB) 200 721f6f934aaa0d86f750b562a1fa8c8db9a665c4
12,024 (11.7 KB) 200 7885913b365c00e46e16284f53d68ca5d78c0332
12,352 (12.1 KB) 200 d097f15a0f22126de5802eae612462130f81b5be
12,324 (12 KB) 200 eee78708a3d45936f2eec6cbbc94a8049e259327
12,324 (12 KB) 200 8d33af8b9623edb74dd8a73c3bb26eda41bdd80b
12,475 (12.2 KB) 200 10f17001d90879fbe3b7df7245aaa75211c3c8a6
12,843 (12.5 KB) 200 b6ae0f518a1eb8f256300563ae2969e5fa58e1f3
12,839 (12.5 KB) 200 86addb116b84e44de9edf752ed3a98d894ea26c0
12,667 (12.4 KB) 200 0d3eb6c4d1cd278ecb2efb53ba7e0574b6ef5cc3
12,844 (12.5 KB) 200 1a611ce76835b01884167eadd028781ab5ebbf9d
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.