Chartbeat 장애 기록

1. 2026년 9월 3일 오후 3:43 UTCinvestigating

   우리의 엔지니어는 현재 우리의 머리 위 전시의 사용자 보고를 적재하지 않으며 현재 이 문제점을 해결하기 위하여 일하고 있습니다

2. 2026년 9월 3일 오후 5:35 UTCmonitoring

   우리의 기술설계 팀은 간헐적인 HUD 선적 문제점을 일으키는 임시 연결 문제점을 확인했습니다, 체계는 11:00 AM EST로 안정되어 있고 우리는 이 문제점을 감시하기 위하여 계속됩니다. HUD를 로딩하는 문제가 발생하면 [email protected]으로 연락 주시기 바랍니다.

3. 2026년 9월 3일 오후 8:56 UTCresolved

   우리는 Heads Up Display 요청을 백업하는 데 걸리는 우리의 데이터베이스 중 하나와 문제가 발견, HUD 기능의 일시적인 붕괴. 오늘 오전 11시 (9월 3일) 문제는 해결되었습니다. 우리는 하루 동안 시스템 성능을 모니터링하고 있습니다. 모든 시스템은 현재 안정적입니다. 귀하의 사이트에 HUD 로딩에 문제가 계속되면 [email protected]으로 연락 주시기 바랍니다.

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

1. 2026년 5월 8일 오전 1:35 UTCidentified

   Beginning at approximately 7:49 PM ET, we noticed disruptions to our third-party AWS service. Shortly after, AWS reported an issue on their end that was causing significant service degradation. This is having some observed impacts on Chartbeat's data processing and several product features, including the Heads Up Display. AWS continues to show an ongoing outage on their end, which we are monitoring closely. We are working with AWS and actively assessing the full scope of impact. We will follow up with specific detail on affected systems as soon as our investigation is complete.

2. 2026년 5월 8일 오전 5:34 UTCresolved

   This incident has been resolved.

1. 2025년 10월 20일 오후 1:43 UTCinvestigating

   Our third-party cloud platform is experiencing an outage that may affect the Historical Dashboard, Advanced Queries, Reports, Conversion, Data Lab, Cohorts, and Social Hub.

2. 2025년 10월 20일 오후 3:11 UTCmonitoring

   While we are noticing early signs of improvement, we are continuing to monitor the third-party service cloud platform's recovery progress, and we'll provide another update within 60 minutes.

3. 2025년 10월 20일 오후 6:07 UTCmonitoring

   While we are noticing signs of improvement, we are continuing to monitor the third-party service cloud platform's recovery progress.

4. 2025년 10월 20일 오후 10:24 UTCmonitoring

   All previously affected Chartbeat products are operational. We are continuing to closely monitor our systems and notifications from our third-party cloud providers.

5. 2025년 10월 21일 오전 12:35 UTCresolved

   This incident has been resolved.

1. 2025년 9월 16일 오전 12:56 UTCinvestigating

   We are currently investigating an issue that is preventing users from running Advanced Queries reports.

2. 2025년 9월 16일 오전 3:17 UTCmonitoring

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

3. 2025년 9월 16일 오전 11:41 UTCresolved

   This incident has been resolved.

1. 2025년 8월 22일 오후 8:11 UTCidentified

   We have identified a bug in our historical data starting on July 23, 2025, that has caused inflated pageviews in the following Chartbeat surfaces: - Historical Dashboard - Reports - Advanced Queries - Data Lab - Cohorts - Conversion Current Status: We have implemented a solution that will fix this issue going forward, and your traffic numbers will be accurate starting today, Friday, Aug 22, 2025 at 20:05 UTC. Next Steps: We will be working to backfill corrected data over the next few days. We expect full resolution of historical data and do not anticipate any data loss.

2. 2025년 8월 22일 오후 10:30 UTCidentified

   Data deduplication process has been initiated for the dates July 23 - August 22. Traffic data over this date range will be subject to change in the affected products until this correction process is completed.

3. 2025년 8월 25일 오후 5:07 UTCidentified

   Corrected data has been backfilled in Historical, Advanced Queries, Conversion, Data Lab, and Cohorts. We are working on the fix to regenerate reports with corrected data in the Reports Dashboard interface (chartbeat.com/reports/dashboard) for dates July 23 - August 22. Corrected reports will not be reissued via email for subscribed users, but can be accessed from the Reports Dashboard once this process is complete.

4. 2025년 9월 4일 오후 4:30 UTCresolved

   Corrected data has been backfilled in the Reports Dashboard (chartbeat.com/reports/dashboard/) for dates August 18 - 23. Reports for July 23 through August 17 will not be viewable from the dashboard. This issue is now fully resolved.

1. 2025년 7월 24일 오후 10:05 UTCmonitoring

   We’ve identified an external issue with Apple News tracking today that temporarily caused lapses in Apple News traffic on dashboards. We've been in touch with the Apple team and are monitoring the situation currently to ensure that it is resolved, but users can expect to see dips in their Apple News dashboards due to the issue. We do not expect impacts on historical data from this issue.

2. 2025년 7월 25일 오후 12:50 UTCresolved

   This incident has been resolved.

1. 2025년 7월 23일 오후 7:50 UTCinvestigating

   We are currently investigating an issue that is causing problems generating Reports and delivery of Reports emails today.

2. 2025년 7월 24일 오전 3:37 UTCidentified

   Our team has been able to identify an issue with a third-party system which powers the graphs in the Daily Reports. We are in process of investigating alternative solutions to make Reports deliverable as soon as we can, but we expect that Reports may still not be delivered or compiled tomorrow morning (Thursday, July 24th) because of this issue.

3. 2025년 7월 24일 오후 2:17 UTCidentified

   We are still working on fixing the identified issue with the third-party system which powers the graphs in our Daily Reports. To mitigate the impact, we have temporarily removed the graphs from our Reports so that they can compile, and expect that should have been allowing most Reports emails to catch up and send, including those that were missed yesterday.

4. 2025년 7월 25일 오후 2:41 UTCresolved

   This incident has been resolved.

1. 2025년 7월 21일 오후 12:58 UTCinvestigating

   We are experiencing longer than usual load times in Chartbeat's Historical Dashboard and API due to a performance issue with Snowflake. Our team is investigating.

2. 2025년 7월 21일 오후 10:14 UTCmonitoring

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

3. 2025년 7월 22일 오후 3:44 UTCresolved

   This incident has been resolved.

1. 2025년 2월 13일 오후 5:29 UTCinvestigating

   We are currently investigating an issue that is causing a delay in some Reports emails.

2. 2025년 2월 13일 오후 11:13 UTCresolved

   The incident has been resolved.

1. 2025년 1월 8일 오후 1:47 UTCinvestigating

   We are currently investigating an issue that is preventing saved queries from running in Advanced Queries for some users.

2. 2025년 1월 8일 오후 3:07 UTCmonitoring

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

3. 2025년 1월 8일 오후 4:07 UTCmonitoring

   A recent upgrade to a component used by Advanced Queries affected saved queries that used a query name, this has now been fixed.

4. 2025년 1월 8일 오후 4:51 UTCresolved

   This incident has been resolved.

1. 2024년 11월 20일 오전 1:53 UTCidentified

   We've identified an outage in the system that powers real-time CPM stats in the Heads Up Display. A fix has been pushed, and CPM stats are fluctuating while the system recovers.

2. 2024년 11월 20일 오전 2:28 UTCresolved

   The earlier fix has fully resolved data issues in HUD— accurate real-time CPM data has been restored.

1. 2024년 10월 3일 오후 5:50 UTCinvestigating

   Our team is investigating an outage in Chartbeat's Recommendation Engine service resulting in error responses and/or placeholder results returned from requests to the API. We're working to restore full functionality as quickly as possible.

2. 2024년 10월 3일 오후 7:20 UTCmonitoring

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

3. 2024년 10월 3일 오후 8:00 UTCresolved

   This incident has been resolved.

1. 2024년 7월 25일 오후 10:59 UTCinvestigating

   We are currently investigating an issue with Headline and Image Testing. Our team is currently investigating.

2. 2024년 7월 25일 오후 11:53 UTCmonitoring

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

3. 2024년 7월 26일 오전 12:16 UTCresolved

   This incident has been resolved.

1. 2024년 6월 6일 오후 1:13 UTCidentified

   Our engineering team has determined the root cause of an issue with Advanced Queries recurring report delivery and one-time queries being stuck. They are pushing out a fix to resolve this.

2. 2024년 6월 6일 오후 4:58 UTCmonitoring

   Our engineering team is currently monitoring the results.

3. 2024년 6월 6일 오후 6:00 UTCresolved

   This incident has now been resolved. Advanced Queries and our Historical API are fully operational.

1. 2024년 5월 30일 오후 1:42 UTCinvestigating

   Our engineering team is aware of issues that are affecting the Historical Dashboard and preventing the dashboard from loading, we are actively investigating.

2. 2024년 5월 30일 오후 2:30 UTCmonitoring

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

3. 2024년 5월 30일 오후 3:18 UTCresolved

   This incident has been resolved.

1. 2024년 4월 29일 오후 6:24 UTCinvestigating

   Our engineering team is aware of issues affecting the loading of the Historical Dashboard and are actively investigating.

2. 2024년 4월 29일 오후 7:34 UTCinvestigating

   The Historical Dashboard is fully operational now.

3. 2024년 4월 29일 오후 9:21 UTCresolved

   This incident has been resolved.

1. 2024년 2월 2일 오후 8:26 UTCinvestigating

   Our team is investigating an issue with the system that powers the Heads-Up Display pin data.

2. 2024년 2월 2일 오후 8:55 UTCmonitoring

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

3. 2024년 2월 3일 오전 12:29 UTCresolved

   This incident has been resolved. All Chartbeat tools are fully operational.

1. 2023년 11월 16일 오전 2:01 UTCmonitoring

   Our engineering team is in the process of reverting a change that is resulting in a blank historical dashboard for many Sites. We will let you know once the change has been rolled back. Thank you for your patience and understanding in advance!

2. 2023년 11월 16일 오전 2:33 UTCmonitoring

   Our engineering team has since rolled back a change. They are currently investigating issues affecting the Historical and Real-Time Dashboards. We will keep you informed of upcoming updates as they work to resolve this.

3. 2023년 11월 16일 오전 3:38 UTCmonitoring

   Our engineering team has reverted a change that affected the Real-Time Dashboard for a short period of time, and it will self-resolve; there will be no impact on the historical data due to this issue. They have also fixed a secondary issue that is impacting the load time of the Historical Dashboard, which we are continuing to monitor.

4. 2023년 11월 16일 오전 11:12 UTCmonitoring

   Our engineering team is aware of issues affecting the load time of the Historical Dashboard and are actively investigating.

5. 2023년 11월 16일 오후 2:57 UTCmonitoring

   Our engineering team deployed a fix that seems to have resolved the Historical Dashboard loading issue. However, slow loading may still be expected. We will keep you posted once this is fully resolved.

6. 2023년 11월 16일 오후 5:22 UTCmonitoring

   Our Historical Dashboard is now operational, but we are continuing to monitor performance closely.

7. 2023년 11월 16일 오후 9:32 UTCresolved

   This incident has been fully resolved: All Chartbeat tools are fully operational.

1. 2023년 10월 8일 오후 1:11 UTCinvestigating

   Our team is investigating an issue with the system that powers Pageview and Unique visitor stats in the Real-time Dashboard.

2. 2023년 10월 8일 오후 1:28 UTCmonitoring

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

3. 2023년 10월 8일 오후 2:07 UTCresolved

   This incident has been resolved.

1. 2023년 9월 26일 오전 1:00 UTCresolved

   Our team identified and fixed an issue in our Conversion tracking that started on Sunday, September 24th. We're now investigating a possible data discrepancy affecting some customers as a result of this issue and triaging what the impacts may have been. We will provide further updates as we have them on what, if anything, to expect was affected by this. FINAL UPDATE: Between 9/24 23:00 EST and 9/25 12:00 EST, there was a data discrepancy for Conversions appearing lower than normal in the Real-Time Dashboard, Heads-Up Display, and Conversion Dashboard. This was caused by a minor lag in data ingestion which was resolved. No data was lost.