Looking for an update now? Check the current status, or follow Zenoti for future changes.
75.5%of 53 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
66.7%
24
8
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 24Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
A fix has been implemented and Zenoti application is now operating as expected. We will continue to monitor performance closely and provide updates if needed.
investigating
We are observing intermittent slowness when accessing the Zenoti application for customers hosted on ASIA11. We are investigating the cause and will provide an update as soon as possible.
We have received some confirmations from the field that the response time is better now. Our team is continuing to monitor the systems.
monitoring
We have implemented a fix for the issue. We are monitoring the systems closely.
investigating
We are observing a higher-than-normal response time on our monitoring systems for API services on AMRS09, which may be causing the application to respond slowly for few customers hosted on this POD. We are investigating the cause and will provide an update as soon as possible.
Our Cloud service provider (Azure) is still working on resolving the issues at their end. They have implemented some fixes and are observing early signs of recovery. We are closely monitoring this and will continue to provide updates as they become available. Thank you for your patience.
identified
We have identified an issue with our Azure cloud provider resulting in intermittent connection issues. Our team is actively working with the provider to resolve the problem and we will continue to share updates as we have them. Thank you for your patience.
investigating
We are continuing to investigate this issue and will provide an update as soon as possible. Thank you for your patience.
investigating
We are continuing to investigate this issue and will provide an update as soon as possible. Thank you for your patience.
investigating
We are continuing to investigate this issue and will provide an update as soon as possible. Thank you for your patience.
investigating
We are continuing to investigate this issue and will provide an update as soon as possible. Thank you for your patience.
investigating
We are continuing to investigate this issue and will provide an update as soon as possible. Thank you for your patience.
investigating
We are continuing to investigate this issue and will provide an update as soon as possible. Thank you for your patience.
investigating
We are investigating reports of intermittent issues affecting some customers hosted in the EURO01, AMRS18 and EMEA02 regions. Our teams have not been able to reproduce the issue internally and we are working directly with our cloud infrastructure provider to determine whether there is an underlying platform issue.
We understand the impact this may have on your operations and appreciate your patience while we work toward a resolution. We will post further updates as soon as more information i...
A fix has been implemented and all components are working fine now. Our teams are internally verifying the application to ensure things are back to normal. Thanks for your patience and apologies for the inconvenience.
identified
Our Cloud service provider (Azure) is still working on resolving the issues at their end. They have implemented some fixes and are observing early signs of recovery. We are closely monitoring this and will continue to provide updates as they become available. Thank you for your patience.
identified
We are currently waiting for a fix from the Azure Cloud provider and are staying in 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.
identified
We have identified an issue with our Azure cloud provider resulting in intermittent connection issues. Our team is actively working with the provider to resolve the problem and we will continue to share updates as we have them. Thank you for your patience.
investigating
We are continuing to investigate this issue with our Azure Cloud partner and will provide an update as soon as possible. Thank you for your patience.
investigating
We are continuing to investigate this issue with our Azure Cloud partner and will provide an update as soon as possible. Thank you for your patience.
investigating
We are continuing to investigate this issue and will provide an update as soon as possible. Thank you for your patience.
investigating
We are continuing to investigate this issue and will provide an update as soon as possible. Thank you for your patience.
investigating
We are continuing to investigate this issue and will provide an update as soon as possible. Thank you for your patience.
investigating
We are continuing to investigate this issue and will provide an update as soon as possible. Thank you for your patience.
investigating
We are continuing to investigate this issue and will provide an update as soon as possible. Thank you for your patience.
investigating
We are continuing to investigate this issue and will provide an update as soon as possible. Thank you for your patience.
investigating
We are continuing to investigate this issue and will provide an update as soon as possible. Thank you for your patience.
investigating
We are continuing to investigate this issue and will provide an update as soon as possible. Thank you for your patience.
investigating
We are continuing to investigate this issue and will provide an update as soon as possible. Thank you for your patience.
investigating
We are seeing intermittent issues for customers hosted on Zenoti-EURO01 and Zenoti-EMEA02. Our team is actively investigating the issue and we will provide updates as soon as more information becomes available.
Legacy Incident Archive
36 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
April 2026
AMRS17 Login Issues
criticalSource not attested
Last archived state: resolved
View archived record details
identified
The issue has been identified, and a fix has been implemented. We're seeing recovery of the application.
investigating
We are seeing reports on login related issues on AMRS17. Our team is actively looking into this issue.
Issue with Guest Search on EMEA02
Source not attested
Last archived state: resolved
View archived record details
identified
The issue has been identified and a fix is being implemented.
investigating
We are receiving reports of guest search not working in some cases for the customers hosted on EMEA02. Our team is actively working on identifying the issue and sort it ASAP.
Other functions of the application are working fine at this point.
Data Refresh Issue for User Notes Reports in Analytics
Source not attested
Last archived state: resolved
View archived record details
identified
We are facing an issue with the replication of the user notes data to the reporting systems. This data will be stale by a day at this point.
Our team is working on restoring replication for the rest of the data to ensure all other reports work correctly.
We regret the inconvenience it may cause.
Intermittent slowness in certain workflows on AMRS01
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are currently investigating an issue of intermittent slowness on AMRS01.
Slowness in certain workflows on AMRS05
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The slowness is resolved now. We're continuing to monitor the situation.
investigating
We are observing intermittent slowness in some workflows for the customers hosted on AMRS05. Our engineers are actively looking into this to identify and mitigate.
March 2026
MIDE01- Login Issues
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented, and the reports functionality is restored. we are monitoring the results.
monitoring
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.
monitoring
A fix has been implemented and we are monitoring the results.
identified
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.
identified
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
identified
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
identified
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
identified
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
identified
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
identified
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
identified
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
identified
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
identified
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
identified
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.
identified
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.
identified
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.
identified
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.
identified
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.
identified
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.
identified
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.
identified
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.
identified
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.
identified
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.
investigating
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.
