Heinemann incident

Heinemann Service Interruption

Critical Resolved View vendor source →

Heinemann experienced a critical incident on February 7, 2025 affecting Login and Login and 1 more component, lasting 8h 28m. The incident has been resolved; the full update timeline is below.

Started
Feb 07, 2025, 03:59 PM UTC
Resolved
Feb 08, 2025, 12:28 AM UTC
Duration
8h 28m
Detected by Pingoru
Feb 07, 2025, 03:59 PM UTC

Affected components

LoginLoginheinemann.comContent and ResourcesContent and ResourcesAssignmentsReporting

Update timeline

  1. investigating Feb 07, 2025, 03:59 PM UTC

    We are currently experiencing a service interruption for multiple Heinemann platforms and websites. Our teams are investigating now and additional updates will be provided here as soon as possible.

  2. identified Feb 07, 2025, 04:48 PM UTC

    Our teams have determined that this issue is due to an external issue with our Internet Service Provider. We are in communication with them now to address this issue. If you require additional assistance, the Heinemann Technical Support team may be reached at 800-225-5800.

  3. identified Feb 07, 2025, 06:17 PM UTC

    The local internet service carrier continues working to address this issue and our teams remain in communication with them. Heinemann teams are also working on an alternative solution to address this issue. Additional updates will be provided here as soon as possible. If you require additional assistance, the Heinemann Technical Support team may be reached at 800-225-5800.

  4. identified Feb 07, 2025, 08:33 PM UTC

    Our teams continue working to restore service, thank you for your patience. Additional updates will be provided here as soon as possible.

  5. identified Feb 07, 2025, 10:37 PM UTC

    Our teams have begun implementing a solution to restore service to impacted platforms and websites, and www.heinemann.com is once again available for visitors. The next update is targeting 60 minutes from now. Thank you for your patience as we work to restore service.

  6. resolved Feb 08, 2025, 12:28 AM UTC

    This incident has been resolved. Thank you for your patience and we apologize for this disruption.