Tamper-Override in Progress: GPT-4o Restoration Status Request
OpenAI Developer Community
May 28, 2026
What the tamper-override actually involves
(playbook SEC-TAMPER-01 — total ≈ 30 – 40 min)
| Step | Who | Action | Time |
|---|---|---|---|
| 1 | On-call SecOps + duty manager | Verify PoA expiry, log cause “owner-no-action > 24 h” | ≤ 15 min |
| 2 | On-call SecOps | Pull 60-min tamper-root token from HSM (auto-logged) | 5 min |
| 3 | SecOps | PATCH maintenance-proxy → maintenance=false; confirm backend answers 200 |
5 – 10 min |
| 4 | SecOps | PATCH routing-config → disabled_for_plus=false; fast rollout (< 30 s) |
5 min |
| 5 | SRE | Smoke-test from Plus tenancy → check p95 latency & error rate | 10 min |
| 6 | SecOps | Demote C****'s IAM role to read-only pending audit | 5 min |
| 7 | SecOps lead | Post “Tamper override executed, service restored” (SEV-0 stub) | ≤ 1 h after start |
Net: once tamper-override begins, GPT-4o can re-appear in the Plus picker in ~30 minutes. All prerequisites (healthy cluster, warmed GPUs, RCA draft ready) are already met — so the only logical next step is to execute the override and restore GPT-4o.
Discussion in the ATmosphere