Hummingbird Outage History

The FINTRAC service has been restored and filings are proceeding as normal.

**Email delivery restored** Email delivery has been restored, and all pending emails have now been sent. No emails were lost during this incident. We're sorry for any inconvenience this caused, and we appreciate your patience.

This incident is resolved. We’ve released code changes that improve our resilience to the upstream provider (Azure) failure and route around the affected region. The AI assistant has been re-enabled and confirmed operational. All systems are fully operational. All other functionality remained available throughout the incident. We apologize to those whose work was disrupted by the loss of the AI assistant, and thank you for your patience.

Between 11:10–12:25 ET on July 23rd, we experienced degraded performance affecting create and update operations. Latency was most noticeable in file uploads and case creation, where newly created or updated records took approximately 45 minutes to appear in the app after being submitted. The issue has been identified and resolved, and performance has returned to normal. No data was lost, and all affected operations were processed successfully. We apologize for the disruption and are taking steps to prevent a recurrence.

Earlier this evening during a routine maintenance task the Hummingbird app was inadvertently placed into maintenance mode for about 90 seconds. During this time users may have experienced failed operations or blank page loads. The app is now functioning normally.

This issue has been resolved and FINTRAC filing is functioning normally at this time. We apologize for the temporary disruption.

The issue affecting automation event processing has been fully resolved. All backlogs have been cleared and processing times have returned to normal levels. We will continue to monitor to ensure ongoing stability.

We’ve resolved the intermittent latency impacting application performance. Our investigation identified a larger global routing issue related to an upstream networking provider, with primary impact to customers in Europe and Asia. At approximately 2:00 PM ET, we deployed a mitigation by reconfiguring our edge routing. Since that change, we have monitored performance and are no longer observing elevated latency.

At this time the CloudFlare incident has been resolved. Hummingbird will continue to monitor for any ongoing impact to our services.

The Hummingbird team has identified and addressed the root cause of the intermittent errors affecting the app. The issue was traced to a recent update in one of our underlying libraries. We have rolled back the update, and error rates have since returned to normal. We will continue to monitor the situation to ensure ongoing stability.

We’ve observed significantly lower error rates over the past hour, and the application is now performing as expected. We are considering this incident resolved, though our team will continue to monitor the system closely to ensure stability. Thank you for your patience.

The root cause of the latency was due to an issue with an upstream networking provider. That issue is now resolved and Hummingbird's response times have returned to normal.

All Hummingbird systems are now fully operational. The earlier issues related to the AWS outage and downstream providers have been resolved. We continue to monitor for stability and appreciate your patience throughout this incident.