Zenoti Outage History
Uptime record, past incidents, and downtime history for Zenoti.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| May 2026 | 69.2% | 13 | 4 |
| April 2026 | 50% | 30 | 15 |
| March 2026 | 0% | 4 | 4 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 47 Days)
Mar 28
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
May 2026
ASIA, EMEA Data refresh for core and analytics reports is impacted
Started: May 11, 6:10 PM
monitoring
A fix has been implemented, and all the reports (both core and analytics) are now operational.
We are monitoring the application closely for any issues.
May 12, 3:53 AM
identified
We have identified the issue, and a fix is being implemented right now. We'll keep you posted on the progress.
May 12, 3:34 AM
investigating
We are currently experiencing an issue with the Core and Analytics reports for ASIA02, ASIA03, ASIA12, EMEA02, and EMEA03 PODs. 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.
May 11, 6:10 PM
Analytics Service Degradation
Started: May 8, 3:08 PM
monitoring
The service is now operational. We're monitoring closely.
May 8, 3:19 PM
investigating
We are currently experiencing an issue with our Analytics Service (analytics02.zenoti.com). We will send an additional update as soon as we resolve this issue.
May 8, 3:08 PM
Zenoti Application Intermittent Issues
Started: May 4, 12:14 PM
monitoring
A fix has been implemented and we are monitoring the results.
May 4, 12:43 PM
investigating
We are investigating reports of intermittent unavailability of application. The customers might see slow response from the application in between.
Our Team is actively working on identifying the root cause.
May 4, 12:14 PM
April 2026
Delay in Payout Processing (US and Canada)
Started: Apr 27, 2:48 PM
monitoring
We have an update regarding the payout initiation delay impacting a subset of customers in the United States and Canada.
Payouts that were delayed earlier today (April 27, 2026) have now been successfully initiated. We have received confirmation that the delayed payouts have been processed. These payouts are expected to be received later this evening and should not be delayed by a full business day.
We continue to monitor the situation closely.
Apr 27, 7:38 PM
investigating
We are continuing to investigate this issue.
Apr 27, 3:32 PM
investigating
We are currently experiencing a delay in payout initiation for some customers in the United States and Canada region.
Payouts that are typically initiated around 1:15 AM EST on Mondays were delayed today (April 27) and initiated closer to 1:55 AM EST. Due to this delay, some payouts may have missed the Fed ACH cutoff window, resulting in deposits being deferred to the next business day (April 28, 2026).
We are actively working with our payment partner (Adyen) who is currently investigating t...
Apr 27, 2:48 PM
AMRS17 Login Issues
Started: Apr 26, 12:14 AM
identified
The issue has been identified, and a fix has been implemented. We're seeing recovery of the application.
Apr 26, 12:24 AM
investigating
We are seeing reports on login related issues on AMRS17. Our team is actively looking into this issue.
Apr 26, 12:14 AM
Issue with Guest Search on EMEA02
Started: Apr 21, 1:11 PM
identified
The issue has been identified and a fix is being implemented.
Apr 21, 1:25 PM
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.
Apr 21, 1:11 PM
Data Refresh Issue for User Notes Reports in Analytics
Started: Apr 2, 11:55 AM
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.
Apr 2, 11:55 AM
Intermittent slowness in certain workflows on AMRS01
Started: Apr 2, 1:09 AM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 2, 1:30 AM
investigating
We are currently investigating an issue of intermittent slowness on AMRS01.
Apr 2, 1:09 AM
Slowness in certain workflows on AMRS05
Started: Apr 1, 2:36 PM
monitoring
The slowness is resolved now. We're continuing to monitor the situation.
Apr 1, 3:22 PM
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.
Apr 1, 2:36 PM
March 2026
MIDE01- Login Issues
Started: Mar 1, 4:23 PM
monitoring
A fix has been implemented, and the reports functionality is restored. we are monitoring the results.
Mar 11, 8:05 AM
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.
Mar 11, 7:53 AM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 5, 9:07 AM
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.
Mar 4, 6:32 PM
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
Mar 4, 3:24 PM
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
Mar 4, 9:02 AM
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
Mar 4, 6:04 AM
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
Mar 4, 3:34 AM
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
Mar 3, 6:59 PM
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
Mar 3, 1:27 PM
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
Mar 3, 12:51 PM
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
Mar 3, 8:56 AM
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
Mar 3, 4:44 AM
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.
Mar 2, 11:14 PM
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.
Mar 2, 6:07 PM
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.
Mar 2, 5:13 PM
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.
Mar 2, 3:46 PM
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.
Mar 2, 1:59 PM
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.
Mar 2, 11:45 AM
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.
Mar 2, 9:45 AM
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.
Mar 2, 8:51 AM
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.
Mar 2, 5:54 AM
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.
Mar 1, 4:39 PM
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.
Mar 1, 4:23 PM