(10:33pm ET — <a href="http://www.timeanddate.com/worldclock/fixedtime.html?iso=2017-04-22T02:33:20">See this in your timezone</a>) Our engineers are aware that search indexing is lagging behind. We've identified the cause and it should recover shortly.
(10:39pm ET — <a href="http://www.timeanddate.com/worldclock/fixedtime.html?iso=2017-04-22T02:39:04">See this in your timezone</a>) Search backlog has caught up and things are performing normally again.
RESOLVED at 10:39pm ET — <a href="http://www.timeanddate.com/worldclock/fixedtime.html?iso=2017-04-22T02:39:19">See this in your timezone</a>
No components marked as affected
Resolved
(10:33pm ET — <a href="http://www.timeanddate.com/worldclock/fixedtime.html?iso=2017-04-22T02:33:20">See this in your timezone</a>) Our engineers are aware that search indexing is lagging behind. We've identified the cause and it should recover shortly.
(10:39pm ET — <a href="http://www.timeanddate.com/worldclock/fixedtime.html?iso=2017-04-22T02:39:04">See this in your timezone</a>) Search backlog has caught up and things are performing normally again.
RESOLVED at 10:39pm ET — <a href="http://www.timeanddate.com/worldclock/fixedtime.html?iso=2017-04-22T02:39:19">See this in your timezone</a>