Japan is thirteen hours ahead of New York in winter and fourteen ahead after the United States springs forward. From Los Angeles the gap is sixteen or seventeen hours. That is not a rounding error you can absorb with a “quick ping.” It is a calendar-date change. The message you send at 20:00 Pacific on Tuesday lands at 13:00 Wednesday in Tokyo — or at 12:00 if you forgot daylight saving on your side.
The humane rule is simple: message Japan during 09:00–18:00 JST unless you already share an on-call rota. Check the live verdict on the Tokyo page before you hit send. If you work with Kansai as well, Osaka uses the same IANA zone and the same no-DST math, with a slightly earlier mental cutoff than Marunouchi.
Why the US clock is the one that moves
Japan has not observed daylight saving in decades. `Asia/Tokyo` stays UTC+9 in January and in July. The United States does move: in 2026, most US zones spring forward on 8 March and fall back on 1 November. For two weeks in March, New York is already on EDT while London is still on GMT — that is a different essay — but for Japan the effect is simpler. After 8 March, New York’s 08:00 is Tokyo’s 21:00, not 22:00. After 1 November it slides back.
If you keep a mental model of “Tokyo is fourteen hours ahead of New York,” you will be wrong for roughly two-thirds of the year. Write the IANA names in the invite (`America/New_York` × `Asia/Tokyo`) and let the calendar do the arithmetic.
East Coast versus West Coast windows
From New York, the overlap with a standard Japanese office day is thin and morning-shaped. 19:00–21:00 Eastern maps to 08:00–10:00 or 09:00–11:00 JST depending on the season. That is a decent slot for a standup if the US side can protect an evening hour. A 09:00 Eastern meeting is 22:00 or 23:00 in Tokyo — a not-now unless someone volunteered for it.
From Los Angeles or San Francisco the picture is almost inverted. Pacific mornings do not reach Japan’s office day at all. Pacific late afternoon and early evening is Japan’s next morning. The San Francisco–Tokyo overlap planner exists because this pair is one of the most common remote-work mistakes: California lunch looks “reasonable,” and it is 05:00 or 06:00 in Tokyo.
A practical cheat sheet for 2026, using 09:00–18:00 JST as the polite window:
- New York winter (EST, UTC−5): ping 19:00–08:00 Eastern for 09:00–18:00 JST. The useful *shared* hour if both people want to be awake is roughly 20:00–21:00 Eastern / 10:00–11:00 JST. - New York summer (EDT, UTC−4): ping 20:00–09:00 Eastern. Shared awake time gets worse, not better. - Los Angeles winter (PST, UTC−8): ping 16:00–01:00 Pacific. Shared awake time is 16:00–18:00 Pacific / 09:00–11:00 JST next day. - Los Angeles summer (PDT, UTC−7): ping 17:00–02:00 Pacific.
Those “until 01:00” ranges are when *they* are working, not when *you* should stay up. Schedule send exists for this. Use it.
After 21:00 JST is a different kind of rude
Japanese office culture still treats late messages as a status event. Overtime exists — Marunouchi lights stay on — but overtime is not consent. A Slack mention at 21:30 JST can feel like a fire alarm even if the unread badge sits until morning. If the work can wait, it should wait. If it cannot wait, say so in the first line: “Production is down. No action needed overnight unless you are on the rota.”
Golden Week in early May, the New Year stretch around 1–3 January, and Obon in mid-August empty inboxes without a US-style out-of-office culture in every company. Do not interpret silence as agreement during those weeks.
How to write the actual message
Put both local times in the first sentence when you propose a call: “Wed 10:00 JST / Tue 21:00 ET.” Link the pair page so nobody has to trust your arithmetic. Keep the ask in one screen. Do not stack follow-ups at 23:00 JST because you are still in your American afternoon.
If you only remember one window from this page: their late morning. For California that means sending in your evening, dated the next day in Japan. For New York that means sending in your evening, dated the next morning in Japan. Check Tokyo first. Then send once.
Field notes from the city desk
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.
Treat Osaka as a place, not a resource pool. Umeda / Nakanoshima keeps 09:00–18:00 as the honest window. Same clock as Tokyo, slightly less formal evenings, still a culture that notices a 22:00 ping. A calendar title that omits Asia/Tokyo is how this city gets pinged in the dark.
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.
Los Angeles (America/Los_Angeles) does not owe you HQ hours. Traffic, not manners, sets the real end of day: a 17:30 ping often lands in a parked car on the 405. Ping inside 09:00–18:00 around Culver City, or schedule send. Presence dots after 18: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.