Mode Analytics Outage History

We observed issues with a third party service provider between 09:00 and 11:30 UTC. The impact would have contributed to Notebook cells failing to render their results, auto-pinning of tables in the schema browser, and notifications for actions such as report duplication (report duplication would still complete in the background). This issue is now resolved. Please reach out to support if you have any questions.

Between approximately 3:55 AM and 4:15 AM PDT, users may have experienced service timeouts due to an AWS networking issue in the us-west-2 (Oregon) region. The AWS outage temporarily disrupted outbound internet connectivity from the region, impacting our ability to communicate with external services. Based on our investigation, the issue was external to our infrastructure, and all services have since been fully restored following AWS's resolution of the incident.

This incident has been resolved.

This incident has been resolved.

Intercom messenger has fully recovered, and the Support team has resumed normal operations.

Intercom messenger has fully recovered, and the Support team has resumed normal operations.

At approximately 12:00 AM Eastern on December 11, we received the first report that Python visuals were not appearing in reports. While the visuals displayed correctly in the notebook, the corresponding report elements appeared empty. Our engineering team identified the cause of the issue and resolved it. All notebook visuals should now render as expected in reports. If you continue to experience any issues, please reach out to Support.

GitHub has reported this incident as resolved and all systems are operational. You can review GitHub updates at https://www.githubstatus.com/

We became aware of an issue affecting scheduled reports executions beginning around 11:00 PM EST on November 17th. The issue affected hourly, 15-minute, and weekly scheduled jobs. Monthly and 30-minute schedules were not impacted. Engineering has resolved the issue, and normal scheduling has resumed. We are continuing to monitor to ensure full stability. Further updates will be provided. Edit: Scheduled executions began failing at 2:00 PM EST on November 17 and were fully resolved by 6:30 AM EST on November 18. As expected after recovery, some delayed or duplicate scheduled runs were triggered as jobs caught up. Normal scheduling has now resumed as of Nov 20.

A fix has been deployed, and functionality for reports using Notebook generated datasets has been restored. If you continue to experience any issues, please refresh your report and try again. If you still encounter any issues, please reach out to our support team for assistance.

The earlier AWS outage impacting Mode services has been resolved. All systems are operational, though some background jobs and scheduled runs may take additional time to clear as backlogs process. Please reach out to Support if you have any questions.