Histórico de interrupções do Mode Analytics

1. 27 Gouere 2026 da 19:34 UTCresolved

   Observamos problemas com um terceiro prestador de serviços entre 09:00 e 11:30 UTC. O impacto teria contribuído para que as células do Notebook não conseguissem renderizar seus resultados, auto-fixar tabelas no navegador de esquemas e notificações para ações como duplicação de relatórios (a duplicação de relatórios ainda estaria completa em segundo plano). Esta questão está agora resolvida. Por favor, contacte o apoio se tiver alguma dúvida.

Traduzido automaticamente da atualização oficial do incidente.

1. 27 Gouere 2026 da 08:57 UTCresolved

   Entre aproximadamente 3:55 AM e 4:15 PDT, os usuários podem ter experimentado períodos de serviço devido a um problema de rede AWS na região us-west-2 (Oregon). A falha da AWS interrompeu temporariamente a conectividade de internet externa da região, impactando nossa capacidade de comunicação com serviços externos. Com base na nossa investigação, a questão era externa à nossa infra-estrutura, e todos os serviços foram desde então totalmente restaurados após a resolução da AWS do incidente.

Traduzido automaticamente da atualização oficial do incidente.

1. 8 Mezheven 2026 da 16:30 UTCinvestigating

   We are currently investigating an issue where users may experience errors in authenticating to Mode through Microsoft SSO. Please reach out to Mode Support ([email protected]) if you or any of your users are experiencing this issue.

2. 8 Mezheven 2026 da 17:13 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 8 Mezheven 2026 da 19:13 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 8 Mezheven 2026 da 20:00 UTCresolved

   This incident has been resolved.

1. 9 Meurzh 2026 da 15:38 UTCinvestigating

   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.

2. 10 Meurzh 2026 da 12:33 UTCidentified

   Our engineers have identified the issue and are currently applying a fix for the syncing pipeline of the Discovery Database.

3. 10 Meurzh 2026 da 13:05 UTCmonitoring

   The freshness of data has been validated and we are monitoring the Discovery Database pipeline through the next daily sync.

4. 11 Meurzh 2026 da 13:47 UTCresolved

   This incident has been resolved.

1. 9 Genver 2026 da 21:01 UTCidentified

   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/

2. 9 Genver 2026 da 21:18 UTCresolved

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

1. 5 Genver 2026 da 14:22 UTCmonitoring

   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/

2. 5 Genver 2026 da 15:09 UTCresolved

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

1. 18 Kerzu 2025 da 17:02 UTCidentified

   We have identified an internal issue affecting the Discovery Database sync, resulting in a delay of up to 24 hours. Some customers may see missing or outdated data during this period. We are actively working to resolve it and will provide an update once resolved.

2. 19 Kerzu 2025 da 13:06 UTCresolved

   The Discovery Database sync delay has been resolved. The sync completed successfully and data is now up to date.

1. 11 Kerzu 2025 da 13:22 UTCresolved

   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.

1. 18 Du 2025 da 21:47 UTCmonitoring

   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/

2. 18 Du 2025 da 22:15 UTCresolved

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

1. 18 Du 2025 da 13:18 UTCresolved

   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.

1. 6 Du 2025 da 13:54 UTCidentified

   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.

2. 6 Du 2025 da 16:20 UTCresolved

   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.

1. 20 Here 2025 da 12:32 UTCmonitoring

   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

2. 20 Here 2025 da 14:53 UTCmonitoring

   AWS had another incident ~30 mins ago. We are monitoring the situation closely. Users may experience degraded performance and/or errors.

3. 21 Here 2025 da 12:08 UTCresolved

   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.

1. 20 Here 2025 da 12:21 UTCinvestigating

   Intercom messenger is experiencing degraded performance 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.

2. 20 Here 2025 da 12:34 UTCinvestigating

   We are continuing to investigate this issue.

3. 21 Here 2025 da 12:03 UTCresolved

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

1. 6 Gouere 2025 da 23:36 UTCinvestigating

   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.

2. 7 Gouere 2025 da 12:07 UTCresolved

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

1. 1 Gouere 2025 da 16:59 UTCinvestigating

   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.

2. 1 Gouere 2025 da 17:38 UTCidentified

   We have applied a fix. We will be able to manually trigger the DDB sync in about an hour.

3. 1 Gouere 2025 da 18:37 UTCmonitoring

   Our team has started the Discovery Database sync. It should complete within an hour.

4. 1 Gouere 2025 da 19:31 UTCresolved

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

1. 1 Gouere 2025 da 01:06 UTCresolved

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

1. 13 Mezheven 2025 da 17:34 UTCmonitoring

   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.

2. 13 Mezheven 2025 da 18:10 UTCresolved

   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.

1. 24 Ebrel 2025 da 20:15 UTCinvestigating

   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.

2. 24 Ebrel 2025 da 20:20 UTCresolved

   Intercom access is recovering and the Support team will resume operations as normal.

1. 16 Ebrel 2025 da 09:18 UTCidentified

   The dataset failed to load. When attempting to use the reusable dataset, it results in a blank screen. The issue has been identified, and our team is actively working on the fix.

2. 16 Ebrel 2025 da 10:15 UTCmonitoring

   A fix has been successfully deployed, and we are actively monitoring.

3. 16 Ebrel 2025 da 13:20 UTCresolved

   This incident has been resolved.

1. 31 Meurzh 2025 da 11:58 UTCidentified

   We are aware that some scheduled emails over the weekend may be delayed. We have identified the cause and are working to resolve the issue.

2. 31 Meurzh 2025 da 12:25 UTCmonitoring

   A fix for the issue has been implemented by our engineers. Scheduled emails that were not previously received should be arriving in the respective inboxes.

3. 31 Meurzh 2025 da 12:57 UTCresolved

   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.