LibreChat Outage History

17 incidents recorded over the last 365 days, 16 of them resolved, 1 still open. 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 LibreChat status95.56% uptime history

Every Recorded LibreChat Incident

LibreChat incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 1, 2026Some services are down—Investigating
Oct 23, 2026LibreChat Demo is down7h 11mResolved
Oct 18, 2026ClickHouse DB, Web Analytics, and 4 other services are down14 minResolved
Oct 18, 2026Hosting provider maintenance16 minResolved
Oct 3, 2026LibreChat Demo is down349h 10mResolved
Oct 2, 2026LibreChat Demo is down391h 43mResolved
Sep 30, 2026Starguard is down869h 1mResolved
Sep 24, 2026LibreChat Demo is down583h 43mResolved
Sep 23, 2026LibreChat Demo is down607h 44mResolved
Sep 22, 2026LibreChat Demo is down631h 44mResolved
Sep 16, 2026LibreChat Demo is down775h 44mResolved
Sep 15, 2026LibreChat Demo is down799h 43mResolved
Sep 14, 2026LibreChat Demo is down823h 43mResolved
Sep 12, 2026LibreChat Demo is down871h 44mResolved
Sep 9, 2026LibreChat Demo is down943h 43mResolved
Sep 7, 2026Storage migration and retention cleanup3h 30mResolved
Aug 25, 2026Scheduled infrastructure maintenance30 minResolved

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 LibreChat 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 LibreChat 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 LibreChat 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 LibreChat outage in this window ran 39d 7h, against a mean recovery of 19d 22h. If you depend on LibreChat 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.