Zūm Rails incident

Interac - Degraded Performance

Minor Resolved View vendor source →

Zūm Rails experienced a minor incident on June 4, 2026 affecting Interac, lasting 19m. The incident has been resolved; the full update timeline is below.

Started
Jun 04, 2026, 03:53 PM UTC
Resolved
Jun 04, 2026, 04:13 PM UTC
Duration
19m
Detected by Pingoru
Jun 04, 2026, 03:53 PM UTC

Affected components

Interac

Update timeline

  1. identified Jun 04, 2026, 03:53 PM UTC

    Please be advised that a few merchants are experiencing Interac issues with some of their transactions. We have already connected with Interac to confirm the issue and they are working on a fix. We will provide updates as soon as possible. Thank you for your understanding

  2. resolved Jun 04, 2026, 04:13 PM UTC

    Please be advised that the Interac issue from 11:05AM to 11:40AM EST has been resolved. Once we have more details from Interac on the issue, we will update here as well. If you are still experiencing issues, please email [email protected] and we will investigate further. Thank you for your understanding

  3. postmortem Jun 04, 2026, 05:10 PM UTC

    **Incident Summary** On June 4th, from 11:00 to 11:40 AM, we had a production issue that hit some of our clients. Zūm Rails lets clients create a user and a transaction in a single call — and that's the flow that broke. The bug only fired when the user already existed in the system. Since some clients pass user data on every transaction request regardless of whether the user is new, a lot of calls failed, specifically for Interac payments, which is why it was identified as an Interac issue at first. Each one came back with an error, no transaction created, and clients had to retry. No funds were moved at all, and no transactions are inconsistent. **Resolution & Prevention** We caught it fast and resolved it by 11:40 AM. Still — 40 minutes is too long, and we're sorry for the disruption. After a proper post-mortem with the team, we added a targeted check in our deployment pipeline that exercises this exact scenario before anything ships. We apologize for any inconvenience and appreciate your understanding. Any transactions that were not created because of this error may not be recreated. If you already retried after 11:40 AM EST, they should have moved accordingly and thus no further action is needed. Thank you