Waterford Outage History

Waterford is up right now

Waterford had 3 outages in the last 2 years totaling 29h 0m of downtime — averaging 0.1 incidents per month.

There were 3 Waterford outages since March 12, 2025 totaling 29h 0m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.waterford.org

Minor October 20, 2025

Dashboards and Reporting Data Processing Is Delayed

Detected by Pingoru
Oct 20, 2025, 04:01 PM UTC
Resolved
Oct 21, 2025, 07:53 PM UTC
Duration
1d 3h
Affected: mentor.waterford.orgReporting and Dashboardsteacher.waterford.org
Timeline · 4 updates
  1. investigating Oct 20, 2025, 04:01 PM UTC

    We are currently experiencing a delay in the processing of student data due to recent events in Amazon Web Services (AWS). As a result, some dashboards and reports may temporarily display outdated information. Our team is monitoring the situation and will provide updates as data processing returns to normal.

  2. identified Oct 20, 2025, 06:36 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Oct 20, 2025, 07:18 PM UTC

    We are continuing to work on a fix for this issue data may remain out of date for an additional 12-24 hours.

  4. resolved Oct 21, 2025, 07:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 12, 2025

Users unable to authenticate with Waterford Reading Academy products

Detected by Pingoru
Mar 12, 2025, 01:19 PM UTC
Resolved
Mar 12, 2025, 02:29 PM UTC
Duration
1h 9m
Affected: my.waterford.orgupstart.waterford.orgmentor.waterford.orgteacher.waterford.org
Timeline · 4 updates
  1. investigating Mar 12, 2025, 01:19 PM UTC

    We are currently investigating this issue.

  2. identified Mar 12, 2025, 01:23 PM UTC

    The issue has been identified, and a fix is currently in progress

  3. monitoring Mar 12, 2025, 01:34 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Mar 12, 2025, 02:29 PM UTC

    This incident has been resolved.

Read the full incident report →