Cadmium incident

Eventscribe Server Unavailable

Critical Resolved View vendor source →

Cadmium experienced a critical incident on February 23, 2026 affecting Education Harvester and Website and 1 more component, lasting 17h 28m. The incident has been resolved; the full update timeline is below.

Started
Feb 23, 2026, 08:20 PM UTC
Resolved
Feb 24, 2026, 01:48 PM UTC
Duration
17h 28m
Detected by Pingoru
Feb 23, 2026, 08:20 PM UTC

Affected components

Education HarvesterWebsiteMobile AppExpo HarvestermyCadmiumSurvey MagnetScorecardLogistics

Update timeline

  1. investigating Feb 23, 2026, 08:20 PM UTC

    Our team is aware there is a service disruption and is working swiftly to identify the cause. Thank you for your patience.

  2. investigating Feb 23, 2026, 08:35 PM UTC

    Our team is still working to identify the cause of the service disruption. We will provide an update as soon as we have more information. Thank you for your patience.

  3. investigating Feb 23, 2026, 08:50 PM UTC

    Our team is still working to identify the cause of the service disruption. We will provide an update as soon as we have more information. Thank you for your patience.

  4. investigating Feb 23, 2026, 09:05 PM UTC

    Our team is still working to identify the cause of the service disruption. We will provide an update as soon as we have more information. Thank you for your patience.

  5. investigating Feb 23, 2026, 09:20 PM UTC

    Our team is still working to identify the cause of the service disruption. We will provide an update as soon as we have more information. Thank you for your patience.

  6. investigating Feb 23, 2026, 09:35 PM UTC

    Our team is still working to identify the cause of the service disruption. We will provide an update as soon as we have more information. Thank you for your patience.

  7. identified Feb 23, 2026, 09:44 PM UTC

    The root cause has been identified, and our team is working as quickly as possible to fix the issue. Thank you for your patience! We will provide an update as soon as we have more information.

  8. identified Feb 23, 2026, 10:00 PM UTC

    The root cause has been identified, and our team is working as quickly as possible to fix the issue. Thank you for your patience! We will provide an update as soon as we have more information.

  9. monitoring Feb 23, 2026, 10:15 PM UTC

    A fix has been put in place, and service is actively being restored. Our team is continuing to monitor the system. We will provide an update as soon as we have more information. Thank you for your patience.

  10. monitoring Feb 23, 2026, 10:25 PM UTC

    A fix has been put in place, and service is actively being restored. Our team is continuing to monitor the system. We will provide an update as soon as we have more information. Thank you for your patience.

  11. monitoring Feb 23, 2026, 10:30 PM UTC

    A fix has been put in place, and service has been restored. Our team is continuing to monitor the system. If you are still experiencing issues, please notify your project manager.

  12. resolved Feb 24, 2026, 01:48 PM UTC

    The issue has been resolved. We will share root cause analysis as soon as possible.

  13. postmortem Feb 24, 2026, 04:49 PM UTC

    On February 23, 2026, between 3:00 PM and 5:30 PM EST, a network configuration change caused a temporary service disruption. Some users may have experienced timeouts or errors during this window. The issue was identified and resolved, and full service was restored at 5:30 PM EST. No data was lost or compromised. We are reviewing our change management procedures to prevent similar disruptions in the future.