Störungsverlauf von Chartbeat

1. 3. September 2026 um 15:43 UTCinvestigating

   Unsere Ingenieure untersuchen derzeit Benutzerberichte, in denen unser Heads Up Display nicht geladen wird, und arbeiten derzeit daran, dieses Problem zu beheben

2. 3. September 2026 um 17:35 UTCmonitoring

   Unser Engineering-Team hat ein temporäres Verbindungsproblem identifiziert, das intermittierende HUD-Ladeprobleme verursacht hat, das System ist ab 11:00 Uhr EST stabil geblieben und wir überwachen dieses Problem weiterhin. Wenn Sie immer noch Probleme beim Laden des HUD haben, wenden Sie sich bitte an [email protected].

3. 3. September 2026 um 20:56 UTCresolved

   Wir haben ein Problem mit einer unserer Datenbanken festgestellt, bei dem Heads Up Display-Anfragen gesichert wurden, was zu einer vorübergehenden Störung der HUD-Funktion führte. Ab heute 11:00 Uhr EST (3. September) Das Problem wurde behoben und wir haben die Leistung des Systems den ganzen Tag über überwacht. Alle Systeme sind derzeit stabil. Wenn Sie weiterhin Probleme mit dem HUD-Laden auf Ihrer Website haben, können Sie sich bitte an [email protected] wenden, um zusätzliche Unterstützung zu erhalten.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 8. Mai 2026 um 01: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. 8. Mai 2026 um 05:34 UTCresolved

   This incident has been resolved.

1. 20. Oktober 2025 um 13: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. 20. Oktober 2025 um 15: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. 20. Oktober 2025 um 18:07 UTCmonitoring

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

4. 20. Oktober 2025 um 22: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. 21. Oktober 2025 um 00:35 UTCresolved

   This incident has been resolved.

1. 16. September 2025 um 00:56 UTCinvestigating

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

2. 16. September 2025 um 03:17 UTCmonitoring

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

3. 16. September 2025 um 11:41 UTCresolved

   This incident has been resolved.

1. 22. August 2025 um 20: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. 22. August 2025 um 22: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. 25. August 2025 um 17: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. 4. September 2025 um 16: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. 24. Juli 2025 um 22: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. 25. Juli 2025 um 12:50 UTCresolved

   This incident has been resolved.

1. 23. Juli 2025 um 19:50 UTCinvestigating

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

2. 24. Juli 2025 um 03: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. 24. Juli 2025 um 14: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. 25. Juli 2025 um 14:41 UTCresolved

   This incident has been resolved.

1. 21. Juli 2025 um 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. 21. Juli 2025 um 22:14 UTCmonitoring

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

3. 22. Juli 2025 um 15:44 UTCresolved

   This incident has been resolved.

1. 13. Februar 2025 um 17:29 UTCinvestigating

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

2. 13. Februar 2025 um 23:13 UTCresolved

   The incident has been resolved.

1. 8. Januar 2025 um 13:47 UTCinvestigating

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

2. 8. Januar 2025 um 15:07 UTCmonitoring

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

3. 8. Januar 2025 um 16: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. 8. Januar 2025 um 16:51 UTCresolved

   This incident has been resolved.

1. 20. November 2024 um 01: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. 20. November 2024 um 02:28 UTCresolved

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

1. 3. Oktober 2024 um 17: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. 3. Oktober 2024 um 19:20 UTCmonitoring

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

3. 3. Oktober 2024 um 20:00 UTCresolved

   This incident has been resolved.

1. 25. Juli 2024 um 22:59 UTCinvestigating

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

2. 25. Juli 2024 um 23:53 UTCmonitoring

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

3. 26. Juli 2024 um 00:16 UTCresolved

   This incident has been resolved.

1. 6. Juni 2024 um 13: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. 6. Juni 2024 um 16:58 UTCmonitoring

   Our engineering team is currently monitoring the results.

3. 6. Juni 2024 um 18:00 UTCresolved

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

1. 30. Mai 2024 um 13: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. 30. Mai 2024 um 14:30 UTCmonitoring

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

3. 30. Mai 2024 um 15:18 UTCresolved

   This incident has been resolved.

1. 29. April 2024 um 18:24 UTCinvestigating

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

2. 29. April 2024 um 19:34 UTCinvestigating

   The Historical Dashboard is fully operational now.

3. 29. April 2024 um 21:21 UTCresolved

   This incident has been resolved.

1. 2. Februar 2024 um 20:26 UTCinvestigating

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

2. 2. Februar 2024 um 20:55 UTCmonitoring

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

3. 3. Februar 2024 um 00:29 UTCresolved

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

1. 16. November 2023 um 02: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. 16. November 2023 um 02: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. 16. November 2023 um 03: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. 16. November 2023 um 11:12 UTCmonitoring

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

5. 16. November 2023 um 14: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. 16. November 2023 um 17:22 UTCmonitoring

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

7. 16. November 2023 um 21:32 UTCresolved

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

1. 8. Oktober 2023 um 13:11 UTCinvestigating

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

2. 8. Oktober 2023 um 13:28 UTCmonitoring

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

3. 8. Oktober 2023 um 14:07 UTCresolved

   This incident has been resolved.

1. 26. September 2023 um 01: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.