- Detected by Pingoru
- Apr 26, 2026, 12:14 AM UTC
- Resolved
- Apr 26, 2026, 12:34 AM UTC
- Duration
- 19m
Affected: Zenoti-AMRS17
Timeline · 4 updates
-
investigating Apr 26, 2026, 12:14 AM UTC
We are seeing reports on login related issues on AMRS17. Our team is actively looking into this issue.
-
identified Apr 26, 2026, 12:24 AM UTC
The issue has been identified, and a fix has been implemented. We're seeing recovery of the application.
-
monitoring Apr 26, 2026, 12:32 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 26, 2026, 12:34 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 21, 2026, 01:11 PM UTC
- Resolved
- Apr 21, 2026, 01:56 PM UTC
- Duration
- 44m
Affected: Zenoti-EMEA02
Timeline · 3 updates
-
investigating Apr 21, 2026, 01:11 PM UTC
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.
-
identified Apr 21, 2026, 01:25 PM UTC
The issue has been identified and a fix is being implemented.
-
resolved Apr 21, 2026, 01:56 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 02, 2026, 11:55 AM UTC
- Resolved
- Apr 04, 2026, 10:50 AM UTC
- Duration
- 1d 22h
Affected: Zenoti-CNDA01
Timeline · 2 updates
-
identified Apr 02, 2026, 11:55 AM UTC
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.
-
resolved Apr 04, 2026, 10:50 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 02, 2026, 01:09 AM UTC
- Resolved
- Apr 02, 2026, 01:41 AM UTC
- Duration
- 32m
Affected: Zenoti-AMRS01
Timeline · 3 updates
-
investigating Apr 02, 2026, 01:09 AM UTC
We are currently investigating an issue of intermittent slowness on AMRS01.
-
monitoring Apr 02, 2026, 01:30 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 02, 2026, 01:41 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 01, 2026, 02:36 PM UTC
- Resolved
- Apr 01, 2026, 04:40 PM UTC
- Duration
- 2h 3m
Affected: Zenoti-AMRS05
Timeline · 3 updates
-
investigating Apr 01, 2026, 02:36 PM UTC
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.
-
monitoring Apr 01, 2026, 03:22 PM UTC
The slowness is resolved now. We're continuing to monitor the situation.
-
resolved Apr 01, 2026, 04:40 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 22, 2026, 09:30 PM UTC
- Resolved
- Mar 23, 2026, 01:37 AM UTC
- Duration
- 4h 6m
Affected: Zenoti-ASIA01Zenoti-AMRS02Zenoti-AMRS09Zenoti-AMRS14
Timeline · 4 updates
-
investigating Mar 22, 2026, 09:30 PM UTC
We are seeing intermittent issues for customers hosted on Zenoti-AMRS02, Zenoti-AMRS09 and Zenoti-AMRS14. Our team is actively investigating the issue, and we will provide updates as soon as more information becomes available.
-
investigating Mar 22, 2026, 10:34 PM UTC
We are continuing to investigate this issue.
-
monitoring Mar 22, 2026, 11:34 PM UTC
We have deployed a fix to the issue and the application is working now. Our team is monitoring the situation closely.
-
resolved Mar 23, 2026, 01:37 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 21, 2026, 03:21 AM UTC
- Resolved
- Mar 23, 2026, 06:12 AM UTC
- Duration
- 2d 2h
Affected: Zenoti-ASIA12
Timeline · 6 updates
-
investigating Mar 21, 2026, 03:21 AM UTC
We are observing a higher-than-normal response time on our monitoring systems for Zenoti-ASIA12, which may be causing the application to not respond or respond slowly. We are investigating the cause and will provide an update as soon as possible.
-
investigating Mar 21, 2026, 04:31 AM UTC
We are continuing to investigate this issue.
-
investigating Mar 21, 2026, 05:10 AM UTC
We are continuing to investigate this issue.
-
monitoring Mar 21, 2026, 07:47 AM UTC
Primary services have been restored and are operational. Users may experience slower than usual response times as full recovery is underway. Additionally, some reports and analytics may display stale data until the recovery process is complete. Our team is actively working to bring all systems to full capacity. We'll provide another update once everything is fully restored. Thank you for your patience.
-
monitoring Mar 22, 2026, 11:43 AM UTC
Core reports are now showing the latest data. Analytics dashboards may still display stale data as the recovery process continues. Our team is working to restore full data freshness across all analytics. We'll provide another update once analytics are fully up to date. Thank you for your continued patience.
-
resolved Mar 23, 2026, 06:12 AM UTC
All services have been fully restored. Core reports and analytics are now displaying the latest data, and response times are back to normal. We appreciate your patience throughout this recovery. If you notice any lingering issues, please reach out to our support team.
Read the full incident report →
- Detected by Pingoru
- Mar 20, 2026, 12:59 PM UTC
- Resolved
- Mar 20, 2026, 01:23 PM UTC
- Duration
- 23m
Affected: Zenoti-ASIA01Zenoti-ASIA02Zenoti-ASIA03Zenoti-ASIA12Zenoti-ASIA22Zenoti-AMRS02Zenoti-AMRS09Zenoti-AMRS14
Timeline · 3 updates
-
investigating Mar 20, 2026, 12:59 PM UTC
We are investigating an issue with the Guest Search functionality of the application which may be causing the guest search to not respond intermittently. All the other Zenoti application functions are working fine at this moment. Our teams are actively working on identifying the problem.
-
monitoring Mar 20, 2026, 01:09 PM UTC
The issue has been fixed now and the team is monitoring the system for stability.
-
resolved Mar 20, 2026, 01:23 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 19, 2026, 01:23 PM UTC
- Resolved
- Mar 19, 2026, 02:09 PM UTC
- Duration
- 45m
Affected: Zenoti-EURO01
Timeline · 3 updates
-
investigating Mar 19, 2026, 01:23 PM UTC
We are observing a higher-than-normal response time on our monitoring systems for Zenoti-EURO01, which may be causing the application to not respond or respond slowly. We are investigating the cause and will provide an update as soon as possible.
-
monitoring Mar 19, 2026, 02:00 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 19, 2026, 02:09 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 14, 2026, 04:22 PM UTC
- Resolved
- Mar 14, 2026, 05:37 PM UTC
- Duration
- 1h 14m
Affected: Zenoti-AMRS11
Timeline · 4 updates
-
investigating Mar 14, 2026, 04:22 PM UTC
We are observing a higher-than-normal response time on our monitoring systems for AMRS11, which may be causing the application to not respond or respond slowly. We are investigating the cause and will provide an update as soon as possible.
-
investigating Mar 14, 2026, 04:56 PM UTC
We are continuing to investigate the cause and will provide an update as soon as possible. Thank you for your patience.
-
monitoring Mar 14, 2026, 05:22 PM UTC
The system has been stable and working fine since 9:40 a.m. PST and we are monitoring the results.
-
resolved Mar 14, 2026, 05:37 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 13, 2026, 12:55 PM UTC
- Resolved
- Mar 13, 2026, 01:48 PM UTC
- Duration
- 52m
Affected: Zenoti-AMRS22
Timeline · 4 updates
-
investigating Mar 13, 2026, 12:55 PM UTC
We are observing a higher-than-normal response time on our monitoring systems for AMRS22, which may be causing the application to not respond or respond slowly. We are investigating the cause and will provide an update as soon as possible.
-
identified Mar 13, 2026, 01:31 PM UTC
The issue has been identified, and a fix is being implemented. We will provide an update as soon as more information is available. Thank you for your patience.
-
monitoring Mar 13, 2026, 01:44 PM UTC
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
-
resolved Mar 13, 2026, 01:48 PM UTC
The incident has been resolved. All systems are functioning normally, and no further issues have been observed. Thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Mar 09, 2026, 06:30 PM UTC
- Resolved
- Mar 09, 2026, 08:11 PM UTC
- Duration
- 1h 40m
Affected: Zenoti-AMRS02
Timeline · 5 updates
-
investigating Mar 09, 2026, 06:30 PM UTC
We are seeing reports on login related issues on AMRS02. Our team is actively looking into this issue.
-
investigating Mar 09, 2026, 07:10 PM UTC
We are continuing to investigate this issue.
-
identified Mar 09, 2026, 07:43 PM UTC
The issue has been identified, and a fix has been implemented. We're seeing recovery of the application.
-
monitoring Mar 09, 2026, 08:00 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 09, 2026, 08:11 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 05, 2026, 09:40 AM UTC
- Resolved
- Mar 05, 2026, 09:57 AM UTC
- Duration
- 16m
Affected: Zenoti-EURO01
Timeline · 2 updates
-
investigating Mar 05, 2026, 09:40 AM UTC
We are facing intermittent errors spike on EURO01. Customers hosted on this POD might see some issues intermittently. Our team is looking into the issue.
-
resolved Mar 05, 2026, 09:57 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2026, 04:33 PM UTC
- Resolved
- Mar 06, 2026, 02:24 AM UTC
- Duration
- 2d 9h
Affected: Zenoti-AMRS01Zenoti-AMRS02Zenoti-AMRS03Zenoti-AMRS04Zenoti-AMRS05Zenoti-AMRS09Zenoti-AMRS11Zenoti-AMRS12Zenoti-AMRS13Zenoti-AMRS14
Timeline · 2 updates
-
monitoring Mar 03, 2026, 04:33 PM UTC
We’re reaching out to proactively inform you of an external issue that may impact the timing of certain payroll and tax payment settlements processed through Zenoti Integrated Payroll (ZIP). Overnight, the Federal Reserve reported delays in processing and delivering ACH payment files through FedACH. As of 7:30am ET, the Federal Reserve confirmed that ACH credits and debits have been delivered to receiving banks. This delivery occurred approximately 8 hours later than the normal processing window. Impact to ZIP Customers: Delayed settlement of payroll direct deposits and tax payments Deposits may post later than expected Delays in return files, which may impact confirmation of failed debits What to Expect: Although ACH files have now been delivered, the timing of deposit posting and fund availability depends on each receiving bank’s internal processing schedule. Some banks may already reflect payments, while others may not show them until later today. This issue originated with the Federal Reserve’s FedACH system and had nationwide impact across financial institutions. Zenoti is actively monitoring the situation, but we are unable to expedite deposits affected by this delay. Payments will reflect as each receiving bank completes its processing. For updates, you may monitor: Federal Reserve FedACH Status: https://frbservices.org/app/status/outage.do?oId=145787
-
resolved Mar 06, 2026, 02:24 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2026, 04:00 PM UTC
- Resolved
- Mar 03, 2026, 04:35 PM UTC
- Duration
- 35m
Affected: Zenoti-AMRS07
Timeline · 3 updates
-
investigating Mar 03, 2026, 04:00 PM UTC
We are observing a higher-than-normal response time on our monitoring systems for Zenoti-AMRS07, which may be causing the application to not respond or respond slowly. We are investigating the cause and will provide an update as soon as possible.
-
monitoring Mar 03, 2026, 04:18 PM UTC
The system is responding normally now. We are monitoring the performance closely.
-
resolved Mar 03, 2026, 04:35 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 01, 2026, 04:23 PM UTC
- Resolved
- Apr 01, 2026, 09:39 AM UTC
- Duration
- 30d 17h
Affected: Zenoti-MIDE01
Timeline · 25 updates
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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.
-
monitoring Mar 05, 2026, 09:07 AM UTC
A fix has been implemented and we are monitoring the results.
-
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.
-
monitoring Mar 11, 2026, 08:05 AM UTC
A fix has been implemented, and the reports functionality is restored. we are monitoring the results.
-
resolved Apr 01, 2026, 09:39 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 01, 2026, 12:39 PM UTC
- Resolved
- Mar 01, 2026, 03:47 PM UTC
- Duration
- 3h 8m
Affected: Zenoti-MIDE01
Timeline · 9 updates
-
investigating Mar 01, 2026, 12:39 PM UTC
We are observing a higher-than-normal response time on our monitoring systems for Zenoti-MIDE01, which may be causing the application to not respond or respond slowly. We are investigating the cause and will provide an update as soon as possible.
-
investigating Mar 01, 2026, 01:09 PM UTC
We are currently experiencing an outage with our service provider (AWS), resulting in intermittent connection issues for our application. Our team is actively working with the provider to resolve the problem, and we will continue to share updates as we have them.
-
investigating Mar 01, 2026, 01:30 PM UTC
We are currently waiting for a fix from the Cloud provider 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 Mar 01, 2026, 01:46 PM UTC
The issue has been identified and a fix is being implemented. We will provide an update as soon as more information is available. Thank you for your patience.
-
identified Mar 01, 2026, 02:06 PM UTC
We are continuing to work on a fix for this issue and will provide an update as soon as more information is available.
-
monitoring Mar 01, 2026, 02:45 PM UTC
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.
-
monitoring Mar 01, 2026, 03:05 PM UTC
The system has been stable since 5:30 AM PST and all the application workflows are now operational. Our team is monitoring this closely. Thank you for the patience.
-
monitoring Mar 01, 2026, 03:34 PM UTC
We are continuing to monitor for any further issues.
-
resolved Mar 01, 2026, 03:47 PM UTC
We are currently awaiting a permanent fix from our cloud provider and remain in close contact with their support team to ensure a swift resolution. In the meantime, we have implemented a remedial fix on our end, and the application has been operating normally since 5:30 AM PST. All workflows are fully functional at this time. Thank you for your continued patience.
Read the full incident report →
- Detected by Pingoru
- Feb 26, 2026, 10:11 PM UTC
- Resolved
- Feb 26, 2026, 11:03 PM UTC
- Duration
- 52m
Affected: Zenoti-CNDA01
Timeline · 4 updates
-
investigating Feb 26, 2026, 10:11 PM UTC
We are observing a higher-than-normal response time on our monitoring systems for Zenoti-CNDA01, which may be causing the application to not respond or respond slowly. We are investigating the cause and will provide an update as soon as possible.
-
identified Feb 26, 2026, 10:27 PM UTC
The issue has been identified and a fix is being implemented. We will provide an update as soon as more information is available. Thank you for your patience.
-
monitoring Feb 26, 2026, 10:47 PM UTC
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.
-
resolved Feb 26, 2026, 11:03 PM UTC
The incident has been resolved. All systems are functioning normally and no further issues have been observed. Thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Feb 23, 2026, 11:03 AM UTC
- Resolved
- Feb 23, 2026, 01:09 PM UTC
- Duration
- 2h 6m
Affected: Zenoti-EURO01Zenoti-EURO02
Timeline · 4 updates
-
investigating Feb 23, 2026, 11:03 AM UTC
We are observing an issue with our analytics site analytics04.zenoti.com. We are investigating the cause and will provide an update as soon as possible
-
investigating Feb 23, 2026, 12:07 PM UTC
We are continuing to investigate this issue.
-
monitoring Feb 23, 2026, 01:00 PM UTC
The service is now operational. We are continuing to monitor.
-
resolved Feb 23, 2026, 01:09 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 20, 2026, 05:46 PM UTC
- Resolved
- Feb 20, 2026, 08:22 PM UTC
- Duration
- 2h 35m
Affected: Zenoti-AMRS05Zenoti-AMRS13Zenoti-CNDA01
Timeline · 6 updates
-
investigating Feb 20, 2026, 05:46 PM UTC
We are investigating reports of intermittent slowness on multiple pods. The customers might see slow response from the application in between. Our Team is actively working on identifying the root cause.
-
investigating Feb 20, 2026, 06:13 PM UTC
We are continuing to investigate this issue.
-
investigating Feb 20, 2026, 06:26 PM UTC
We are continuing to investigate this issue.
-
investigating Feb 20, 2026, 07:00 PM UTC
We are continuing to investigate this issue.
-
monitoring Feb 20, 2026, 08:01 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 20, 2026, 08:22 PM UTC
This incident has been resolved.
Read the full incident report →
Critical February 19, 2026 - Detected by Pingoru
- Feb 19, 2026, 11:34 PM UTC
- Resolved
- Feb 20, 2026, 12:11 AM UTC
- Duration
- 37m
Affected: Zenoti-AMRS05
Timeline · 3 updates
-
investigating Feb 19, 2026, 11:34 PM UTC
We are seeing unusually higher response time on our servers on AMRS05. The application may be responding slowly or not at all. Our team is looking into the issue actively.
-
monitoring Feb 19, 2026, 11:50 PM UTC
The system is responding normally now. We are monitoring the performance closely.
-
resolved Feb 20, 2026, 12:11 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 13, 2026, 09:44 AM UTC
- Resolved
- Feb 13, 2026, 10:34 AM UTC
- Duration
- 50m
Affected: Zenoti-ASIA03
Timeline · 3 updates
-
investigating Feb 13, 2026, 09:44 AM UTC
We are observing a higher-than-normal response time on our monitoring systems for Zenoti-ASIA03, which may be causing the application to not respond or respond slowly. We are investigating the cause and will provide an update as soon as possible.
-
monitoring Feb 13, 2026, 10:18 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 13, 2026, 10:34 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 12, 2026, 05:54 PM UTC
- Resolved
- Feb 12, 2026, 06:22 PM UTC
- Duration
- 27m
Affected: Zenoti-AMRS14
Timeline · 3 updates
-
investigating Feb 12, 2026, 05:54 PM UTC
We are observing a higher-than-normal response time on our monitoring systems for Zenoti-AMRS14, which may be causing the application to not respond or respond slowly. We are investigating the cause and will provide an update as soon as possible.
-
monitoring Feb 12, 2026, 06:15 PM UTC
The application is working normally now. We are closely monitoring the situation.
-
resolved Feb 12, 2026, 06:22 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 11, 2026, 10:15 PM UTC
- Resolved
- Feb 11, 2026, 10:15 PM UTC
- Duration
- —
Affected: ZPay_USZPay_CAZpay (Stripe) _ US
Timeline · 1 update
-
resolved Feb 11, 2026, 10:15 PM UTC
Dear Zenoti Payments Customer, Please note that Monday, February 16, 2026 is a bank holiday in both the United States and Canada. As a result, payouts that would normally be deposited on Monday, February 16th will instead be deposited on Tuesday, February 17th, 2026. No action is required on your end. Payouts will resume on the regular schedule following the holiday. Thank you for your continued partnership. Best regards, The Zenoti Payments Team
Read the full incident report →
- Detected by Pingoru
- Feb 09, 2026, 02:26 PM UTC
- Resolved
- Feb 09, 2026, 02:51 PM UTC
- Duration
- 25m
Affected: Zenoti-AMRS06
Timeline · 3 updates
-
investigating Feb 09, 2026, 02:26 PM UTC
We are observing a higher-than-normal response time on our monitoring systems for Zenoti-AMRS06, which may be causing the application to not respond or respond slowly. We are investigating the cause and will provide an update as soon as possible.
-
monitoring Feb 09, 2026, 02:38 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 09, 2026, 02:51 PM UTC
This incident has been resolved.
Read the full incident report →
