Chartbeat Outage History

10 incidents recorded over the last 365 days, 2 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Chartbeat status100.00% uptime history

Every Recorded Chartbeat Incident

Chartbeat incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Sep 3, 2026Heads Up Display experiencing loading issuesWe identified an issue with one of our databases that caused Heads Up Display requests to back up, resulting in a temporary disruption of the HUD feature. As of 11:00 AM EST today (September 3rd) The issue has been…5h 12mResolved
Aug 10, 2026Planned Maintenance WindowThe scheduled maintenance has been completed.2h 0mScheduled
Aug 10, 2026Planned Maintenance WindowThe scheduled maintenance has been completed.2h 0mScheduled
Jul 7, 2026Real Time Dashboard MaintenanceThe scheduled maintenance has been completed.3h 0mScheduled
Jun 15, 2026Planned Maintenance WindowThe scheduled maintenance has been completed.2h 0mScheduled
Jun 4, 2026RTD Conversions and Article Search MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
May 15, 2026Planned Maintenance WindowThe scheduled maintenance has been completed.48h 0mScheduled
May 8, 2026Third-party service outage that may affect Chartbeat productsThis incident has been resolved.3h 58mResolved
Dec 13, 2025Scheduled Maintenance: Chartbeat Web Application and Real-Time DashboardThe scheduled maintenance has been completed.3h 0mScheduled
Dec 5, 2025Scheduled Maintenance: Headline TestingThe scheduled maintenance has been completed.1h 0mScheduled

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Chartbeat incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Chartbeat Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Chartbeat acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Chartbeat outage in this window ran 2d, against a mean recovery of 7h 7m. If you depend on Chartbeat in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.