Mode Analytics Outage History

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.

The issue is resolved. Please reach out to Support if you have any questions.

The issue is resolved. Please reach out to Support if you have any questions.

Emails were blocked by ~1.5 hours. Emails were blocked from 4:22-5:57PM Pacific. The issue is resolved and emails have resumed.

We are observing expected response codes and response times for the Audit Logs API endpoint. If you experience any other disruptions please feel free to reach out to Mode Support via in-app chat or by email ([email protected]). Thank you.

This incident has been resolved.

The incident has been resolved. Please reach out to Support, via chat or by emailing [email protected], if you are still encountering any issues in receiving scheduled emails. Thank you for your patience as we worked to resolve this.

We believe this issue to now be resolved.

Our Engineers have rolled back today's deploy, and will deploy corrected code tomorrow. Bridged Connections are fully operational again.

Due to the incident that occurred on Dec 23rd, some O365 users might see a screenshot stating "Approval Required" to login to Mode workspaces. Mode Engineers are aware of this and in the process of updating the app configuration to resolve this issue. O365 Admins may approve the Mode App to address this issue in the meantime.

Our Engineers have implemented a fix. We believe the issue is now resolved. Please reach out to [email protected] if you have any questions.

There was an issue in Mode where queries were encountering a "There was a problem running your report" error, preventing reports and queries from running. The issue was identified and resolved shortly after it first started, and everything should be functioning normally again. We apologize for any inconvenience caused and appreciate your patience while we worked to resolve the issue. Please reach out to support if you have any further questions or concerns. Thank you.

There was a period of time where users were unable to access query header settings and saw an error message. The behavior started occurring on 11/21/2024 at roughly 1:30 PM EST and was resolved on 11/22/2024 at approximately 6:07 PM EST. We apologize for any inconveniences caused during this period and invite you to reach our Support team ([email protected]) for any questions.

This incident has been resolved.

This incident has been resolved.

Our engineers have pushed a fix and users should now be able to successfully authenticate. Please refresh and retry authentication through the appropriate sign-in methods. Thank you for your patience as we worked to resolve this.

Our engineers have deployed a fix for this issue. A browser refresh may be necessary but the API tab is now accessible. Thank you for your patience as we worked to resolve this.