Do not ping someone on their public holiday. This should not require an article. It requires one because global Slack made it possible to forget that Tokyo is closed while New York is writing Jira tickets, and that London is on a bank holiday while California is in a sprint review.
Asleep flips a city to MAYBE or NOT NOW on Public and Bank holidays. That is the point of `holidays.json`. This essay is what to do with the feeling that “it’s just a ping.”
Holidays are not synchronized
In 2026, 1 January is widely closed and still a bad day to demand a reply. After that, the calendars diverge hard:
- United States: MLK Day, Presidents Day, Memorial Day, Juneteenth, Independence Day (observed 3 July 2026 in the feed), Labor Day, Veterans Day, Thanksgiving. - United Kingdom: Early May, Spring, and Summer bank holidays, plus Scotland’s 2 January and extra local days. A Monday that is ordinary in Manhattan is closed in Manchester. - Japan: Coming of Age Day, Foundation Day, the Emperor’s Birthday, Vernal Equinox, Shōwa Day, Golden Week cluster, Marine Day, Mountain Day, Respect for the Aged, Autumnal Equinox, Sports Day, Culture Day, Labour Thanksgiving. - Australia: Australia Day, ANZAC Day, plus state-level days that empty Sydney without emptying Perth the same way.
Good Friday 3 April 2026 is public in Britain and parts of the US, and a normal-ish US federal workday in other states. If you ping a global channel “need this today” on Good Friday, you have announced that you do not know who is in the channel.
What silence means
Silence on a holiday is not passive aggression. It is the point of the holiday. Escalating at 14:00 your time because you have not seen a read receipt is how you become the overseas villain in a group chat you will never be invited to.
If the work cannot wait, page the on-call, not the person whose city is dark on the holiday map. If there is no on-call, the work can wait. That sentence is uncomfortable for a reason.
How to schedule around the 2026 clusters
Golden Week in Japan (late April into early May) is a multi-day mute. Chinese New Year dates empty East and Southeast Asia on a lunar calendar — do not use a solar “February-ish” guess. US Thanksgiving week kills Thursday and often Friday. Europe in August is not a holiday so much as a seasonal evaporation, especially in Paris and Rome.
When you must book across a holiday, book the *next* overlapping workday and say why in the invite: “Skipping Fri 3 Apr (Good Friday UK).” The New York–London overlap is useless on a day London is off.
A channel convention that works
Set a bot or a pinned doc: “If the city page says holiday, we wait.” Require IANA city names in profiles. Teach people to look at Tokyo before they @ the Tokyo person. Do not celebrate “hustle” that is just timezone abuse dressed as commitment.
Your Tuesday is someone else’s National Foundation Day. The kind version of urgency is a scheduled message on the next local work morning. The unkind version is the badge on the picnic blanket. Do not send the unkind version.
How to staff coverage without fake urgency
If the business must run on a holiday, publish a volunteer rota with extra pay or time in lieu. Do not "see who answers." People who answer are not more committed; they are more trapped.
For launches, pick a week that is boring in every required city. That sounds obvious and is how you avoid shipping on Golden Week plus a UK bank holiday plus US Memorial Day because someone aligned the GitHub milestone to a sprint number.
For support, follow-the-sun only works if each region's holiday is covered by another region's ordinary Tuesday. Map 2026's collisions: 25 May is both UK Spring bank and US Memorial Day — a bad day to assume "someone in English-speaking HQ is in." Sydney may be the adult in the room that Monday. Ask them first, do not dump.
Add the holiday flag to your status page or embed. A customer who sees NOT NOW on Tokyo will wait. A customer who sees a green Slack dot will not.
Field notes from the city desk
Treat New York as a place, not a resource pool. FiDi keeps 09:00–18:00 as the honest window. Slack after 19:00 is usually parked until the morning subway ride. A calendar title that omits America/New_York is how this city gets pinged in the dark.
Treat London as a place, not a resource pool. the City / Shoreditch keeps 09:00–18:00 as the honest window. Sorry-culture is real: a 19:00 Slack gets a next-morning reply and a faint wince. A calendar title that omits Europe/London is how this city gets pinged in the dark.
In Tokyo, start from Marunouchi. Nine-to-six on paper, later in practice. After 21:00 a Slack ping can feel like a fire alarm; Golden Week is a blackout. The local prior remains 09:00–18:00 (Asia/Tokyo). If this article's advice conflicts with that desk, the desk wins — ask once and write it down.
Sydney (Australia/Sydney) does not owe you HQ hours. AEDT in summer, AEST in winter. US calls eat breakfast or dinner — never lunch. After 18:00 a ping is tomorrow. Ping inside 09:00–17:00 around the CBD / Barangaroo, or schedule send. Presence dots after 17:00 are scenery.
None of these notes replace the live verdict. Open the city page at send time. Clocks and holidays move; this paragraph does not.