Mode Analytics 장애 기록

1. 2026년 7월 27일 PM 7:34 UTCresolved

   우리는 09:00와 11:30 UTC 사이 제 3 자 서비스 제공 업체와 문제를 관찰했습니다. 영향은 노트북 셀에 기여할 것입니다. 결과 렌더링 실패, 스키마 브라우저의 테이블 자동 핀, 및 보고서 복제 (report duplication은 여전히 배경에 완료 될 것입니다)와 같은 행동에 대한 알림. 이 문제는 이제 해결되었습니다. 자주 묻는 질문.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 27일 AM 8:57 UTCresolved

   약 3 : 55 AM 및 4 : 15 AM PDT 사이, 사용자는 우리에게 서서 AWS 네트워킹 문제로 인해 서비스 타임 아웃을 경험할 수 있습니다. 2 (Oregon) 지역. AWS Outage는 일시적으로 외부 서비스와 소통하는 능력에 영향을 미치는 영역에서 아웃바운드 인터넷 연결을 중단했습니다. 우리의 조사에 근거하여, 문제점은 우리의 인프라에 외부이고, 모든 서비스는 사건의 AWS의 해결책 뒤에 완전히 복원되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 8일 PM 4: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. 2026년 6월 8일 PM 5:13 UTCidentified

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

3. 2026년 6월 8일 PM 7:13 UTCmonitoring

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

4. 2026년 6월 8일 PM 8:00 UTCresolved

   This incident has been resolved.

1. 2026년 3월 9일 PM 3: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. 2026년 3월 10일 PM 12:33 UTCidentified

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

3. 2026년 3월 10일 PM 1:05 UTCmonitoring

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

4. 2026년 3월 11일 PM 1:47 UTCresolved

   This incident has been resolved.

1. 2026년 1월 9일 PM 9: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. 2026년 1월 9일 PM 9:18 UTCresolved

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

1. 2026년 1월 5일 PM 2: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. 2026년 1월 5일 PM 3:09 UTCresolved

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

1. 2025년 12월 18일 PM 5: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. 2025년 12월 19일 PM 1:06 UTCresolved

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

1. 2025년 12월 11일 PM 1: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. 2025년 11월 18일 PM 9: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. 2025년 11월 18일 PM 10: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. 2025년 11월 18일 PM 1: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. 2025년 11월 6일 PM 1: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. 2025년 11월 6일 PM 4: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. 2025년 10월 20일 PM 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. 2025년 10월 20일 PM 2:53 UTCmonitoring

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

3. 2025년 10월 21일 PM 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. 2025년 10월 20일 PM 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. 2025년 10월 20일 PM 12:34 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025년 10월 21일 PM 12:03 UTCresolved

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

1. 2025년 7월 6일 PM 11: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. 2025년 7월 7일 PM 12:07 UTCresolved

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

1. 2025년 7월 1일 PM 4: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. 2025년 7월 1일 PM 5:38 UTCidentified

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

3. 2025년 7월 1일 PM 6:37 UTCmonitoring

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

4. 2025년 7월 1일 PM 7:31 UTCresolved

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

1. 2025년 7월 1일 AM 1: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. 2025년 6월 13일 PM 5: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. 2025년 6월 13일 PM 6: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. 2025년 4월 24일 PM 8: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. 2025년 4월 24일 PM 8:20 UTCresolved

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

1. 2025년 4월 16일 AM 9: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. 2025년 4월 16일 AM 10:15 UTCmonitoring

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

3. 2025년 4월 16일 PM 1:20 UTCresolved

   This incident has been resolved.

1. 2025년 3월 31일 AM 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. 2025년 3월 31일 PM 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. 2025년 3월 31일 PM 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.