Sources checked
The ZZZ 3.3 release date was October 21, 2026. HoYoverse’s “Journey to the Sky” update announcement specifies maintenance beginning at 06:00 UTC+8, with a duration estimated at about five hours. The same announcement places the end of Version 3.3 at December 2, 2026 at 06:00 UTC+8. These are published maintenance and version boundaries; they are not interchangeable with the opening or closing time of an individual banner. Official Version 3.3 update announcement.
| Milestone | Official date / time | Status |
|---|---|---|
| Version 3.3 update | 06:00 UTC+8 | Published maintenance start |
| Maintenance duration | About five hours | Estimated duration |
| Version 3.3 end | 06:00 UTC+8 | Published version-end boundary |
| Exact Version 3.4 playable opening | not officially confirmed | Not established by the 3.3 maintenance notice |
What the release-date answer does and does not mean
If you arrived here looking for the day the patch began, the opening date above is the direct answer. If you need the moment maintenance finished, a scheduled start plus an estimated duration is not the same kind of evidence. Adding five hours produces a planning estimate, not a verified historical completion record. Keep that distinction whenever you compare this guide with a video upload, a login screenshot, or an older countdown.
For someone reading during the patch, the useful next step depends on the task. A player checking a channel should open that channel’s notice. A player updating a client should follow the instructions for their platform. Someone archiving announcements should save the version number and source title together with the timestamp. These questions share a version label but do not all have the same deadline or availability rule.
Regional maintenance-start conversions
The regional entries below are arithmetic conversions of the official timestamp. They are not separate regional maintenance announcements or promises about when a download finishes. Daylight-saving offsets are shown for this particular date; do not reuse them automatically for December or for a different year. A location’s civil clock and a game notice’s server-time label should not be assumed to mean the same thing.
| Clock | Same maintenance-start instant |
|---|---|
| UTC+8 (official) | 06:00 |
| UTC | 22:00 |
| America/New_York (UTC−4 on this date) | 18:00 |
| Europe/Berlin (UTC+2 on this date) | 00:00 |
Compare the preceding versions
The recent-version table gives context for the change from the preceding patch. Read dates from the announcements rather than filling a spreadsheet by repeating an assumed interval. That approach keeps the record useful even when a future schedule changes. The 3.2 release-date page expands the previous row, while the history page provides the broader selected timeline.
| Version | Update date | Maintenance starts (UTC+8) | Source |
|---|---|---|---|
| 3.1 | 06:00 | Official Version 3.1 update announcement | |
| 3.2 | 06:00 | Official Version 3.2 update announcement | |
| 3.3 | 06:00 | Official Version 3.3 update announcement |
Banners within Version 3.3
The Official Version 3.3 Phase I overview identifies Phoenix and Velina in Phase I. For a channel’s complete availability period, use its official details rather than the patch-end timestamp. Our banner schedule guide keeps the confirmed lineup records separate from the update calendar. This separation matters when a player is deciding whether a specific channel is still open rather than asking which software version is currently installed.
When reading an overview graphic, check the caption attached to each date range. A range associated with an outfit, login event, or other activity should stay with that activity in your notes. It should not be copied into a banner table without an explicit connection. If the exact timestamp you need is not available in the source you have checked, leave that field unresolved and open the matching notice.
The December boundary and the next update
The end of one version is useful information, but it does not independently confirm every detail of the next release. For example, a published maintenance boundary does not establish the exact playable opening after maintenance, the next channel’s final lineup, or the availability of every previewed feature. This page does not convert the December boundary into a guaranteed Version 3.4 opening hour. Unverified future details remain not officially confirmed.
If you use the homepage countdown, read its labels as well as its numbers. For a firm deadline, the relevant official announcement should be the reference you save. A countdown can help visualize remaining time, but it cannot resolve a missing timezone, establish that maintenance has finished, or replace a notice that later changes. Keep a direct link to the source alongside any reminder you create.
FAQ
What was the ZZZ 3.3 release date?
October 21, 2026. The official announcement gives a maintenance start of 06:00 UTC+8.
When is the official Version 3.3 end boundary?
December 2, 2026 at 06:00 UTC+8, according to the Version 3.3 update announcement.
Does the 3.3 end boundary guarantee the exact 3.4 opening time?
No. The exact playable opening of Version 3.4 is not officially confirmed by that boundary alone.
Where should I check a 3.3 banner deadline?
Read the individual official Signal Search notice and its timezone or server-time label.