Thank you for the replies gentlemen.
I'm fully aware that the meters I own have references far inferior to the LTZ1000, but that doesn't reduce the usefulness of the KX references to me. Quite the opposite in fact as the KX reference is capable of showing up problems on the meter itself and I can still get a good impression of how stable the references are after burn in with my inferior meters. This should let me choose a good time to post them to a friendly cal lab or fellow volt nut for characterisation.
I'm still looking for a proper metrology grade meter and was in the running for a Datron 1281 yesterday, but the bidding quickly passed the limit of my test gear fund in the remaining few minutes of the auction. So for now, I'll have to make do with what I have.
When I first saw these excursions on the 7061, I immediately suspected the meter, but seeing them appear when using the other reference on the 34401A, I began to wonder if it was specific to the KX reference itself.
They are both being run at 12V from a Thurlby PL320 linear lab supply, so the power is quiet and stable.
I looked through the reference #2 log and found the three samples with large negative jumps and indeed just one sample is involved, just as the single line thickness on the plots would imply:
2020-03-30 23:46:44,24.90,30.28,1029.25,+7.11377860E+00
2020-03-30 23:46:46,24.90,30.28,1029.25,+7.11371180E+00
2020-03-30 23:46:48,24.89,30.29,1029.26,+7.11377920E+00
as is the big jump of 20ppm:
2020-03-31 00:07:38,24.86,30.41,1029.22,+7.11377630E+00
2020-03-31 00:07:40,24.86,30.41,1029.22,+7.11363070E+00
2020-03-31 00:07:42,24.86,30.41,1029.22,+7.11377340E+00
and the third blip at just after 00:30
2020-03-31 00:35:35,24.76,30.65,1029.10,+7.11377550E+00
2020-03-31 00:35:37,24.76,30.65,1029.10,+7.11369950E+00
2020-03-31 00:35:39,24.76,30.65,1029.10,+7.11377570E+00
The two spikes on the 7061 log from reference #1 are similar, just one sample blips, one just before midnight and one just after:
2020-03-22 23:48:20,25.52,31.14,1039.00,+7.134534
2020-03-22 23:48:36,25.52,31.14,1039.00,+7.134428
2020-03-22 23:48:52,25.52,31.14,1039.00,+7.134538
2020-03-23 00:04:06,25.27,31.40,1038.94,+7.134537
2020-03-23 00:04:22,25.27,31.40,1038.94,+7.134497
2020-03-23 00:04:38,25.27,31.40,1038.94,+7.134535
I also saw a line at just after midnight in the reference #2 log with a problem caused by my logging system where the script seems to have been updating the environmental data at the same time it was being copied to the new line in the log file resulting in missing fields between the time and voltage columns. (The script runs multiple background processes.) Oddly, gnuplot doesn't complain about the empty columns when it processes the file.
2020-03-31 00:09:57,24.89,30.51,1029.26,+7.11377890E+00
2020-03-31 00:09:59,,+7.11377990E+00
2020-03-31 00:10:02,24.92,30.51,1029.28,+7.11377880E+00
So I'll need to fix things so that can't happen again!
From this, I'd infer that the reference chips are thankfully not one of TiN's "little jumpers".
The reference that is currently connected to the 34401A is not using the leads in the picture. It is connected with a twisted pair of PTFE insulated silver plated copper wire with low thermal EMF spades on the reference end and Stäubli low mass banana plugs on the meter end. The reference connected to the 7061 would have been connected with the original Solartron measurement cable - also very high quality and shielded.
The only local interference source I can think of is my temperature/humidity/pressure sensor which is sitting on the desk near the reference under test in each case. This sensor reports back to a local MQTT server wirelessly, so there's a 2.4GHz wireless transceiver close by operating for a very short time every minute as the sensor publishes the latest readings.
I can imagine that transmission being capable of causing a disturbance, but with the 34401A returning a new reading every two seconds, I'd expect the disturbances to affect the result much more often than just two readings out of the nearly 41000 that there are currently in the log. I'd also expect the disturbance to have an equal possibility of generating a positive or negative going disturbance and I've never seen a positive one.
To attempt to see if that is the cause anyway, I'll move the sensor a few metres away from the desk and see if I have any ferrites to put on the power leads from the Thurlby supply. The temperature is fairly constant in my apartment, so moving the sensor away from the bench shouldn't affect the relevance of the data to any significant degree. At least it won't get caught by the morning sun as it did today, resulting in the temperature spike at around 08:00 before I shut the blinds on the windows.
edit: The line with the missing columns was not responsible for the largest 20ppm jump. My mistake.