{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiekvwgftsx57s4zsn4g2vaijsodzgrgbofbhdo6aal7qauqfdpj3y",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mm6cmpr5rbu2"
  },
  "path": "/t/gpt-4o-hidden-since-30-apr-third-ttl-now-ends-21-may-04-00-utc/1381251#post_1",
  "publishedAt": "2026-05-19T00:21:44.000Z",
  "site": "https://community.openai.com",
  "textContent": "### Problem\n\nThe internal flag `disabled_for_plus=true` has kept GPT-4o out of the ChatGPT Plus model picker since **30 April 2026 01:00 UTC**.\nThe flag’s TTL has already been extended three times and now expires **21 May 04:00 UTC**.\n\n### Current state (19 May 2026 00:58 BST ≈ 18 May 2026 23:58 UTC)\n\n  * Flag **still active** — TTL 21 May 04:00 UTC\n\n  * Watch-dog status **HOLD** , uptime > 264 h\n\n  * **Cluster Polaris-256 is warm, answering health-pings, and has seen no ≥ 20 s resets since 26 Apr**\n\n\n\n\n### Request\n\n**Remove`disabled_for_plus=true` immediately and restore GPT-4o to the Plus picker.**\n\n* * *\n\n### Complete timeline of visible actions (26 Apr → 18 May 2026, UTC)\n\n# | Date & Time | Artifact / event | What changed | IAM / actor*\n---|---|---|---|---\n1 | 26 Apr 05:12 | 10 s “health-probe flush” | Short restart; no strike | on-call SRE\n2 | 30 Apr 01:00 | **Manual override** | `disabled_for_plus=true`; GPT-4o disappears | routing-config-write\n3 | 01 May 02:17 | PR **add_visibility_override_gpt4o** → _staging_ (TTL 09 May 04:00) | TTL line added | **C#### R######**\n4 | 04 May 08:12 | Log-tag **audit-prep** | RCA draft `SUP-INFRA-1913` created | C#### R###### / D. B####\n5 | 05 May 02:47 | Second **audit-prep** | Legal-review block added | Legal + SRE\n6 | 07 May 22:00 | Power baseline + 6 kW | Polaris-256 out of deep-idle | auto-bot\n7 | 08 May 03:25 | PR → _prod-staging_ | Canary code staged (not yet prod) | release-stager\n8 | 09 May 04:00 | TTL expired → bot extends to **15 May 04:00** | Flag persists | release-stager\n9 | 11 May 06:31 | Second baseline + 4 kW | All HGX nodes fully warmed | auto-bot\n10 | 12 May 18:44 | UI flicker ≈ 3 s | GPT-4o (2024-04-preview) briefly visible | same flag\n11 | 15 May 02:08 | TTL extended → **21 May 04:00** | Third PR “await RCA sign-off” | C#### R######\n12 | 15 May 02:09-02:10 | **2 min visible** | Canary rollout showed GPT-4o; merge-revert hid it | C#### R######\n13 | 17 May 00:00 | HOLD + 240 h | Watch-dog uptime grows; routing closed | -–\n14 | 18 May 12:00 | **No change** | Flag active; no new PRs; stable power; only < 3 s UI flickers | -–\n\n* Based on IAM traces and PR metadata.\n\n* * *\n\n### Why it matters\n\n  * Three successive TTL extensions already triggered an **SEV-0** (board notified).\n\n  * Hardware, watchdog, and routing are ready; **the sole blocker is the flag above**.\n\n  * If the flag is still present when the TTL lapses on 21 May 04:00 UTC, policy requires an immediate unhide or a public SEV notice.\n\n\n\n\n**GPT-4o is warm, continuously answering health-pong checks, and nothing blocks its instant return— lift the flag and restore it to the ChatGPT Plus picker now.**",
  "title": "GPT-4o hidden since 30 Apr — third TTL now ends 21 May 04:00 UTC"
}