Completed -
The scheduled maintenance has been completed.
Jul 10, 23:30 EDT
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 10, 21:30 EDT
Update -
We will be undergoing scheduled maintenance during this time.
Jul 7, 16:13 EDT
Update -
We will be undergoing scheduled maintenance during this time.
Jul 7, 16:12 EDT
Scheduled -
Scheduled Date: Wednesday, July 10, 2025 Time: 9:30 PM EST Duration: 2 hours Expected Outage: None
We will be performing maintenance on HSM clusters to apply essential system updates and upgrades. These updates are part of our regular enhancement process to maintain security, performance, and reliability.
No downtime or service interruptions are expected during this maintenance window.
If you have any concerns or encounter unexpected issues, please reach out to our support team.
Thank you for your continued support.
Zift Operations Team status.zift.io | support@zift.io
Jul 7, 16:10 EDT
Completed -
The scheduled maintenance has been completed.
Jul 9, 23:30 EDT
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 9, 21:30 EDT
Scheduled -
Scheduled Date: Wednesday, July 9, 2025 Time: 9:30 PM EST Duration: 2 hours Expected Outage: None
We will be performing maintenance on HSM clusters to apply essential system updates and upgrades. These updates are part of our regular enhancement process to maintain security, performance, and reliability.
No downtime or service interruptions are expected during this maintenance window.
If you have any concerns or encounter unexpected issues, please reach out to our support team.
Thank you for your continued support.
Zift Operations Team status.zift.io | support@zift.io
Jul 7, 16:08 EDT
The scheduled Database Cluster Maintenance originally planned for:
Date: Tuesday, July 8, 2025 Time: 7:30 PM EST Duration: 1.5 hours
has been cancelled.
This maintenance was intended to enhance capacity and performance, but will be rescheduled for a future date. We will notify you once the new schedule is confirmed.
No action is required at this time. If you have any questions, please contact our support team.
Thank you for your understanding.
Zift Operations Team status.zift.io | support@zift.io
Jul 8, 19:38 EDT
Update -
We will be undergoing scheduled maintenance during this time.
Jul 7, 16:11 EDT
Scheduled -
Scheduled Date: Tuesday, July 8, 2025 Time: 7:30 PM EST Duration: 1.5 hours Expected Outage: None
Zift will be performing scheduled Database Cluster Maintenance to improve capacity and performance. This proactive maintenance is part of our ongoing efforts to ensure optimal system performance and scalability.
No service interruptions are expected during this window.
If you have any questions or experience unexpected behavior during the maintenance period, please contact our support team.
Thank you for your understanding.
Zift Operations Team status.zift.io | support@zift.io
Jul 7, 15:58 EDT
We have completed updates to Zift terminals that were experiencing S20 errors after extended idle periods. These updates are now live and should prevent the issue from recurring.
If you continue to experience any issues processing transactions with your Zift terminal, please contact Zift Support for immediate assistance.
Thank you for your continued patience and partnership.
Zift Operations Team status.zift.io | support@zift.io
Jul 4, 17:10 EDT
Identified -
Zift Incident Notice: Terminal S20 Error While Idle
We are currently aware of an issue affecting some terminals, where an S20 error may appear after the terminal has been idle for an extended period of time.
Our team has identified the root cause and is actively working on delivering updates to all affected terminals.
In the meantime, merchants can continue to process transactions using the Merchant Console as an alternative.
If you have any questions or need assistance, please contact Zift Support.
We appreciate your patience and understanding.
Zift Operations Team status.zift.io | support@zift.io
Jul 4, 08:58 EDT
Resolved -
This incident has been resolved.
Jul 2, 22:28 EDT
Update -
As of 5:35 PM EST, Google has resolved the DNS issues that were impacting connectivity. All Zift services are now fully operational, including terminal connectivity.
If your terminal is still showing as offline, please contact Zift Support for assistance.
For merchants who updated their terminal DNS settings to 1.1.1.1, there is no immediate need to revert those changes. Your terminal will continue to function properly using 1.1.1.1, as that DNS service remains stable and fully supported.
This incident will remain open while we continue to monitor this issue.
Zift Operations Team status.zift.io | support@zift.io
Jul 2, 17:49 EDT
Update -
Zift, along with other companies, continues to experience issues related to Google DNS.
For Zift merchants using Suni terminals, we’ve developed a workaround to help mitigate the impact of these DNS problems. Please follow the instructions at the link below:
If you have any questions or need assistance with this process, please don’t hesitate to contact Zift Support.
Zift Operations Team status.zift.io | support@zift.io
Jul 2, 17:25 EDT
Monitoring -
Global DNS services are starting to improve. If you have experienced an issue access the Zift portal or running at transaction we recommend trying your transaction again at this time.
Jul 2, 16:21 EDT
Investigating -
Date: July 2, 2025 Impact: Terminals, Real-Time Transaction Processing, and Portal Access
Zift is currently experiencing service disruptions due to a widespread issue affecting Google’s DNS infrastructure. As a result, the following Zift services may be intermittently impacted:
Terminal Connectivity and Processing Real-Time Transaction API Performance and Availability Access to the Zift Portal and Administrative Interfaces
We are actively monitoring the situation and working with upstream providers to mitigate downstream effects. Our infrastructure teams are implementing DNS redundancy measures where feasible to reduce user impact.
We will provide updates as more information becomes available or once the issue is fully resolved. We appreciate your patience and understanding.
Next Update: Within 60 minutes or sooner if conditions change.