For the most part the absolute timestamps I see make sense, and are within a few seconds of the request time. Then every now and then I see some extremely absurd timestamps and I don't know what to make of them. Here's a sample:
112731879 (Safari 4 on Mac OS X 10.4.11 (PPC)) 574766408 (Android 2.3.1) 6855660455 (iOS 4.2.1 on iPad) 5000 (Safari 3.1) 356902853 (Mobile Safari 4.0.4 on iOS 3.2 (iPad)) 133643085 (Mobile Safari 5.0.2 on iPhoneOS 4.2.1 (iPod)) 2775235876 (Mobile Safari 4.0.5 on iPhoneOS 4.1 (iPod))
While it looks like these are mostly mobile devices, there are a couple in there that aren't. Note that all these timestamps should be milliseconds, so there should be 13 digits for anything recent.
I've searched the net, but I either don't have a good search query, or there's nothing out there that talks about this. I've tested out my own iOS devices and get 13 digit timestamps, so I have no idea what these could be. Any ideas/suggestions for where to look or what to look for would be appreciated.
I understand that some of these request might just be fake, but the rest of the user's browsing pattern suggests that they're legitimate users of a website.
Any chance this could be related to the unreliable system clock that Date() is based on? The new performance.now() API is supposed to help address such issues (though I don't know how common this issue should be in the real world, or why mobile would be affected so drastically.)