News

DeepSeek's clock is a Beijing clock: the same working day costs 75% more there than in San Francisco

DeepSeek's price list, in force since 16 August 2026, is the first from a major model provider in which the hour of the day is a full pricing variable rather than a promotion: peak hours are 01:00–04:00 and 06:00–10:00 UTC, and everything outside them costs exactly half. The published windows say nothing about where those hours fall. Converted, they say a great deal. Beijing keeps UTC+8 all year, with no daylight saving. The two peak windows land at 09:00–12:00 and 14:00–18:00 local time — Chinese office hours. The gap between them, 04:00–06:00 UTC, is 12:00–14:00 in Beijing: the lunch break, priced at half rate. The tariff is not described in geographic terms anywhere in the documentation, but it is drawn around one country's working day. That has an arithmetic consequence nobody has published. Take a team using DeepSeek-V4-Pro evenly through a 09:00–17:00 local working day, and price a million output tokens ($3.96 at peak, $1.98 off-peak). In San Francisco the local working day is 16:00–24:00 UTC and misses both peak windows entirely, so every hour bills at $1.98. In Warsaw it is 07:00–15:00 UTC, of which three hours are peak: $2.72 per million, 37.5% above San Francisco. In Beijing it is 01:00–09:00 UTC, of which six hours are peak: $3.47 per million — 75% above San Francisco, for identical work on identical weights. Bangalore lands in between at $3.09, or 56% above. European bills also move with the clock change. In winter Warsaw shifts to UTC+1, only two working hours stay inside the peak, and the same million falls to $2.48 — a 9% discount granted by nothing but the end of daylight saving. What this does not show: DeepSeek is not charging anyone by location. The tariff is identical worldwide and time-based, and the company presents it as load management — the peak windows are simply when its servers are busiest, which is when its home market is at work. Batch and overnight jobs can be moved into the cheap hours by anyone, anywhere, and for most production workloads cached input, billed at a fiftieth of a cache miss, matters far more than the clock. The figures above assume usage spread evenly across office hours, which no real team does exactly. But the direction is not an artefact: the further a user's working day sits from Beijing's, the less DeepSeek's price rise costs them.