Sources checked
The ZZZ 3.2 release date was September 9, 2026. This is a historical update date, not a prediction. The official announcement for “Their Secret Histories” gives a maintenance start of 06:00 UTC+8 and an estimated five-hour maintenance period. Its published version-end boundary is October 21, 2026 at 06:00 UTC+8. Treat the maintenance estimate separately from an announcement confirming that servers have reopened. Official Version 3.2 update announcement.
| Milestone | Official date / time | Meaning |
|---|---|---|
| Version 3.2 update | 06:00 UTC+8 | Maintenance start |
| Maintenance duration | About five hours | Official estimate; not an actual completion record |
| Version 3.2 end | 06:00 UTC+8 | Published version boundary |
Release date versus server availability
A release-date search often hides two different questions: when an update was scheduled and when someone could actually enter the game. The announcement answers the first question directly and supplies a duration estimate for maintenance. It does not make the estimate a verified reopening timestamp. This guide therefore records the published start, labels the duration as an estimate, and avoids claiming an observed completion time that its sources do not establish.
If you are documenting when you personally started playing this version, record that separately from the scheduled update. A screenshot taken after login can show that your client was available at that moment, but it does not necessarily establish the first moment of availability for everyone. For a historical timeline, the official maintenance notice provides a consistent reference without requiring assumptions about individual players or platform downloads.
Convert the maintenance start correctly
The following conversions refer to the same maintenance-start instant. They are calculated from the announcement’s fixed UTC+8 timestamp, not separately announced regional release times. Notice that the UTC calendar date is the preceding day. Keeping this distinction in view helps explain why two accurate reports can show different dates. When sharing a time with another player, include the zone name or explicit UTC offset.
| Clock | Maintenance-start equivalent |
|---|---|
| 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 |
Where 3.2 sits in the version sequence
Use this recent-version table to compare update boundaries rather than relying on a remembered interval. Each row links to its own official announcement. The table is deliberately about software versions, so it does not assign a character, event, or channel to every date. A separate schedule should be used when your question is about a banner rather than the patch itself.
| 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 |
Checking banners that ran during 3.2
For channel information, the ZZZ banner schedule separates official phase-overview records from version dates. Start by identifying the phase you want to research, then open the relevant official source. Do not take the version-end boundary in the first table and silently apply it to every channel. Likewise, an event deadline should not be substituted for a Signal Search deadline simply because both appear in one update announcement.
This distinction is useful when you return to an older guide after a patch has ended. A page can remain correct about a release date while no longer describing a currently available channel. Read the version number before using advice about availability. If you are reconstructing your own search history, compare dates with your account records instead of assuming that every result obtained during the patch came from the same banner.
How to use an archived release guide
For a returning player, an archived page should help locate the right official material. Keep a note of the version title, the update date, and the question you are trying to answer. If that question concerns a time-limited activity, follow the activity-specific notice. If it concerns the next update, move to the 3.3 release-date guide rather than extending the old schedule into a new patch.
A historical release date does not guarantee that every past reward, event, or promotion is still available. Before following an old instruction, check whether it describes permanent content or a dated window. This page supplies a timeline and source links; it is not an inventory of everything you can claim today. Keeping that boundary clear prevents an accurate archive from becoming misleading current advice.
Related dates and future claims
The version history gives selected launch milestones and recent update boundaries in one place. The homepage contains a separate countdown. Do not treat a future timer as evidence for the date on this historical page, or use this historical page to validate an unannounced sequel patch. Any future release detail without a checked official announcement remains not officially confirmed.
FAQ
What was the ZZZ 3.2 release date?
September 9, 2026. The official update announcement specifies maintenance starting at 06:00 UTC+8.
When did Version 3.2 end?
The official announcement lists October 21, 2026 at 06:00 UTC+8 as the version-end boundary.
Was the five-hour maintenance duration guaranteed?
No. The announcement describes an estimated duration, which does not independently establish the actual reopening time.
Does this release date determine every 3.2 banner deadline?
No. Individual channel windows must be checked in their own official Signal Search notices.