Status
Do not call it fixed without a version
A status page can mark an incident resolved and still omit the timezone and the client version.
OpenAI's status page for the Codex and Work mode degradation lists 6:21 p.m. on Wednesday, October 7, 2026 as investigating, and 7:23 p.m. the same day as resolved. The page does not state a timezone. It does not name a client version that received a fix.
Resolved on that page means the vendor closed the incident. It does not tell you which build you are running.
Copy the clock lines first
Write investigating at 6:21 p.m. and resolved at 7:23 p.m., both dated October 7, 2026. On the next line write Timezone not stated. Leaving the zone blank lets a reader assume their own.
An hour of clock time is the duration the page supports. Do not convert it into a region.
Ask for the client version before you announce a fix
If the status page names no version, your note says Version not stated. A person on an older install can still be in the bad state after the incident is closed.
The fallback is the product's own check: version screen, then the status page, in that order. Do not skip the version because the banner turned green.
Tell the user only the supported sentence
A fair sentence is: the vendor marked this incident resolved at 7:23 p.m. on October 7, 2026, with no timezone and no client version on the page.
It is fixed now is a larger claim. It needs a version and a clock with a zone.
Related guides
Primary references
Useful Tomorrow home · All guides and studies · Awesome Patel’s publication profile