First seen on February 3 at 8:39 UTC
There are a variety of IP addresses that throw the "Duplicate entry" error. There are 19,983 instances of the error appearing since February 3.
In subsequent imports, we see "Found failed batches from a previous run; attempting to re-import batches from an update from 20240202 to 20240203" but this ends up triggering the same errors again.
In practice, I think that means the production DB contains a mix of data newer than February 3rd, and stale entries.
See also: