Looking back on my system for what happened on the 12th, it looks like the appropriate updates DID go out because the timestamp updated, but the data INSIDE the file for the last 6 hours of the day froze.  My system ended up collecting an off time update at 1:07 am the next morning as the server spit out a fully updated file that caught us back up.  Man, sometimes the Stanford data files pull some weird things. But, doing my updates hourly and for our contests, I've pretty much gotten used to all the esoteric issues they've produced over time.
 
However, now that EVGA's system is updating, it's still a bit out of whack for when it's listing the start of this month. There's gonna be a LOT of grumpy people come the end of the month when they can't get their bucks that they've absolutely done the appropriate work for. OR, there's going to be a LOOOOOOT of work on the back end manually checking points for folks so they can manually request the correction if the IT folks can't get it sorted.
 
If need be, I can set up a google sheet comparing start of month to end of month to make things easier, should it come down to that.
 
d