Zūm Rails Outage History

This incident has been resolved.

On October 1, 2026, from approximately 7:52 p.m. to 7:55 p.m. Eastern Time (EDT), the Zūm Rails API experienced instability for around three minutes following a hardware failure in the underlying Amazon Web Services (AWS) infrastructure. Service recovered automatically, and this incident is resolved. The failure originated in AWS infrastructure; although Zūm Rails has redundancy, rare infrastructure failures can still cause brief interruptions while recovery takes place. This incident is unrelated to the other incident reported earlier today.

On October 1, between approximately 12:14 PM and 1:20 PM EDT, some Zūm Rails API requests were slow or failing. The issue started during a routine software update that coincided with a period of unusually high traffic, which left our API servers temporarily unable to handle incoming requests. Webhooks, and routine jobs such as EFT kept running throughout, from initial check ups no data was found to be lost. Our team restored full service by 1:20 PM EDT. We're now improving how updates are rolled out, to avoid the issue from happening again. We apologize for the disruption and will keep you updated as needed. Thank you for your understanding

We are happy to report that we received confirmation that the issue has been fully resolved. Again, there was an Interac outage from 11:15AM to 11:30AM EST as well as 11:35AM to 12:15PM EST, but they have confirmed that all is operational. We thank you for your understanding and please let us know if you're experiencing any other issues.

Please be advised that the delay issue with Interac (Option 1) has been resolved. Transactions created from 10:45 AM EST to 11:35 AM EST were affected, but they were processed at 11:35 AM EST and should continue as expected. If you are encountering any issues outside of this window, please reach out to [email protected] for assistance. Thank you for your understanding,

This incident has been resolved. Our banking partner has confirmed that the issue on their end has been fully addressed, and Interac e-Transfer payments are now processing normally across all Interac URL clients. We have been monitoring our platform throughout and can confirm that processing has returned to expected levels. We apologize for the disruption this may have caused and thank you for your patience while we worked to restore service.

We are happy to report that the issue with the Interac transactions has been resolved and no further issues have occurred. We thank you for your understanding while we worked through this issue and appreciate all your feedback while we conducted our investigations. Thank you

The fix has been fully deployed and our team has confirmed that there are no further issues. Details below: Earlier today, between approximately 9:05 AM and 9:55 AM EST, an unexpected AWS storage event briefly impacted our database performance. As a result, our portal was offline and some payments may appear as in progress even though they were successfully completed or failed. Our team has identified the root cause and implemented new safeguards, including an improved database monitoring process, early-warning alerts to our support team, and enhanced storage auto-scaling to prevent recurrence. We are also reviewing all transactions and will notify you of any inconsistent payment statuses. If you have any doubts, please contact our support team before re-initiating a payment to avoid duplication. Thank you for your understanding

We are experiencing a delay in processing EFT files with one of our banks today. We typically exchange files with banks three times a day: at 6 AM, 3 PM, and 7 PM. Specifically, we exchange one file for debit transactions and one file for credit transactions. Today, the three credit files (sent at 6 AM, 3 PM, and 7 PM) and the two debit files (pulled at 3 PM and 7 PM) will be delayed until October 3rd at 6 AM. The debit file from 6 AM today was processed normally. If you are with a bank that exchanges files at 3 AM, please note that there will be no impact for you. Our team has been working throughout the day to resolve this issue with the affected bank. We apologize for any inconvenience this may have caused.

We are happy to report the issues with our banking partner and Interac transactions has been fully resolved! This incident caused all Interac transactions to fail with a Generic Error as well as some registered auto-deposit emails to become deactivated. Any Interac transactions created through your Zūm account that have failed due to Generic Error will need to be recreated. Thank you for your patience and understanding while we work through this with our partner banks, and we apologize for the inconvenience and impact this has caused your business.

We want to update you that the issue affecting our system earlier today has been fully resolved. The system experienced downtime from 6:45 AM EST to 7:27 AM EST, and after a thorough investigation, our team identified that the root cause was due to a specific client with a unique use case that inadvertently overloaded the system, impacting other users. To prevent this from happening again, we have implemented a new mechanism to safeguard system stability and mitigate similar situations in the future. Our team will continue to monitor performance closely to ensure everything runs smoothly. We appreciate your patience and understanding as we worked to resolve this issue.

Please be advised that the issue for Interac Option 1 - Accounts Payable transactions has been resolved. Thank you for your understanding

This incident has been resolved. The system was unstable for 29 minutes, and our team is assessing the root cause to prevent this problem from happening again. Thank you for your understanding.

Please be informed that INTERAC has advised us that the technical issue you were experiencing has now been resolved. We will share a post-incident report with you as soon as we receive it from INTERAC.