We are excited to announce three significant enhancements in the Container Intelligence platform, incident visibility, live terminal metrics, and proactive notifications, designed to help you manage risk in real time and reduce manual monitoring effort.
1. Incidents in the Web application
We have introduced a dedicated Incidents layer to help you pinpoint operational bottlenecks before they impact your schedule.
Global coverage: Access a live list of incidents impacting ports, terminals, and vessels globally.
Operational focus: Get alerts covering 8 incident types: Conflict, Politcal, Operational, Accident, Weather, Strike, Holidays, Detention.
Severity mapping: Incidents are color-coded (Red for high impact, Yellow for medium impact, Gray for low impact) to help you prioritize your response. It's meant to be high level visual information. They don't correspond to quantitative/measurable impact.
Historical context: By clicking the "+" icon on any incident row, you can view the full history of updates, ensuring you see how a situation has evolved since it began.
Frequency: Our system checks for new updates every 3 hours, reflecting the latest available data from thousands of global sources.
Note: Important: Incidents are displayed for situational awareness only. They are not currently incorporated into predictive ETA calculations. Incidents are labeled as Ongoing until resolved, at which point they are removed from the live display.
Why it matters
Port disruptions don't announce themselves in advance. A strike, a storm, or a geopolitical event can cascade into schedule delays before your team is even aware. The Incidents layer brings that awareness directly into your workflow — so instead of discovering a problem through a delayed vessel, you see the signal early and can act. Less reactive firefighting, more proactive planning.
2. Enhanced Terminal live metrics
Based on user feedback regarding the complexity of previous indexes, we have streamlined the terminal view to focus on Live Metrics that reflect current reality rather than just historical averages.
Live waiting average: Shows the real-time average wait time for vessels currently in the queue.
Live stay average: Reflects the actual time vessels currently at the berth have spent since berthing.
Simplified interface: We have removed the "Performance Index" and legacy graphs to provide a cleaner, more relatable data set that matches the vessel list you see on screen. We added the waiting vessels and at berth vessels in the top bar.
Accurate planning: This allows you to identify if waiting times are surging right now, enabling you to adjust vessel speeds for Just-in-Time arrivals and save on fuel.
Why it matters
Historical averages can mask what's actually happening at a terminal today. A port that performed well last week may be severely congested right now, and making arrival decisions based on outdated data costs time and fuel. Live metrics give your team a truthful, current picture of terminal conditions, enabling just-in-time arrival decisions that reduce unnecessary waiting and unnecessary fuel burn.
3. Notifications control: Live waiting average
You can now set proactive alerts to stay ahead of port congestion without manually checking the platform.
Threshold alerts: Set custom notifications for any port or specific terminal. You will be notified via email or in-app message when the Live Waiting Average crosses your specified threshold (e.g., exceeds 24 hours).
Multi-Terminal monitoring: You can combine multiple terminals or entire ports (e.g., all terminals in Shanghai) into a single notification rule.
Relaxation alerts: Use "conditions" to be notified when a situation improves (e.g., waiting time drops below 12 hours), signaling that it is safe to resume standard routing.
Why it matters
Manually checking terminal congestion across multiple ports is time-consuming and easy to miss. Notifications shift you from a monitoring posture to an alert-driven workflow, you only need to act when conditions cross a threshold you've defined. Combined with relaxation alerts, you get a complete signal: when to divert or slow-steam, and when it is safe to resume standard routing.
Frequently Asked Questions
How often are the operational incidents updated?
How often are the operational incidents updated?
MarineTraffic checks for new data every 3 hours. However, the "Last Updated" timestamp on an incident reflects when the information was last verified or edited by the original source.
Do these incidents affect the Predictive ETA shown in the app?
Do these incidents affect the Predictive ETA shown in the app?
Currently, incidents are provided for context and visibility only. They are not yet incorporated into the machine-learning models that calculate vessel ETAs.
What is the difference between "Live Waiting Average" and the historical average?
What is the difference between "Live Waiting Average" and the historical average?
The historical average (last 7 days) looks at past performance. The Live Waiting Average calculates the current wait time for vessels presently in the queue, giving you a real-time snapshot of terminal congestion.
Can I set notifications for multiple terminals at once?
Can I set notifications for multiple terminals at once?
Yes. You can combine an unlimited number of terminals or even entire ports into a single notification rule. For example, you can create one alert for all terminals in Shanghai and another for a specific terminal in Ningbo.
How do I know if an incident is still "Live"?
How do I know if an incident is still "Live"?
Incidents are labeled as Ongoing until they are resolved. Once an incident is over, it is removed from the live display on the web application.
What types of events are classified as "Incidents"?
What types of events are classified as "Incidents"?
We focus on operational disruptions, including strikes, port-specific holidays, weather events (like storms or fog), and geopolitical conflicts that physically hamper terminal activity.
Is there an extra fee for using these new notification features?
Is there an extra fee for using these new notification features?
No. Container Intelligence operates on a fixed annual subscription model. This provides unlimited global access to data and notifications without per-container or per-alert fees.
Is there an extra fee for using Incidents?
Is there an extra fee for using Incidents?
Incidents are available live in the web application at no extra cost. For access via API, please contact us, API access is subject to a separate commercial agreement.
What are the steps for setting a new notification for Live Waiting Average?
What are the steps for setting a new notification for Live Waiting Average?
1.Select your terminals or ports. Add individual terminals or group all terminals within a port (e.g., all of Shanghai) into a single rule. There is no limit on how many terminals you can combine.
2. Set your threshold. Define the Live Waiting Average value that triggers the alert (e.g., exceeds 24 hours). This is the condition you want to be notified about.
3. Add a relaxation condition. Set a recovery threshold to be notified when congestion improves (e.g., drops below 12 hours). This signals when it is safe to resume standard routing.
4. Choose your delivery channel. Receive alerts via email, in-app notification, or both.