LibreTexts Systems Outage History
4 incidents recorded over the last 365 days, 3 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.
Every Recorded LibreTexts Systems Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 18, 2026 | Partial Outage on LibrariesThis incident has been resolved. | 3h 2m | Resolved |
| Jun 26, 2026 | Degraded Performance on LibrariesThe issue with the third-party service provider has been resolved. Libraries are operating normally. | 5h 6m | Resolved |
| Jun 21, 2026 | LibreOne Scheduled MaintenanceThe scheduled maintenance has been completed as planned. | 2h 0m | Scheduled |
| Feb 4, 2026 | This is an example incidentEmpathize with those affected and let them know everything is operating as normal. | -1424 min | Resolved |
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 LibreTexts Systems 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 LibreTexts Systems 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 LibreTexts Systems 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 LibreTexts Systems outage in this window ran 5h 6m, against a mean recovery of 3h 23m. If you depend on LibreTexts Systems 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.