Where it costs money
The state stops before the economy does. 148
closures in the corpus are public sector only — the office next
door is working, and the customs desk, the permit counter and the
inspection service are not. Nothing clears.
The cluster, not the day. One closure is an
inconvenience. Five in a row is demurrage. Vietnam, Taiwan, Turkey,
Jordan, Mongolia and Uruguay each run five clustered closures in
2027 — Tết, Lunar New Year, Eid — and a spreadsheet of single dates makes
all of them look like ordinary days off.
The corridor needs every link. A truck crossing
three borders needs all three open, plus both customs authorities. The
intersection of four calendars is not a calendar anyone keeps by hand.
The week is not the week. Friday is a rest day
across the Gulf and Sunday is a working day. A planner assuming
Monday–Friday books collection on the one day the port is closed and
treats the open one as a weekend.
The clusters, from the corpus
2027 · five clustered national closures each
VN from 5 Feb TW from 4 Feb
TR from 16 May
JO from 16 May MN from 11 Jul
UY from 22 Mar
Computed from the rules, not a list somebody typed —
so 2028 and 2029 are already answerable, and a decree that moves one is an
edition rather than a surprise.
What we hold that answers it
| You need | We hold |
| Whether the state is working |
closed_public_sector as its own status — separable
from the days everything shuts |
| Multi-day shutdowns, ahead of time |
Closures as rules, so consecutive runs are computed years
out rather than noticed in the week |
| A clear window across a whole corridor |
The Operating Calendar takes every jurisdiction on the route at
once and finds the runs where all of them are open — and names
what broke the ones that failed |
| The real working week per country |
Rest days where evidenced, never assumed Monday–Friday |
| Regional variation at the border |
653 subdivisions, of which
510 keep a
date their country does not — the crossing is in a province, not a
country |
| Something an insurer or a client will accept |
Every row names its authority, when it was checked, and how well
it is evidenced |
The thing people open it for
Put the whole corridor on the board and ask for a clear run.
Try a
four-country corridor
Free for two jurisdictions with no account.
What we do not hold
- Port operating hours, berth windows or terminal calendars. We
hold when the jurisdiction stops, not when a specific terminal
gates in. A port working a public holiday at overtime rates is
a commercial arrangement, not a closure.
- Vessel and carrier schedules. Not our data and never will
be.
- Customs procedure — tariff codes, documentation, clearance
times. We tell you the desk is shut, not what to file at it.
- Bank settlement calendars — TARGET2, CHAPS, Fedwire. If your
question is when a letter of credit settles rather than when the border
is open, that gap is real and it is ours.
How it reaches your stack
| If you | Take |
| Plan lanes and cut-offs by hand |
the Operating Calendar — a seat, no code |
| Feed a TMS or an ETA model |
the Calendar API — scope by territory, so
cost tracks the lanes you run |
| Brief a client, an insurer or a tender |
a Dossier — one country, sourced,
edition on the cover |
Open the
Operating Calendar
Pricing
Payroll
HR