The timing is incongruous for sure. I’d expect any automatic gate would block it immediately, but any monitoring would surely take longer than one minute to be acknowledged and responded to.
My guess when I read this was that some sort of asynchronous verification system blipped and rather than blocking the transaction some record was tossed into a queue to process later.
But I really hope it was actually some support person watching a board in a NOC, or a server person that just happened to be tailing the purchase log, and they just happened to see google.com go across their screen. It’s fun to imagine the face they’d make.
One minute is a pretty fast turnaround. I wonder how they noticed and fixed the problem so quickly.
The timing is incongruous for sure. I’d expect any automatic gate would block it immediately, but any monitoring would surely take longer than one minute to be acknowledged and responded to.
My guess when I read this was that some sort of asynchronous verification system blipped and rather than blocking the transaction some record was tossed into a queue to process later.
But I really hope it was actually some support person watching a board in a NOC, or a server person that just happened to be tailing the purchase log, and they just happened to see
google.comgo across their screen. It’s fun to imagine the face they’d make.The latter scenario sounds more exciting, so I’ll consider that as fact.