Chartbeat Outage History

Chartbeat is up right now

Chartbeat had 3 outages in the last 2 years totaling 323h 2m of downtime — averaging 0.1 incidents per month.

There were 3 Chartbeat outages since August 22, 2025 totaling 323h 2m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://chartbeat.statuspage.io

Major May 8, 2026

Third-party service outage that may affect Chartbeat products

Detected by Pingoru
May 08, 2026, 01:35 AM UTC
Resolved
May 08, 2026, 05:34 AM UTC
Duration
3h 58m
Affected: Chartbeat Publishing - Realtime DashboardsChartbeat Publishing - Historical DashboardsChartbeat Publishing - Heads Up DisplayChartbeat Publishing - Headline and Image TestingChartbeat Publishing - ReportsChartbeat Publishing - Advanced Queries
Timeline · 2 updates
  1. identified May 08, 2026, 01:35 AM UTC

    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. resolved May 08, 2026, 05:34 AM UTC

    This incident has been resolved.

Read the full incident report →

Major September 16, 2025

Issue with Advanced Queries

Detected by Pingoru
Sep 16, 2025, 12:56 AM UTC
Resolved
Sep 16, 2025, 11:41 AM UTC
Duration
10h 45m
Affected: Chartbeat Publishing - Advanced Queries
Timeline · 3 updates
  1. investigating Sep 16, 2025, 12:56 AM UTC

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

  2. monitoring Sep 16, 2025, 03:17 AM UTC

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

  3. resolved Sep 16, 2025, 11:41 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 22, 2025

Historical Data Bug

Detected by Pingoru
Aug 22, 2025, 08:11 PM UTC
Resolved
Sep 04, 2025, 04:30 PM UTC
Duration
12d 20h
Affected: Chartbeat Publishing - Historical DashboardsChartbeat Publishing - ConversionsChartbeat Publishing - ReportsChartbeat Publishing - Advanced Queries
Timeline · 4 updates
  1. identified Aug 22, 2025, 08:11 PM UTC

    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. identified Aug 22, 2025, 10:30 PM UTC

    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. identified Aug 25, 2025, 05:07 PM UTC

    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. resolved Sep 04, 2025, 04:30 PM UTC

    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.

Read the full incident report →