LibreTexts Outage History

LibreTexts is up right now

LibreTexts had 3 outages in the last 2 years totaling 8h 9m of downtime, averaging 0.1 incidents per month.

There were 3 LibreTexts outages since February 3, 2026 totaling 8h 9m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.libretexts.org

Major August 18, 2026

Partial Outage on Libraries

Detected by Pingoru
Aug 18, 2026, 07:12 PM UTC
Resolved
Aug 18, 2026, 10:15 PM UTC
Duration
3h 2m
Affected: ChemistryBiologyBusinessEngineeringEspanolGeologyHumanitiesK-12 EducationMathematicsMedicinePhysicsSocial SciencesStatisticsWorkforceUkrayinskaGlobal
Timeline · 3 updates
  1. identified Aug 18, 2026, 07:12 PM UTC

    An issue with a third-party service provider is currently affecting our libraries. Users may be unable to access content or log in. We apologize for any inconvenience and will provide updates as they are available.

  2. monitoring Aug 18, 2026, 07:52 PM UTC

    We are seeing improved availability and performance on the libraries. We will continue to monitor for signs of degradation.

  3. resolved Aug 18, 2026, 10:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 26, 2026

Degraded Performance on Libraries

Detected by Pingoru
Jun 26, 2026, 04:31 PM UTC
Resolved
Jun 26, 2026, 09:38 PM UTC
Duration
5h 6m
Affected: ChemistryBiologyBusinessEngineeringEspanolGeologyHumanitiesK-12 EducationMathematicsMedicinePhysicsSocial SciencesStatisticsWorkforceUkrayinskaGlobal
Timeline · 3 updates
  1. investigating Jun 26, 2026, 04:31 PM UTC

    Our libraries are currently experiencing degraded performance and unexpected behavior. We are working to restore normal function as soon as possible. We apologize for any inconvenience.

  2. identified Jun 26, 2026, 05:11 PM UTC

    An issue with a third-party service provider has been identified and a fix is being implemented.

  3. resolved Jun 26, 2026, 09:38 PM UTC

    The issue with the third-party service provider has been resolved. Libraries are operating normally.

Read the full incident report →

Notice February 3, 2026

This is an example incident

Detected by Pingoru
Feb 03, 2026, 01:34 AM UTC
Resolved
Feb 03, 2026, 01:34 AM UTC
Duration
–
Timeline · 4 updates
  1. investigating Feb 04, 2026, 01:18 AM UTC

    When your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.

  2. identified Feb 04, 2026, 01:18 AM UTC

    As you continue to work through the incident, update your customers frequently.

  3. monitoring Feb 04, 2026, 01:18 AM UTC

    Let your users know once a fix is in place, and keep communication clear and precise.

  4. resolved Feb 04, 2026, 01:18 AM UTC

    Empathize with those affected and let them know everything is operating as normal.

Read the full incident report →