Our data processing recovered completely at 4:00 am PDT. We are processing data without delay currently.
Posted Apr 02, 2018 - 05:13 PDT
Update
Our data processing services have made significant progress and continue to catch up on the backlogged data. We expect our services to be caught up completely by 7:00 am PDT. Our data ingestion services are fully functional and no data has been lost.
Posted Apr 01, 2018 - 23:49 PDT
Monitoring
The User Activity functionality has been restored, and we expect data processing to continue to be delayed into the late evening.
Posted Apr 01, 2018 - 17:10 PDT
Update
Our critical database has completely recovered and we have resumed our data processing services. We are scaling up our processing services to catch up with the backlogged events. We expect delays in processing to continue for the next few hours. Our ingestion servers are functional and no data has been lost.
Posted Apr 01, 2018 - 16:02 PDT
Update
Our team is continuing to work on resolving issues. We expect delays in processing event data to continue until Sunday evening PST. User activity functionality is also unavailable. Our ingestion servers are functional and no data has been lost.
Posted Apr 01, 2018 - 12:00 PDT
Update
We are continuing to work on resolving issues. We expect data processing delays to extend for another 12 hours. Our ingestion servers are completely functional and no data has been lost.
Posted Apr 01, 2018 - 09:19 PDT
Update
We're continuing to work on resolving the issue. We expect data processing delays for up to 12 hours.
Posted Mar 31, 2018 - 21:05 PDT
Identified
We identified an issue with a critical database that forced us to pause data processing as of 7:25pm PST. As a result of this issue, the User Activity feature and corresponding APIs are degraded. We're working to resolve the issue.