Data Feed Report

data provider: impel_ai

We have been tracking https://s3.amazonaws.com/sftp.dealertrend.com/users/impel_ai/rvdepot.csv for at least 4 months now. In recent history, the data provider seems to be sending a data file 6 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: 736

Modification Events
reported	last modified	content length (bytes)	http status	hash
about 10 hours	about 10 hours	4,367,925 (4.17 MB)	200	3c511782b9b3a28a2ff4134816256d21463c40ae
about 10 hours	about 10 hours	4,367,925 (4.17 MB)	200	3c511782b9b3a28a2ff4134816256d21463c40ae
about 10 hours	about 10 hours	4,367,925 (4.17 MB)	200	3c511782b9b3a28a2ff4134816256d21463c40ae
1 day	1 day	4,367,925 (4.17 MB)	200	3c511782b9b3a28a2ff4134816256d21463c40ae
1 day	1 day	4,367,925 (4.17 MB)	200	3c511782b9b3a28a2ff4134816256d21463c40ae
1 day	1 day	4,367,925 (4.17 MB)	200	3c511782b9b3a28a2ff4134816256d21463c40ae
1 day	1 day	4,367,925 (4.17 MB)	200	3c511782b9b3a28a2ff4134816256d21463c40ae
1 day	1 day	4,367,925 (4.17 MB)	200	3c511782b9b3a28a2ff4134816256d21463c40ae
1 day	1 day	4,367,925 (4.17 MB)	200	3c511782b9b3a28a2ff4134816256d21463c40ae
2 days	2 days	4,367,925 (4.17 MB)	200	3c511782b9b3a28a2ff4134816256d21463c40ae
2 days	2 days	4,367,925 (4.17 MB)	200	3c511782b9b3a28a2ff4134816256d21463c40ae
2 days	2 days	4,367,925 (4.17 MB)	200	3c511782b9b3a28a2ff4134816256d21463c40ae
2 days	2 days	4,367,925 (4.17 MB)	200	3c511782b9b3a28a2ff4134816256d21463c40ae
2 days	2 days	4,367,925 (4.17 MB)	200	3c511782b9b3a28a2ff4134816256d21463c40ae
2 days	2 days	4,367,925 (4.17 MB)	200	3c511782b9b3a28a2ff4134816256d21463c40ae
3 days	3 days	4,361,007 (4.16 MB)	200	a7c36349a023e0c6055f19f825ff2039d400ad9c
3 days	3 days	4,358,151 (4.16 MB)	200	743ede6acec1f77c8a01cadd147fcd74a7217914
3 days	3 days	4,357,901 (4.16 MB)	200	e2d6a69577d89b053274a1473a4f8b2af69834d1
3 days	3 days	4,357,901 (4.16 MB)	200	e2d6a69577d89b053274a1473a4f8b2af69834d1
3 days	3 days	4,357,901 (4.16 MB)	200	e2d6a69577d89b053274a1473a4f8b2af69834d1
3 days	3 days	4,357,901 (4.16 MB)	200	e2d6a69577d89b053274a1473a4f8b2af69834d1
4 days	4 days	4,358,121 (4.16 MB)	200	79e86a08b3951abe2604f6c5c0c06bf7839c902b
4 days	4 days	4,358,121 (4.16 MB)	200	79e86a08b3951abe2604f6c5c0c06bf7839c902b
4 days	4 days	4,357,681 (4.16 MB)	200	fd9991af7bf647d7e47fba9b03917746aab8e83d
4 days	4 days	4,357,681 (4.16 MB)	200	fd9991af7bf647d7e47fba9b03917746aab8e83d

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 10 hours .

We have determined that the resource was actually modified 2 days , 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.