MIDE01- Login Issues

Update timeline

1. investigating Mar 01, 2026, 04:23 PM UTC

   We are currently experiencing an issue with the Core and Analytics reports for MIDE01 POD. All other application workflows are operating as expected. Our team is actively investigating the issue, and we will provide updates as soon as more information becomes available.

2. identified Mar 01, 2026, 04:39 PM UTC

   All the services other than reports are up and running fine. Few Core and Analytics reports for MIDE01 POD might be stale. We have been working with our cloud service provider (AWS) to resolve the same. Thanks for your patience and apologies for the inconvenience.

3. identified Mar 02, 2026, 05:54 AM UTC

   We are currently waiting for a fix from the Cloud provider (AWS) and are staying in close contact with their support team to ensure this is resolved as quickly as possible. We will provide updates as soon as we receive new information or when a fix has been implemented. Thank you for your patience and understanding.

4. identified Mar 02, 2026, 08:51 AM UTC

   We are currently experiencing application accessibility issues with the evolving power situation in the region where the cloud provider (AWS) data center is hosted. We will provide updates as soon as we receive new information or when a fix has been implemented. Thank you for your patience and understanding.

5. identified Mar 02, 2026, 09:45 AM UTC

   We are currently waiting for a fix from the Cloud provider (AWS) and are staying in close contact with their support team to ensure this is resolved as quickly as possible. We will provide updates as soon as we receive new information or when a fix has been implemented. Thank you for your patience and understanding.

6. identified Mar 02, 2026, 11:45 AM UTC

   We are currently waiting for a fix from the Cloud provider (AWS) and are staying in close contact with their support team to ensure this is resolved as quickly as possible. We will provide updates as soon as we receive new information or when a fix has been implemented. Thank you for your patience and understanding.

7. identified Mar 02, 2026, 01:59 PM UTC

   We continue to wait for a fix from the Cloud provider (AWS) and are staying in close contact with their support team to ensure this is resolved as quickly as possible. We will provide updates as soon as we receive new information or when a fix has been implemented. Thank you for your patience and understanding.

8. identified Mar 02, 2026, 03:46 PM UTC

   We continue to wait for a fix from the Cloud provider (AWS) and are staying in close contact with their support team to ensure this is resolved as quickly as possible. We will provide updates as soon as we receive new information or when a fix has been implemented. Thank you for your patience and understanding.

9. identified Mar 02, 2026, 05:13 PM UTC

   We continue to wait for a fix from the Cloud provider (AWS) and are staying in close contact with their support team to ensure this is resolved as quickly as possible. We will provide updates as soon as we receive new information or when a fix has been implemented. Thank you for your patience and understanding.

10. identified Mar 02, 2026, 06:07 PM UTC

    We continue to wait for a fix from the Cloud provider (AWS) and are staying in close contact with their support team to ensure this is resolved as quickly as possible. We will provide updates as soon as we receive new information or when a fix has been implemented. Thank you for your patience and understanding.

11. identified Mar 02, 2026, 11:14 PM UTC

    We continue to wait for a fix from the Cloud provider (AWS) and are staying in close contact with their support team to ensure this is resolved as quickly as possible. We will provide updates as soon as we receive new information or when a fix has been implemented. Thank you for your patience and understanding.

12. identified Mar 03, 2026, 04:44 AM UTC

    We continue to wait for a fix from the Cloud provider (AWS) and are staying in close contact with their support team to ensure this is resolved as quickly as possible. We will provide updates as soon as we receive new information or when a fix has been implemented. Thank you for your patience and understanding. Link to the Cloud provider status page is: https://health.aws.amazon.com/health/status

13. identified Mar 03, 2026, 08:56 AM UTC

    We continue to wait for a fix from the Cloud provider (AWS) and are staying in close contact with their support team to ensure this is resolved as quickly as possible. We will provide updates as soon as we receive new information or when a fix has been implemented. Thank you for your patience and understanding. Link to the Cloud provider status page is: https://health.aws.amazon.com/health/status

14. identified Mar 03, 2026, 12:51 PM UTC

    We continue to wait for a fix from the Cloud provider (AWS) and are staying in close contact with their support team to ensure this is resolved as quickly as possible. We will provide updates as soon as we receive new information or when a fix has been implemented. Thank you for your patience and understanding. Link to the Cloud provider status page is: https://health.aws.amazon.com/health/status

15. identified Mar 03, 2026, 01:27 PM UTC

    We continue to wait for a fix from the Cloud provider (AWS) and are staying in close contact with their support team to ensure this is resolved as quickly as possible. We will provide updates as soon as we receive new information or when a fix has been implemented. Thank you for your patience and understanding. We will provide another update by March 3 at 10:00 AM PST Link to the Cloud provider status page is: https://health.aws.amazon.com/health/status

16. identified Mar 03, 2026, 06:59 PM UTC

    We continue to wait for a fix from the Cloud provider (AWS) and are staying in close contact with their support team to ensure this is resolved as quickly as possible. We will provide updates as soon as we receive new information or when a fix has been implemented. Thank you for your patience and understanding. Link to the Cloud provider status page is: https://health.aws.amazon.com/health/status

17. identified Mar 04, 2026, 03:34 AM UTC

    Few EC2 instances are responding intermittently, while Redis, DynamoDB, and DocumentDB are returning 504 errors. These services are critical for the Zenoti application to function normally. Our team is actively working to restore all affected services. We will share further updates as soon as we receive new information or once a fix has been implemented. Thank you for your patience and understanding. Link to the Cloud provider status page is: https://health.aws.amazon.com/health/status

18. identified Mar 04, 2026, 06:04 AM UTC

    We continue to work on restoring all affected services. Further updates will be shared as soon as new information becomes available or once a fix has been implemented. Thank you for your patience and understanding. For the latest updates from the cloud provider, please refer to the status page: https://health.aws.amazon.com/health/status

19. identified Mar 04, 2026, 09:02 AM UTC

    We continue to work on restoring all affected services. Further updates will be shared as soon as new information becomes available or once a fix has been implemented. Thank you for your patience and understanding. For the latest updates from the cloud provider, please refer to the status page: https://health.aws.amazon.com/health/status

20. identified Mar 04, 2026, 03:24 PM UTC

    We continue to work on restoring all affected services. Further updates will be shared as soon as new information becomes available or once a fix has been implemented. Thank you for your patience and understanding. For the latest updates from the cloud provider, please refer to the status page: https://health.aws.amazon.com/health/status

21. identified Mar 04, 2026, 06:32 PM UTC

    We continue to work on restoring all affected services. Further updates will be shared as soon as new information becomes available or once a fix has been implemented. Thank you for your patience and understanding.

22. monitoring Mar 05, 2026, 09:07 AM UTC

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

23. monitoring Mar 11, 2026, 07:53 AM UTC

    While most of the application components are working fine, we are observing some issues with the reports functionality. Our team is working on a fix to restore it.

24. monitoring Mar 11, 2026, 08:05 AM UTC

    A fix has been implemented, and the reports functionality is restored. we are monitoring the results.

25. resolved Apr 01, 2026, 09:39 AM UTC

    This incident has been resolved.