BetterStack Outage History

9 incidents recorded over the last 365 days, 9 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 BetterStack status99.79% uptime history

Every Recorded BetterStack Incident

BetterStack incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 20, 2026Degraded Telemetry performance91h 28mResolved
Aug 9, 2026Migrating Telemetry sources to new infrastructure11h 13mResolved
Jul 24, 2026Degraded configuration changes / new sources733h 6mResolved
Jun 15, 2026AWS Direct Connect connection outage1679h 42mResolved
Jun 14, 2026Elevated Telemetry querying errors1703h 18mResolved
May 21, 2026Uptime degradation1713h 13mResolved
May 8, 2026Some of the status pages are under DDoS2020h 23mResolved
Feb 13, 2026Degraded dashboard in the UK1847h 30mResolved
Jan 14, 2026Delayed data processing on US East cluster1832h 53mResolved

How to Read This BetterStack 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 BetterStack 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 BetterStack outage in this window ran 84d 4h, against a mean recovery of 53d 20h. If you depend on BetterStack 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.