MyCase incident

Access to MyCase

Major Resolved View vendor source →

MyCase experienced a major incident on August 15, 2022 affecting MyCase, lasting 22h 50m. The incident has been resolved; the full update timeline is below.

Started
Aug 15, 2022, 03:52 PM UTC
Resolved
Aug 16, 2022, 02:42 PM UTC
Duration
22h 50m
Detected by Pingoru
Aug 15, 2022, 03:52 PM UTC

Affected components

MyCase

Update timeline

  1. investigating Aug 15, 2022, 03:52 PM UTC

    MyCase is currently experiencing intermittent connection issues and access to the system may be affected. Our Development Team is aware of the issue and working as quickly as possible to get this resolved. Please check back on this page, or subscribe to updates, and we will provide an update shortly.

  2. investigating Aug 15, 2022, 04:26 PM UTC

    We are continuing to investigate this issue.

  3. identified Aug 15, 2022, 05:01 PM UTC

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

  4. identified Aug 15, 2022, 05:35 PM UTC

    We are continuing to work on a fix for this issue.

  5. identified Aug 15, 2022, 06:12 PM UTC

    We are continuing to work on a fix for this issue.

  6. identified Aug 15, 2022, 07:01 PM UTC

    We are continuing to work on a fix for this issue.

  7. monitoring Aug 15, 2022, 08:11 PM UTC

    Thank you for your patience, we have identified the issue and are monitoring the situation closely.

  8. monitoring Aug 15, 2022, 09:38 PM UTC

    We are continuing to monitor for any further issues.

  9. monitoring Aug 15, 2022, 10:31 PM UTC

    Thank you for your patience as we continue working through this issue.

  10. monitoring Aug 15, 2022, 11:28 PM UTC

    Our Engineering team is continuing to work on a fix for this issue.

  11. monitoring Aug 16, 2022, 12:33 AM UTC

    Thank you for your patience as we continue working on this issue.

  12. monitoring Aug 16, 2022, 02:52 AM UTC

    We are continuing to monitor for any further issues.

  13. monitoring Aug 16, 2022, 01:21 PM UTC

    We are continuing to monitor for any further issues.

  14. resolved Aug 16, 2022, 02:42 PM UTC

    This incident has been resolved.