Public holidays, market closures and deadlines for 240 jurisdictions — every date carrying its evidence, its precision, and the day we last checked.
Engine updates continuously · — PDF reports update monthly · latest —
Worked answers, computed from the corpus rather than looked up.
Most calendars hand you a date. This one hands you the date, what stands behind it, and how sure we are.
A rule holds for years we have never published, and changes when the rule changes — not when someone remembers to update a spreadsheet.
Where a date is an estimate — a lunisolar rule awaiting a moon-sighting decree — we return it as an estimate rather than a confident wrong answer.
REST access across jurisdictions, exchanges and calendar systems, with assurance filters and inheritance — a subdivision falls back to its national rule unless it overrides it.
PDF dossiers for operations, finance and HR — delivered with CSV and ICS appendices and a provenance section, so a person can act on them without touching an API.
Nine places where a date is not admin — it is the decision.
A regional holiday pays one state late.
Different closures. Confusing them moves money late.
Customs winds down before the holiday, not during.
Some jurisdictions roll forward, some back.
The same date carries several kinds of fact, and they are not the same kind of claim. We keep them in separate layers and label each one, so a statistical estimate can never be mistaken for a gazette.
A government published it. Carries provenance and an assurance label.
Arithmetic, not authority. Exact or estimate — never "verified", because there is nobody to verify it against.
A distribution over history. Says nothing about a specific future date, which is exactly why it is honest.
Dated like the first layer, and sourced the same way. Not yet shipped, so not yet sold.
Items in grey are being built and are not part of any plan until they ship.
The dates are computed from 36 calendar systems — lunar, lunisolar, solar and astronomical.