Mode Analytics Outage History

Mode Analytics had 12 outages in the last 2 years totaling 89h 21m of downtime — averaging 0.5 incidents per month.

There were 12 Mode Analytics outages since June 13, 2025 totaling 89h 21m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.modeanalytics.com

Minor March 9, 2026

Discovery Database Sync Delay

Detected by Pingoru: Mar 09, 2026, 03:38 PM UTC
Resolved: Mar 11, 2026, 01:47 PM UTC
Duration: 1d 22h

Affected: Discovery Database

Timeline · 4 updates

investigating Mar 09, 2026, 03:38 PM UTC

As of March 7th there have been failures when syncing new data to the Discovery Database. As a result the latest data seen in the Discovery Database will be for March 6th as subsequent syncs have failed. Our engineers are investigating to identify the root cause of the issue and we will share updates accordingly.
identified Mar 10, 2026, 12:33 PM UTC

Our engineers have identified the issue and are currently applying a fix for the syncing pipeline of the Discovery Database.
monitoring Mar 10, 2026, 01:05 PM UTC

The freshness of data has been validated and we are monitoring the Discovery Database pipeline through the next daily sync.
resolved Mar 11, 2026, 01:47 PM UTC

This incident has been resolved.

Read the full incident report →

Critical January 9, 2026

Intercom outage affecting the in-app messenger

Detected by Pingoru: Jan 09, 2026, 09:01 PM UTC
Resolved: Jan 09, 2026, 09:18 PM UTC
Duration: 17m

Affected: Third Party Dependency

Timeline · 2 updates

identified Jan 09, 2026, 09:01 PM UTC

Intercom messenger is experiencing an outage and users are currently unable to load the in-app chat widget in Mode. If you need to contact Support during this time, please email us at: [email protected], or by reaching out to your Account Team to raise any priority issues, and they will alert us directly. We will resume operations for existing and new tickets in Intercom as soon as possible. To stay up-to-date: https://www.intercomstatus.com/
resolved Jan 09, 2026, 09:18 PM UTC

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

Read the full incident report →

Major January 5, 2026

Intercom Outage

Detected by Pingoru: Jan 05, 2026, 02:22 PM UTC
Resolved: Jan 05, 2026, 03:09 PM UTC
Duration: 47m

Affected: Third Party Dependency

Timeline · 2 updates

monitoring Jan 05, 2026, 02:22 PM UTC

Intercom messenger is experiencing an outage and the Support Team is intermittently unable to access Intercom at this time. Please reach out to your Account Team to raise any priority issues, and they will alert us directly. We will resume operations for existing and new tickets in Intercom as soon as possible. To stay up-to-date: https://www.intercomstatus.com/
resolved Jan 05, 2026, 03:09 PM UTC

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

Read the full incident report →

Notice December 11, 2025

Resolved - Missing Notebook Visuals in Reports

Detected by Pingoru: Dec 11, 2025, 05:00 AM UTC
Resolved: Dec 11, 2025, 05:00 AM UTC
Duration: —

Timeline · 1 update

resolved Dec 11, 2025, 01:22 PM UTC

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.

Read the full incident report →

Major November 18, 2025

GitHub incident impacting Git Syncs

Detected by Pingoru: Nov 18, 2025, 09:47 PM UTC
Resolved: Nov 18, 2025, 10:15 PM UTC
Duration: 27m

Affected: Third Party Dependency

Timeline · 2 updates

monitoring Nov 18, 2025, 09:47 PM UTC

GitHub is reporting failures and degraded availability for Git operations, which may interrupt Mode's Github integration. Some syncs may fail, stall, or not reflect recent changes. We're monitoring GH's incident and will provide updates as it progresses. You can also follow the GitHub updates at https://www.githubstatus.com/
resolved Nov 18, 2025, 10:15 PM UTC

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

Read the full incident report →

Notice November 18, 2025

Scheduled Report Failures

Detected by Pingoru: Nov 18, 2025, 01:00 PM UTC
Resolved: Nov 18, 2025, 01:00 PM UTC
Duration: —

Timeline · 1 update

resolved Nov 18, 2025, 01:18 PM UTC

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.

Read the full incident report →

Minor November 6, 2025

Reports using Notebook generated Datasets failing to load

Detected by Pingoru: Nov 06, 2025, 01:54 PM UTC
Resolved: Nov 06, 2025, 04:20 PM UTC
Duration: 2h 26m

Affected: Site and APINotebooks: Python & RReports and DashboardsVisual Explorer

Timeline · 2 updates

identified Nov 06, 2025, 01:54 PM UTC

We're investigating an issue causing reports that use Notebook generated datasets to fail. Affected reports may show missing datasets in the Data pane, charts that infinitely load, or errors stating that the underlying dataset was deleted. Our team has identified the cause, and a fix is currently being implemented to restore functionality.
resolved Nov 06, 2025, 04:20 PM UTC

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.

Read the full incident report →

Minor October 20, 2025

AWS outage impacting Mode - elevated errors and delays

Detected by Pingoru: Oct 20, 2025, 12:32 PM UTC
Resolved: Oct 21, 2025, 12:08 PM UTC
Duration: 23h 35m

Affected: Site and APIData Source Connectivity - Direct ConnectData Source Connectivity - BridgeNotebooks: Python & RReport Run SchedulerReports and DashboardsSQL EditorThird Party Dependency

Timeline · 3 updates

monitoring Oct 20, 2025, 12:32 PM UTC

We're aware of a widespread AWS outage in the US-EAST-1 region that may have caused errors and delays across Mode. The issue has since been resolved by AWS, and Mode services are operating normally. We will continue to monitor the situation. You can also follow the AWS updates at https://health.aws.amazon.com/health/status that began on Oct 20 12:11 AM PDT
monitoring Oct 20, 2025, 02:53 PM UTC

AWS had another incident ~30 mins ago. We are monitoring the situation closely. Users may experience degraded performance and/or errors.
resolved Oct 21, 2025, 12:08 PM UTC

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.

Read the full incident report →

Major July 6, 2025

Third party service provider interruption

Detected by Pingoru: Jul 06, 2025, 11:36 PM UTC
Resolved: Jul 07, 2025, 12:07 PM UTC
Duration: 12h 31m

Affected: Notebooks: Python & RReports and DashboardsThird Party Dependency

Timeline · 2 updates

investigating Jul 06, 2025, 11:36 PM UTC

We have observed issues with a third party service provider beginning around 16:00 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 will still complete in the background). We are investigating the issue with our third party provider and will share updates as they become available.
resolved Jul 07, 2025, 12:07 PM UTC

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

Read the full incident report →

Major July 1, 2025

DDB Outage

Detected by Pingoru: Jul 01, 2025, 04:59 PM UTC
Resolved: Jul 01, 2025, 07:31 PM UTC
Duration: 2h 31m

Affected: Discovery Database

Timeline · 4 updates

investigating Jul 01, 2025, 04:59 PM UTC

This morning's daily Discovery Database update was not successful. We are investigating and will provide additional information as soon as possible. Previous data should still be available.
identified Jul 01, 2025, 05:38 PM UTC

We have applied a fix. We will be able to manually trigger the DDB sync in about an hour.
monitoring Jul 01, 2025, 06:37 PM UTC

Our team has started the Discovery Database sync. It should complete within an hour.
resolved Jul 01, 2025, 07:31 PM UTC

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

Read the full incident report →

Notice July 1, 2025

Email Outage

Detected by Pingoru: Jul 01, 2025, 01:06 AM UTC
Resolved: Jul 01, 2025, 01:06 AM UTC
Duration: —

Affected: Reports and Dashboards

Timeline · 1 update

resolved Jul 01, 2025, 01:06 AM UTC

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

Read the full incident report →

Major June 13, 2025

AWS Partial Outage impacting API

Detected by Pingoru: Jun 13, 2025, 05:34 PM UTC
Resolved: Jun 13, 2025, 06:10 PM UTC
Duration: 35m

Affected: Site and API

Timeline · 2 updates

monitoring Jun 13, 2025, 05:34 PM UTC

An AWS partial outage is impacting the Audit Logs API endpoint. We are aware of and monitoring the situation. You can follow the AWS updates at https://health.aws.amazon.com/health/status under the "Increased Queue Processing Time" incident that began on June 13th, at 10:12 AM PDT.
resolved Jun 13, 2025, 06:10 PM UTC

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.

Read the full incident report →