This incident was caused by an internal data system using more resources than expected, which then caused processing of Events mode changes to become backlogged. Once additional server capacity was added, the backlog of changes was processed and the issue was resolved. We have adjusted our monitoring to more quickly identify this issue and are working on improvements to better allocate server resources to avoid this in the future.