Zenless Zone Zero 3.3
ZZZ 3.3 release time in every time zone
One official clock, one estimate. Maintenance starts 2026/10/21 06:00 (UTC+8)and the notice says it “will take five hours”, which puts the estimated go-live at11:00 (UTC+8).
Maintenance starts
21 Oct 2026, 06:00 (UTC+8)
Estimated go-live
21 Oct 2026, 11:00 (UTC+8)
Official wording
“2026/10/21 06:00 (UTC+8) : We estimate this will take five hours.”
One instant, many clocks
The same moment, everywhere
Maintenance start and estimated go-live in 14 time zones
Offsets are the ones in force on the launch date: the US is still on daylight saving time and Europe is on summer time, which is exactly where fixed-offset tables go wrong.
| Time zone | In force | Maintenance starts | Estimated go-live | Offset vs UTC+8 |
|---|---|---|---|---|
| Los AngelesAmerica/Los_Angeles | GMT-7 | -7 h vs UTC | ||
| DenverAmerica/Denver | GMT-6 | -6 h vs UTC | ||
| ChicagoAmerica/Chicago | GMT-5 | -5 h vs UTC | ||
| New YorkAmerica/New_York | GMT-4 | -4 h vs UTC | ||
| UTC / London (winter)UTC | UTC | same as UTC+8 | ||
| LondonEurope/London | BST | +1 h vs UTC | ||
| Berlin / Paris / RomeEurope/Berlin | CEST | +2 h vs UTC | ||
| Athens / HelsinkiEurope/Athens | EEST | +3 h vs UTC | ||
| MoscowEurope/Moscow | GMT+3 | +3 h vs UTC | ||
| Mumbai / New DelhiAsia/Kolkata | GMT+5:30 | +5.5 h vs UTC | ||
| Bangkok / JakartaAsia/Bangkok | GMT+7 | +7 h vs UTC | ||
| Shanghai / Beijing / SingaporeAsia/Shanghai | GMT+8 | +8 h vs UTC | ||
| Tokyo / SeoulAsia/Tokyo | GMT+9 | +9 h vs UTC | ||
| Sydney / MelbourneAustralia/Sydney | GMT+11 | +11 h vs UTC |
The server clock is UTC+8 in every row: “server time” in an official ZZZ notice means the same thing as “(UTC+8)”.
Why some sites say October 20 and others say October 21
HoYoverse
Lists the update as October 21, because that is the date on the UTC+8 server clock.
US-facing sites
Often print October 20, because 2026-10-20 23:00 EDT is the same instant as 2026-10-21 11:00 UTC+8.
Two events, not one
Maintenance starts at 06:00 (UTC+8) and the servers return about five hours later. A page that prints one “launch time” for both is wrong on one of them.
Time zone mistakes we checked and corrected
Seen elsewhere
“America runs on UTC-5 … 13 real hours apart”
On the 3.3 launch date the US was on EDT (UTC-4) and PDT (UTC-7), so the difference from UTC+8 is 12 hours, not 13 — and one offset covers two different local times.
Seen elsewhere
“ET (UTC-5)” rows, with several cells left empty
One Chinese launch-time table labels Eastern Time as UTC-5 in October, when the US is on UTC-4, and leaves the Eastern end-of-version row blank. This table is complete and states which offset is in force.
FAQ
Release time FAQ
Time zone questions that come up on every version launch.
Which time zone does HoYoverse use?
All official ZZZ notices are written in UTC+8, the same clock the game servers run on. "Server time" therefore means UTC+8.
Why is the launch shown as both October 20 and October 21?
The official date is October 21 on the UTC+8 server clock. In North America the same moment is October 20 at 23:00 EDT, which is why several English sites print October 20.
Does daylight saving time change the answer?
Not during Version 3.3. The US leaves daylight saving time in early November and the EU in late October, so the Phase II window in November shifts again.
Why does the maintenance start time differ from the go-live time?
The server is closed from 06:00 (UTC+8) while the update is installed. The estimated go-live time adds the "about five hours" that HoYoverse quotes for the maintenance itself.
The clock you
actually need
Four timers on one page: the version launch, the Phase I switch, the Phase II switch and the end of 3.3.