Hummingbird had 10 outages in the last 2 years totaling 254h 12m of downtime — averaging 0.4 incidents per month.
There were 10 Hummingbird outages since August 7, 2025 totaling 254h 12m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
FinCEN's server has begun responding this morning. We've resumed sending filings and expect all pending filings to be submitted shortly.
Update 8/13: We have a fix in place and data is now up to date in reporting dashboards.