3 ms·The incident was caused by a database query that was "2-22-22" when it was supposed to be "2-22-22".by bugeats 4y agoThe incident was caused by a database query that was "2-22-22" when it was supposed to be "2-22-22".