Mode Analytics Outage History

Starting around 17:19 UTC on September 4th, users accessing the "My API Keys" page in workspace settings may have experienced an error message. Affected users were unable to access the management frame for API keys, which prevented them from creating new keys or managing existing ones. The root cause was identified and addressed shortly after, and the issue was corrected later that afternoon. As always, please reach out to Support if you have any questions or concerns.

The data was backfilled just past midnight on the 27th and we expect future syncs to succeed. If you have any questions please feel free to reach out to Mode Support.

This issue is resolved, and we have reached out to the impacted customers.

We have backfilled the missing data in the Discovery Database. Future syncs should proceed as expected. Thanks again for your patience.

This incident has been resolved.

On July 31st, we experienced higher than expected memory usage between 10:15AM and 10:40AM PST. We expect this to have three potential impacts: 1. Some users may experience an exception during Report Cloning. Please retry that action. 2. Some Scheduled Report Runs may not have started their runs as expected during this timeframe. We will automatically retry those runs every five minutes. Some Scheduled Runs may have a brief delay. 3. Some Report Runs' Notebook Runs may have failed. Please manually retry those Report Runs. If you have any questions, please reach out to Support via chat or email ([email protected]). Thank you,

This incident has been resolved.

From approximately July 16, 2024 19:00 UTC there was the possibility that a sync to Github from Mode would not be pushed to the respective repository. The behavior has been corrected as of July 20th and subsequent syncs should create commits in the repositories. For any missing commits we recommend to re-sync the changes as necessary. This would not have impacted syncs from Github to Mode. As always, please reach out to Support for any questions or concerns.

The daily scheduled report runs are confirmed working as expected.

This incident has been resolved.

A recent upstream change in a server component generated errors during ingestion. Our Engineers have accounted for this behavior.