LogRocket Outage History

7 incidents recorded over the last 365 days, 6 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 LogRocket status100.00% uptime history

Every Recorded LogRocket Incident

LogRocket incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 24, 2026Analytics Ingestion DelaysThis incident has been resolved.3h 39mResolved
Oct 17, 2026MCP server upgradeThe scheduled maintenance has been completed.1h 0mScheduled
Jul 22, 2026Ingestion failures during upgradeBetween 8:50pm and 9:10pm America/New_York on July 21st, there were availability blips during an upgrade of our nginx proxy layer. SDK clients will have retried during this event and we recovered from a backlog by…-32 minResolved
Jun 15, 2026Delayed analytics ingestion and alertsThis incident has been resolved.3h 15mResolved
Jun 2, 2026Dashboard instabilityThis incident has been resolved.46 minResolved
Nov 18, 2025Dashboard instabilityThis incident has been resolved.2h 33mResolved
Nov 5, 2025Ingestion InstabilityThis incident is fully resolved.3h 5mResolved

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 LogRocket 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 LogRocket 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 LogRocket 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 LogRocket outage in this window ran 3h 39m, against a mean recovery of 2h 23m. If you depend on LogRocket 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.