4 ms·
"We have identified the root cause of this incident. It has been traced back to a cert issue triggered on 2/29/2012 GMT"
by joshmaker 15y ago
"We have identified the root cause of this incident. It has been traced back to a cert issue triggered on 2/29/2012 GMT"
- viraptor 15y agoIt's a bit unfortunate description of time, I think. They could at least say "2/29/2012 01:45 GMT". Otherwise it looks like there's a different date in each timezone (yeah, there are two different ones, but not different in each, the bug started closer to beginning of 2/29/2012 GMT+2).