You should now see more accurate congestion, delay, and utilization metrics across the platform, including corrected values for ports such as Warri and Lagos–Tin Can.
Thanks to everyone who reported the issue. Your feedback helped us improve the accuracy of our live analytics.
We’ve deployed an update to the engine powering our live port congestion metrics.
We identified an issue where background data synchronization refreshed internal timestamps on historical vessel records, allowing some inactive voyages to be counted as live traffic.
In certain cases, this inflated congestion percentages.
The fix changes congestion calculations to rely on operational vessel events rather than synchronization timestamps, while automatically excluding inconsistent historical records older than 30 days.
This means:
• Agent performance is now compared on clean, consistent cargo groupings
• Global benchmarks and agent benchmarks are aligned on the same definitions
• Spelling or formatting differences no longer affect ranking or speed analysis
We’ve upgraded how agent performance is calculated in Hafintel.
Before now, small differences in how cargo types were written could split data unintentionally. For example, “G/CARGO”, “GEN. CARGO”, and
We’ve built a unified normalization layer that automatically standardizes cargo types into a single meaning before any performance calculation happens. So regardless of how an agent or system records it, all variations of general cargo are treated as one consistent category.
One shipping agent processed GEN. CARGO imports 75% faster than average.
Another was 37% slower than average under the same port.
Not because of luck.
But because the operational patterns behind that movement — clearance speed, turnaround efficiency, and
In addition, we built a terminal ranking system that evaluates throughput and delay performance per cargo flow, with ranked positions where data is sufficient and “pending” status where it is not.
We are evolving Hafintel Version 3 into a real-time port intelligence system that goes beyond shipment tracking to deliver actionable operational insights.
We also developed agent-level performance intelligence that benchmarks shipping agents by cargo type efficiency, showing how they perform against global averages in clear percentage terms.
Lagos – Tin Can Port congestion has surged sharply over the past 5 days.
• Congestion: 83% ↑
• Avg. arrival delay: 57 hrs ↓
• Vessels awaiting clearance: 10 ↑
Despite improved arrival flow, vessel buildup at the port has intensified, pushing congestion levels higher.
Lagos - Tin Can Port is seeing heavy delays today.
• Congestion: 50%
• Avg. arrival delay: 130 hrs (~5.4 days)
• Avg. berth wait: 4 hrs
• Vessels awaiting clearance: 6
Track congestion, delays, and vessel activity across other ports on
https://t.co/AdKIXfkasC
We’ve fixed the "frozen" data issues and introduced a visual-first Analytics suite because we believe intelligence should be beautiful and actionable.
Log in now to see the new HAFINTEL: https://t.co/AdKIXfkasC
When we launched Hafintel v1, our goal was simple: show the ships. But as the data grew, we noticed some cracks. Slower sync times, "frozen" delay numbers, and data that didn't tell the full story of why a port was congested. We knew we had to do better.
We’ve added a "National Pulse" to our landing page. Before you even log in, you can see which maritime gateways are clear and which are red zones. It’s a 10,000ft view of Nigeria’s shipping efficiency.