Somewhere right now a yard is full, a typhoon has closed a terminal, or a carrier has quietly dropped a port from its schedule. When a lane seizes up, knowing about it is not the hard part. The hard part is getting the reroute in front of every origin office before the next shipment books to the port you are trying to avoid.
Checks lets you write one plain-English rule the moment a port goes bad. It reaches every operator at once and checks every booking against it in real time.
Starting at $1 per shipment, live in as little as one day.
48 seconds: one rule, written in plain English, live for every operator.
The routing guide is the theory. The real world is the exception. A strike or a closure hits, and now you send the advisory to every origin office. Some read it. Some do not. So you pull someone off their real job and tell them: for the next two weeks, scan the daily report and find anything headed to that port in the window. It is slow, it is manual, and the one that slips through is always the transshipment leg nobody was looking at.
The reason it is hard is not knowledge. It is speed. Goods move faster than an email reaches 22 origin offices, and far faster than an IT ticket to reconfigure your TMS. By the time the new rule is built, the strike is canceled and you are unwinding it.
The gap between knowing and being able to act is what Checks closes.
A worked example
Say there is an airport strike at Milan from August 10 to 17, and everything destined to Milan in that window has to reroute to Bologna. In Checks you write exactly that. In plain English. No airport codes, no lookup, no ticket.
"There is an airport strike at Milan, Italy from August 10 to August 17. Anything destined to Milan in that window must reroute to Bologna, Italy. Flag any booking that breaks this."
The moment an operator tries to route to Milan in that window, Checks flags it in real time, tells them why, and points them to Bologna. Not two weeks later in a report. As it happens, while the file is still in front of them.
When the strike clears, you hit delete. The rule is gone. Nothing to unwind, no ticket to reverse.
The person who writes the rule is your account manager, not your IT department. So it happens in minutes, not a sprint.
Port status as of August 5, 2026
Write these the way you would say them out loud. Each one names the port and the window inline, so the rule is self-contained.
Jeddah, Saudi Arabia
"Jeddah is congested and some carriers are omitting it or refusing in-transit bookings. Flag any shipment routing through Jeddah, especially in-transit cargo that has to leave Saudi ports within 15 days, so ops can confirm the carrier and routing before we book."
Shanghai and Ningbo, China
"Shanghai and Ningbo are congested after Typhoon Bavi. Flag any booking with origin, transshipment, or discharge at Shanghai or Ningbo so we can confirm routing before it books."
Manila, Philippines
"Manila is running 10 to 12 day delays. Flag any shipment routing through Manila so ops can check the schedule before it books."
Any port, any advisory
"Any shipment booked into a port with an active strike or closure advisory this month should be flagged for a reroute decision before it books."
Which ports are bad changes week to week. The pattern does not. Whatever is congested the month you read this, the rule is the same shape: name the port, name the window, say what should happen instead.
A report tells you what already went wrong. You read it the next day and start apologizing. Checks runs the rule on every shipment as it books, so the wrong booking gets stopped while the file is still open.
A filter in your TMS needs someone to build it. By the time it ships, the strike is canceled and you are unwinding it. A Check is a sentence, so a change is an edit and a rollback is a delete.
The booking that burns you is the transshipment leg nobody scanned for. A rule that names the port catches the whole exposed set, including the legs a human reading a spreadsheet would skip.
The same rule flags at booking and surfaces on the daily view. You are not choosing between fast and thorough, and you change both by editing one sentence.
Checks does not book, classify, or file, and it does not replace your operators or your broker. What it does is make the rule you just wrote live for every operator at once, so the wrong booking gets stopped in real time instead of caught in a report the next day. First line of defense, not a new system to run.
When a port goes bad, you should be able to reach every operator in the time it takes to write a sentence. Starting at $1 per shipment, live in as little as one day.
Every port status on this page comes from a published operational update, not from us. Read them for yourself:
For each specific port named above, the closest primary source is that port authority's own status advisory. Check it alongside these.
Checks flags shipments that may be affected so a person can review them. It is not legal, customs, or routing advice, and it does not replace your broker or carrier. Port status changes fast. Confirm current conditions with the relevant port authority and your carrier before acting. Port conditions on this page are current as of August 5, 2026.
Try Checks with your own spreadsheet. AI finds the issues—you decide what matters.