Sirs, the issue might very well be the way that Twitter handles their inbound traffic. I am guessing they use a queuing mechanism that does not ensure first in, first out. An example of this would be a product called Apache Kafka.
However, we are way beyond the point of knowing that the time stamps are too close to be a random coincidence.
WWG1WGA!