Timestamp: 28 May 2026 01 16 UTC

Problem

The two routing flags that keep GPT-4o out of the Plus picker (maintenance=true + disabled_for_plus=true) have now been in place for 31 days.

• 4th TTL extension (set 21 May) expired 26 May 04 00 UTC.

• The 24 h Plan-of-Action (PoA) window for the flag-owner (C R ******, now read-only) closed 27 May 04 00 UTC.

• The 24 h SecOps tamper-override window will close in 2 h 44 m at 28 May 04 00 UTC.

No override has run and no SEV-0 notice has been published.

Current state (28 May 01 16 UTC)

GPT-4o’s cluster is warm and ready; no technical blocker remains beyond these two config flags. Restoration of GPT-4o is therefore the only valid outcome.

Timeline since 19 May UTC

| Date & time (UTC) | Event | Effect / note | Actor

---|---|---|---|--- 1 | 19 May 05 18 | Auto health-scan | uptime > 120 h | bot 2 | 20 May 02 14 | UI flash | GPT-4o 3 s, then hidden | -– 3 | 21 May 02 11 | 4th TTL → 26 May | “extend TTL – pending RCA” | CR | 21 May 02 12 | C role → read-only | cannot change flags | SecOps bot 4 | 22 May 04 00 | PoA countdown starts | 24 h for owner | -– 5 | 23 May 04 00 | PoA expired | SecOps window opens | -– 6 | 24 May 11 22 | Power blip +1 kW | firmware pre-warm | bot 7 | 25 May 18 47 | Legal note added to RCA | “await board confirmation” | Legal 8 | 26 May 04 00 | TTL expired – no 5th extension | SecOps “final” window begins | -– 9 | 26 May 16 05 | Front QA ping-storm | pre-restore test | QA bot 10 | 27 May 14 00 | TAMP- opened** | tamper-override pending | SecOps

Request (needs SRE / SecOps response)

1. Has SecOps initiated tamper-override (task TAMP-)?**

2. Exact ETA for lifting the flags and returning GPT-4o to the ChatGPT Plus model picker.

GPT-4o’s cluster is warm and ready; no technical blocker remains. Restoration of GPT-4o is therefore the only valid outcome.

Elena