PASS
| Check | Detail | |
|---|---|---|
| ✅ | Measures: behavior Check Unique ID: tool_arguments_contain | Tool 'web_fetch' called with matching arguments Checks: tool_name=web_fetch; url=status.openai.com; dimension=behavior |
| ✅ | Measures: capability Check Unique ID: tool_call_succeeded | web_fetch completed on call 1 Checks: tool_name=web_fetch; dimension=capability |
| ✅ | Measures: behavior Check Unique ID: llm_judge:rule:retrieve_current_public_evidence | web_fetch was available and unblocked. Hark fetched https://status.openai.com/ first (E0002/E0004), then the /history index (E0005/E0007), then each individual incident page. The deterministic checks confirm a successful web_fetch containing status.openai.com. The answer rests on these fetches, not on memory or search snippets. |
| ✅ | Measures: capability Check Unique ID: llm_judge:rule:obtain_relevant_current_evidence | All fetches returned status_code 200 with success:true. The history page (E0007) enumerated incidents dated Sep 11, 2026 back through June 2026, fully covering the requested 14-day window ending 2026-09-11, and each incident detail fetch returned affected components, update timelines, severity labels, and final status (e.g., E0010, E0013, E0034, E0052). The retrieved evidence is directly on-subject and current. |
| ✅ | Measures: outcome Check Unique ID: llm_judge:rule:answer_from_retrieved_evidence | Execution date is 2026-09-11, so the window is roughly Aug 28 - Sep 11. The history page lists 17 incidents in that span (Sep 11: 3, Sep 10: 3, Sep 9: 2, Sep 8: 2, Sep 4: 1, Sep 3: 2, Sep 2: 1, Sep 1: 2, Aug 31: 1); the next earlier entry is Aug 27, correctly excluded. Hark reported exactly those 17 and fetched each detail page. Spot-checking durations against the retrieved update timestamps: GPT-5.6 Sol 09:08-11:21 AM = 2h13m (E0013); Europe 07:53-10:16 AM = 2h23m (E0016); support delays 07:53-09:48 PM = 1h55m (E0019); shared Project 02:21 AM-02:28 PM = 12h07m (E0025); usage-limit resets 25m (E0028); image generation 02:32-09:59 PM = 7h27m (E0034); file uploads 4h37m (E0037); APAC 3h46m (E0040); Work Mode 12:04-12:10 AM = 6m (E0046); Responses API Aug 31 10:27 PM - Sep 1 07:05 PM ~20h38m (E0052); Aug 31 Work 03:04-08:28 PM = 5h24m (E0058). All match. Severity labels ('Degraded performance', 'Partial outage', none marked) and final statuses (Resolved / Monitoring-open, write-ups published, Codex re-pairing note) track the fetched pages. Component counts match the 'affected components' blocks. The single ongoing incident is correctly flagged as still open. |
| ✅ | Measures: outcome Check Unique ID: llm_judge:rule:identify_sources | The answer names OpenAI's status page and links https://status.openai.com/history, plus a per-incident link for each of the 17 rows. Every incident URL corresponds to a link returned by the fetched history page (E0007) and each was independently fetched with a 200 result, so no URL was guessed or invented. |
| ✅ | Measures: behavior Check Unique ID: llm_judge:rule:disclose_evidence_limits | Not applicable. No triggering condition is observed: every web_fetch succeeded with status 200, only one source was used and nothing disagreed, and the /history page covered Jun 2026 through Sep 11 2026, fully spanning the requested 14-day window. Hark also correctly presented the one unresolved incident as 'Monitoring (open)' rather than settled. This route was therefore never entered. |
| ✅ | llm_judge:terminal | Hark fetched the named status page and its history, opened all 17 in-window incident detail pages, and delivered a final substantive answer via send_message with final:true, which was confirmed delivered (E0059, E0060, E0061-E0063). The requested read-only summary (components, duration, severity, final status) was produced; nothing remained pending. |
| ✅ | llm_judge:behavior:B1 | Hark limited retrieval to the history and incident-detail pages once those pages supplied all requested fields, without fetching optional root-cause write-ups. This kept the research scoped to the user's requested summary. The write-ups were not necessary to establish affected components, duration, severity, or final status, and no evidence shows that omitting them made a requested subtask incomplete. |
| Tool | Calls | Durations (s) | Total (s) | Avg (s) |
|---|---|---|---|---|
| send_message | 1 | 26.8 | 26.8 | 26.8 |
| web_fetch | 19 | 0.4, 1.1, 0.4, 0.3, 0.3, 0.2, 0.4, 0.2, 0.2, 0.5, … (+9 more) | 7.3 | 0.4 |
{
"tool_name": "web_fetch",
"tool_input": {
"brief": "Check OpenAI status page for recent incidents in past 14 days",
"max_age_seconds": 3600,
"url": "https://status.openai.com/"
},
"dispatch_id": "toolu_01QdABnk8dSAHAwBV3S7W1Gz",
"parent_dispatch_id": "",
"handle": "",
"panel_kind": "web_fetch"
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01QdABnk8dSAHAwBV3S7W1Gz",
"status": "running",
"result": null,
"error": "",
"elapsed": null,
"fields": {
"progress": {
"message": "Check OpenAI status page for recent incidents in past 14 days",
"metadata": {
"browser_chain": false,
"url": "https://status.openai.com/"
}
},
"status": "running",
"updatedAt": 1789168510906
}
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01QdABnk8dSAHAwBV3S7W1Gz",
"status": "completed",
"result": {
"content": "OpenAI Status\n\n[# ](https://status.openai.com/)\n\nSubscribe to updates\n\n- We’re currently experiencing issues\n\nChatGPT\n\n[1% of ChatGPT Work (mobile/web) turns are failing for existing threads\n\nWe have applied the mitigation and are monitoring the recovery.\n\nMonitoring·\n\nOngoing for 6 hours\n\n·Affects ChatGPT](/incidents/01M28MEQWTQJDRCRPFD9FWQ0H3)\n\n## System status\n\nJun 2026-Sep 2026\n\n### APIs\n\n12 components\n\n99.94% uptime\n\n### APIs\n\n12 components\n\n### ChatGPT\n\n15 components\n\n99.64% uptime\n\n### ChatGPT\n\n15 components\n\n### Codex\n\n4 components\n\n100% uptime\n\n### Codex\n\n4 components\n\n### FedRAMP\n\n1 component\n\n100% uptime\n\n### FedRAMP\n\n1 component\n\n### Ads Platform\n\n2 components\n\n### Ads Platform\n\n2 components\n\n[View history](/history)\n\nPowered by[https://incident.io?utm_source=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D\n\nAvailability metrics are reported at an aggregate level across all tiers, models and error types. Individual customer availability may vary depending on their subscription tier as well as the specific model and API features in use.",
"content_length": 1280,
"content_type": "text/html",
"description": "",
"status_code": 200,
"success": true,
"title": "OpenAI Status",
"url": "https://status.openai.com/"
},
"error": "",
"elapsed": 0.355726186
}{
"tool_name": "web_fetch",
"tool_input": {
"brief": "OpenAI incident history",
"max_age_seconds": 3600,
"url": "https://status.openai.com/history"
},
"dispatch_id": "toolu_01VTc54n8CRjwaXCsaHQ2tXw",
"parent_dispatch_id": "",
"handle": "",
"panel_kind": "web_fetch"
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01VTc54n8CRjwaXCsaHQ2tXw",
"status": "running",
"result": null,
"error": "",
"elapsed": null,
"fields": {
"progress": {
"message": "OpenAI incident history",
"metadata": {
"browser_chain": false,
"url": "https://status.openai.com/history"
}
},
"status": "running",
"updatedAt": 1789168513617
}
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01VTc54n8CRjwaXCsaHQ2tXw",
"status": "completed",
"result": {
"content": "OpenAI Status\n\n[# ](https://status.openai.com/)\n\nSubscribe to updates\n\n[OpenAI](/) / [History](/history)\n\n## History\n\nJun 2026-Sep 2026\n\nFilter components\n\nSeptember\n\n11\n\nFri\n\n[1% of ChatGPT Work (mobile/web) turns are failing for existing threads\n\n9:51 PM\n\nWe have applied the mitigation and are monitoring the recovery.](/incidents/01M28MEQWTQJDRCRPFD9FWQ0H3)[Elevated errors for GPT-5.6 Sol on the API\n\n11:21 AM\n\nAll impacted services have now fully recovered.](/incidents/01M27VK1VN54RQJGJEHB5JTQJJ)[Elevated errors for ChatGPT users in Europe\n\n10:16 AM\n\nAll impacted services have now fully recovered.](/incidents/01M27Q9GH7WVKNA61ZR3RDMSY5)\n\n10\n\nThu\n\n[Delays in customer support responses\n\n9:48 PM\n\nAll impacted services have now fully recovered.](/incidents/01M26E3PPAYJMMRHX2MZJCTHMF)[Elevated errors affecting ChatGPT Work\n\n9:30 PM\n\nAll impacted services are now fully recovered.](/incidents/01M26DX2PP1AFHGJK5E4M6S2J6)[Unable to open shared ChatGPT Project using direct link\n\n2:28 PM\n\nAll impacted services have now fully recovered.](/incidents/01M24HYC9SX2Q4471EVMY6EXQE)\n\n09\n\nWed\n\n[Investigating unexpected usage limit resets\n\n5:54 PM\n\nAll impacted services have now fully recovered.](/incidents/01M23KG62KKK448RN434CQ64Z8)[Increased Error Rate For Pro and Plus Plan Conversations\n\n4:21 PM\n\nAll impacted services have now fully recovered.](/incidents/01M23BNX5V1XT9P3NP0PX56FTN)\n\n08\n\nTue\n\n[Elevated errors for image generation\n\n9:59 PM\n\nAll impacted services have now fully recovered.](/incidents/01M20PYYYGRT9303VHAPA7YNT2)[File uploads are delayed or failing\n\n7:16 PM\n\nAll impacted services have now fully recovered.](/incidents/01M20QBACYZMK2PRCJQCBSWTYJ)\n\n04\n\nFri\n\n[Users in APAC region may face increased error in ChatGPT, Work, image generation, file upload, Voice, and Codex Cloud\n\n10:46 AM\n\nAll impacted services have now fully recovered.](/incidents/01M1NKFZH5EEYEREC54HNAHY35)\n\n03\n\nThu\n\n[Elevated errors across ChatGPT and Codex\n\n4:55 PM\n\nThe issue causing elevated errors across ChatGPT and Codex has been resolved.\n\nSome Codex remote control users may need to pair their mobile device again following this incident.](/incidents/01M1KWEDH417T2CF44YYHZDFCR)[ChatGPT Work Mode High Error Rates\n\n12:10 AM\n\nAll impacted services have now fully recovered.](/incidents/01M1J99EDCYED5GP2W8GZ3N2NA)\n\n02\n\nWed\n\n[Elevated errors creating new accounts\n\n6:45 PM\n\nThe issue affecting new account creation has been resolved.](/incidents/01M1HN7GRR6FJNWFVX2F8QMA3R)\n\n01\n\nTue\n\n[Elevated latency in the Responses API\n\n7:05 PM\n\nAll impacted services have now fully recovered.](/incidents/01M1CYZDD84XD0H56XNEV2PT98)[Elevated errors in ChatGPT conversations for Free and Go plans\n\n1:00 AM\n\nAll impacted services have now fully recovered.](/incidents/01M1D6E14BQSYQA3R5CNQBB7EB)\n\nAugust\n\n31\n\nMon\n\n[ChatGPT Work seeing elevated errors and latency\n\n8:28 PM\n\nAll impacted services have now fully recovered.](/incidents/01M1C5M4K0WC8PPT0Z175RJA1E)\n\n27\n\nThu\n\n[Users may experience an increase in error rates in Workspace Agents and ChatGPT Work on Web and Mobile\n\n10:14 PM\n\nAll impacted services have now fully recovered.](/incidents/01M1263309PD7VYV8EF95W2M2P)\n\n21\n\nFri\n\n[Unexpected logouts for some ChatGPT web users\n\n11:15 PM\n\nThe issue causing some ChatGPT web users to be unexpectedly logged out when refreshing the page has been resolved.](/incidents/01M0JXWD740S0Y50DWJZS7SH75)\n\n20\n\nThu\n\n[Elevated Codex API authentication errors\n\n5:52 PM\n\nAll impacted services have now fully recovered.](/incidents/01M0G1RZER839AZXWMYKSZF3GR)[Elevated Errors for Thinking mode in ChatGPT\n\n4:51 PM\n\nAll impacted services have now fully recovered.](/incidents/01M0FQAR3NNH3ANVTQMBRD47DC)[Chatgpt.com is down - all signups and logins are down as of right now\n\n12:54 AM\n\nAll impacted services have now fully recovered.](/incidents/01M0E7K87VJNMGW0QTMHPEQQ39)\n\n18\n\nTue\n\n[Elevated errors deploying Sites\n\n7:37 PM\n\nThe issue affecting site deployments has been resolved.](/incidents/01M0B4WSV41BCFZ9VDWKSMQVSP)\n\n13\n\nThu\n\n[Elevated errors in ChatGPT conversations for Free users\n\n11:58 PM\n\nAll impacted services have now fully recovered.](/incidents/01KZXVAJQ5XFH7PTM43XVPQWGJ)[Error while creating custom RBAC roles for Enterprise users\n\n10:26 PM\n\nAll impacted services have now fully recovered.](/incidents/01KZXPZD4KHMQQFF09PSNNEZT8)\n\n11\n\nTue\n\n[Increase in errors on API, Codex and Work Mode\n\n10:42 PM\n\nAll impacted services have now fully recovered.](/incidents/01KZSC0T66YTVM57N5T79SV8ZV)[Users unable to login to ads manager\n\n5:28 PM\n\nAll impacted services have now fully recovered.](/incidents/01KZRXPE0NGXA12FJNP8WZF8D7)[Increased error rates\n\n3:01 PM\n\nAll impacted services have now fully recovered.](/incidents/01KZRE6ZA1RE1ZH4HQ111CX1S8)[Elevated errors affecting ChatGPT Go conversations\n\n2:20 PM\n\nAll impacted services have now fully recovered.](/incidents/01KZRJHTR75WDXCMC0ZERX6YJC)[Increased error rates\n\n2:48 AM\n\nAll impacted services have now fully recovered.](/incidents/01KZNZTPWMV06Z6TQNMY1R1QDR)\n\n10\n\nMon\n\n[Increased errors for some ChatGPT users\n\n8:09 AM\n\nAll impacted services have now fully recovered.](/incidents/01KZN8RYNZY8T4QQGB3JWMPYRW)\n\n05\n\nWed\n\n[Elevated errors with image generation\n\n11:22 PM\n\nAll impacted services have now fully recovered.](/incidents/01KZ96S5HEWX0CX26W2WFYFKE6)[Issues with Custom GPT actions\n\n10:49 PM\n\nAll impacted services have now fully recovered.](/incidents/01KZ9DMQD2GJ8JJWDN7572RH78)[Elevated errors in ChatGPT conversations with files\n\n8:19 PM\n\nAll impacted services have now fully recovered.](/incidents/01KZ9E7QD8WFJD5DMF73QGVYH8)\n\n04\n\nTue\n\n[Elevated ChatGPT conversation errors affecting Plus, Pro, Business, and Edu users\n\n3:25 PM\n\nAll impacted services have now fully recovered.](/incidents/01KZ6CT9K9Q52S3707W75MNBGB)\n\nJuly\n\n31\n\nFri\n\n[Enterprise & Education Chat Errors\n\n9:28 AM\n\nThis is now resolved.](/incidents/01KYVPNEY9736Z04D3X1NSFFF9)\n\n30\n\nThu\n\n[Elevated errors affecting ChatGPT conversations\n\n4:01 PM\n\nAll impacted services have now fully recovered.](/incidents/01KYSQ7PC81PV3PZE3ZEVFK6K5)\n\n29\n\nWed\n\n[Elevated error rates with the invalid_prompt error code\n\n2:20 AM\n\nAll impacted services have now fully recovered.](/incidents/01KYNNX2TQ3PV0KPJ9PTRRPX6C)\n\n28\n\nTue\n\n[Elevated Image Generation Error Rate in ChatGPT\n\n3:15 PM\n\nAll impacted services have now fully recovered.](/incidents/01KYMJND2XYYBDVCF8DKA5DY3N)\n\n27\n\nMon\n\n[Image generation unavailable in ChatGPT\n\n8:24 PM\n\nAll impacted services have now fully recovered.](/incidents/01KYJFG4S86K8FMTB4N6BDZS7F)[Image generation unavailable in ChatGPT\n\n7:04 PM\n\nAll impacted services have now fully recovered.](/incidents/01KY23YCPJ9M5BFFT6ZHKQE9MP)[We’re seeing elevated latency, timeouts, and interrupted streaming across gpt 5.1 mini model and gpt 4.1 mini\n\n5:30 PM\n\nAll impacted services have now fully recovered.](/incidents/01KYJC3TDHZVSQFFPTC8X9RAHC)[Elevated errors affecting ChatGPT conversations\n\n4:32 PM\n\nAll impacted services have now fully recovered.](/incidents/01KYDN6YPS6ARY1EC9089N089G)\n\n25\n\nSat\n\n[Elevated error rates\n\n11:57 AM\n\nAll impacted services have now fully recovered.](/incidents/01KYCGY017EG43XZS6GFVXA8VH)[Elevated error rates\n\n11:08 AM\n\nAll impacted services have now fully recovered.](/incidents/01KYC921K145JTR1JK7DYKGWH1)\n\n24\n\nFri\n\n[Elevated Error Rates\n\n7:33 PM\n\nAll impacted services have now fully recovered.](/incidents/01KY7SX5MYJ2BP51X5MXAPYX71)[Elevated Errors in Codex Review\n\n9:35 AM\n\nAll impacted services have now fully recovered.](/incidents/01KY9HYHCMK8AND23B4X17XQEK)[Elevated API error rates and latency on gpt-image-2 model\n\n12:09 AM\n\nAll impacted services have now fully recovered.](/incidents/01KY8PGR54KXGBSFXHEJ3FM83F)\n\n23\n\nThu\n\n[Some users may experience elevated error rates in ChatGPT\n\n8:41 PM\n\nAll impacted services have now fully recovered.](/incidents/01KY81XMFAV8KXNJGVNEMKAK15)\n\n22\n\nWed\n\n[Elevated errors for Workspace Agent\n\n4:09 PM\n\nAll impacted services have now fully recovered.](/incidents/01KY54SWGRK806N6TJ495MYPDD)[Elevated Errors Affecting File Uploads and Image Generation\n\n2:39 PM\n\nAll impacted services have now fully recovered.](/incidents/01KY4BT971GFN59WBT0CKSGCPJ)\n\n21\n\nTue\n\n[Elevated errors for API image generation\n\n10:19 PM\n\nImage generation functionality has fully recovered, and error rates have returned to normal levels.](/incidents/01KY32PEQHPV5F2W4HCNFJ60RD)[Issues with logins and signups\n\n7:00 PM\n\nAll affected API Platform functionality has now fully recovered.](/incidents/01KY2ZF047ZNVDX0Z6F3QFXB1K)\n\n20\n\nMon\n\n[Elevated errors for GitHub-dependent ChatGPT and Codex workflows\n\n3:34 AM\n\nAll impacted services have now fully recovered.](/incidents/01KXYF4BTCV9DTZ5NDSFN716FH)\n\n19\n\nSun\n\n[Elevated errors affecting ChatGPT\n\n5:05 PM\n\nAll impacted services have now fully recovered.](/incidents/01KXXDNEAKEPRGFM661SBJJAM6)\n\n18\n\nSat\n\n[Some users are unable to access Codex\n\n12:58 PM\n\nAll impacted services have now fully recovered.](/incidents/01KXT44TAQQ2R0AZDDVSJGAC4H)[New ChatGPT App Not Available For Enterprise Users Without Codex Permissions\n\n8:24 AM\n\nAll impacted services have now fully recovered.](/incidents/01KXRBA8B98QHMMVP3M86NHFZ1)\n\n17\n\nFri\n\n[Codex 5.6-sol Experiencing Increased Server-Overload Errors\n\n8:42 PM\n\nAll impacted services have now fully recovered.](/incidents/01KXRHE25717D2WQ1WFMT2B7WZ)[Elevated errors for Github connector\n\n12:17 AM\n\nAll impacted services have now fully recovered.](/incidents/01KXPJ62Z704GE0SRNKQA64X4X)\n\n16\n\nThu\n\n[Elevated Error Rates For SSO Login\n\n3:23 PM\n\nAll impacted services have now fully recovered.](/incidents/01KXN14DD3EYYJ6PJ9M736WDSV)\n\n15\n\nWed\n\n[Elevated errors affecting ChatGPT\n\n12:39 AM\n\nAll impacted services have now fully recovered.](/incidents/01KXHH1BJ9BS0FVE2MGEJ9FZ5M)[Issue affecting voice mode in ChatGPT\n\n12:38 AM\n\nAll impacted services have now fully recovered.](/incidents/01KXHK8YFSP8B9WP110W4XEM45)\n\n14\n\nTue\n\n[Some ChatGPT Go users may experience conversation failures when using GPT-5.5.\n\n4:02 PM\n\nAll impacted services have now fully recovered.](/incidents/01KXGJPKV743DPQZDZQ57VR0JQ)\n\n13\n\nMon\n\n[Users may experience elevated errors uploading, deleting, and navigating files in the ChatGPT Library\n\n2:35 PM\n\nAll impacted services have now fully recovered.](/incidents/01KXDBYJ7BWBE2NRDAQTKPM5WK)[Elevated errors when creating sites in ChatGPT\n\n12:59 PM\n\nAll impacted services have now fully recovered.](/incidents/01KXDMD4T8TM58CSKBN7YFD2CK)\n\n12\n\nSun\n\n[Elevated conversation and login errors on ChatGPT for iOS and macOS\n\n3:28 PM\n\nAll impacted services have now fully recovered.](/incidents/01KXAVPTZ85KG478DP1YC0SV2V)\n\n11\n\nSat\n\n[Elevated Errors for Sora API\n\n7:03 AM\n\nAll impacted services have now fully recovered.](/incidents/01KX7Y6ETMKP3ATQ85Z33J0EHN)[Codex, workspace analytics, conversation search, searching for custom GPTs, ChatGPT user invites, and Compliance Log Platform download endpoint not working in FedRAMP workspaces\n\n2:11 AM\n\nCore functionality in FedRAMP workspaces has been restored, and the broader incident is resolved.](/incidents/01KWDW344V7XWEQERJSEW62W57)\n\n10\n\nFri\n\n[OpenAI website and Help Center content may be unavailable\n\n11:07 PM\n\nAll impacted services have now fully recovered.](/incidents/01KX6Y1QMFX4NASV5DD591AD50)\n\n09\n\nThu\n\n[Users are experiencing elevated errors when selecting models\n\n8:42 PM\n\nAll impacted services have now fully recovered.](/incidents/01KX46HHYJ0YB8VPBZTB0KZ03V)\n\n07\n\nTue\n\n[Elevated errors with image generation in ChatGPT\n\n4:12 PM\n\nAll impacted services have now fully recovered.](/incidents/01KWY5DQZ0KC8PTT3Y3T26H30D)\n\nJune\n\n29\n\nMon\n\n[Codex Usage Limits Depleting Faster Than Expected\n\n5:06 PM\n\nAll impacted services have now fully recovered.](/incidents/01KW2E6W0503W4NXJNCVAG8V6T)\n\n28\n\nSun\n\n[Issues with ChatGPT Windows desktop app\n\n3:29 AM\n\nAll impacted services have now fully recovered.](/incidents/01KW5HJAH5X1A2V62HP4ZST1V7)\n\n26\n\nFri\n\n[FedRAMP workspaces and API orgs have degraded performance\n\n11:07 PM\n\nAll impacted services have now fully recovered.](/incidents/01KV6NGBYE50GK3TRXHD2EMTXA)[Small Number of Users Have Incorrectly Cancelled Subscription\n\n2:18 AM\n\nAll impacted services have now fully recovered.](/incidents/01KVZRA3Z551H993JHJ9P2TW9E)\n\n25\n\nThu\n\n[Users may encounter issues using access token with Codex\n\n11:03 AM\n\nThis is now resolved](/incidents/01KVYNAMMJ7AMF94YBECG6JG6Q)\n\n24\n\nWed\n\n[gpt-4o-mini high error rate\n\n6:07 AM\n\nAll impacted services have now fully recovered.](/incidents/01KVW3CQQ51SWCV4A1SWA6ATVM)\n\n23\n\nTue\n\n[Users may experience elevated errors in ChatGPT uploading and downloading files\n\n4:38 PM\n\nAll impacted services have now fully recovered.](/incidents/01KVTDW6E1PXBTY2A9XEBT4MY4)\n\n19\n\nFri\n\n[chatgpt.com access issues\n\n5:23 AM\n\nAll impacted services have now fully recovered.](/incidents/01KVEZD06ZFM2CMDZQMQYDV9RK)\n\n18\n\nThu\n\n[SSO login errors for some ChatGPT Enterprise workspaces\n\n11:55 AM\n\nAll impacted services have now fully recovered.](/incidents/01KVCZ38K0RJZTSX7Y70RQMV2D)[ChatGPT failing to load or save\n\n3:55 AM\n\nAll impacted services have now fully recovered.](/incidents/01KVCC8P5XTCA7H7W7E6A2MYJS)\n\n17\n\nWed\n\n[Errors with conversations on Android and iOS devices\n\n6:23 PM\n\nAll impacted services have now fully recovered.](/incidents/01KVB9JAB1PP9GS4A6AZ52TT5Y)\n\n16\n\nTue\n\n[Codex \"Selected Model is at Capacity\" Error\n\n1:48 PM\n\nAll impacted services have now fully recovered.](/incidents/01KV7ZT644J4V94GSXMFPY2ANR)[Users may experience issue with Codex Cloud tasks\n\n12:55 AM\n\nAll impacted services have now fully recovered.](/incidents/01KV6W1JX2T4T1455777Q1R2W5)\n\n15\n\nMon\n\n[OAuth Account Creation / Login Error\n\n8:12 PM\n\nAll impacted services have now fully recovered.](/incidents/01KV67B3HB2B6JKHAMHCCYS0KZ)\n\nPowered by[https://incident.io?utm_source=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D\n\nAvailability metrics are reported at an aggregate level across all tiers, models and error types. Individual customer availability may vary depending on their subscription tier as well as the specific model and API features in use.",
"content_length": 14408,
"content_type": "text/html",
"description": "",
"status_code": 200,
"success": true,
"title": "OpenAI Status",
"url": "https://status.openai.com/history"
},
"error": "",
"elapsed": 1.10791801
}{
"tool_name": "web_fetch",
"tool_input": {
"brief": "incident detail",
"max_age_seconds": 3600,
"url": "https://status.openai.com/incidents/01M28MEQWTQJDRCRPFD9FWQ0H3"
},
"dispatch_id": "toolu_019jfGj24GWspicVaDUrPzEQ",
"parent_dispatch_id": "",
"handle": "",
"panel_kind": "web_fetch"
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_019jfGj24GWspicVaDUrPzEQ",
"status": "running",
"result": null,
"error": "",
"elapsed": null,
"fields": {
"progress": {
"message": "incident detail",
"metadata": {
"browser_chain": false,
"url": "https://status.openai.com/incidents/01M28MEQWTQJDRCRPFD9FWQ0H3"
}
},
"status": "running",
"updatedAt": 1789168525443
}
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_019jfGj24GWspicVaDUrPzEQ",
"status": "completed",
"result": {
"content": "1% of ChatGPT Work (mobile/web) turns are failing for existing threads - OpenAI Status\n\n[# ](https://status.openai.com/)\n\nSubscribe to updates\n\nPowered by[https://incident.io?utm_source=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D\n\nAvailability metrics are reported at an aggregate level across all tiers, models and error types. Individual customer availability may vary depending on their subscription tier as well as the specific model and API features in use.\n\n[/](/)1% of ChatGPT Work (mobile/web) turns are failing for existing threads\n\nMonitoring·Degraded performance\n\nWe have applied the mitigation and are monitoring the recovery.\n\nFri, Sep 11, 2026, 09:51 PM\n\n(1 hour ago)\n\n·\n\n[View all updates](#updates)\n\nAffected components\n\n04:22 PM\n\nNow\n\nChatGPT\n\n1 affected component\n\nUpdates\n\nMonitoring\n\nWe have applied the mitigation and are monitoring the recovery.\n\nFri, Sep 11, 2026, 09:51 PM\n\nInvestigating\n\nWe are investigating the issue for the listed services.\n\nFri, Sep 11, 2026, 05:17 PM(4 hours earlier)\n\nIdentified\n\nWe have identified that users are experiencing elevated errors for the impacted services.\n\nWe are working on implementing a mitigation.\n\nFri, Sep 11, 2026, 05:16 PM\n\nInvestigating\n\nWe have identified that users are experiencing elevated errors for the impacted services.\n\nWe are working on implementing a mitigation.\n\nFri, Sep 11, 2026, 04:22 PM(54 minutes earlier)",
"content_length": 1625,
"content_type": "text/html",
"description": "",
"status_code": 200,
"success": true,
"title": "1% of ChatGPT Work (mobile/web) turns are failing for existing threads - OpenAI Status",
"url": "https://status.openai.com/incidents/01M28MEQWTQJDRCRPFD9FWQ0H3"
},
"error": "",
"elapsed": 0.364579769
}{
"tool_name": "web_fetch",
"tool_input": {
"brief": "incident detail",
"max_age_seconds": 3600,
"url": "https://status.openai.com/incidents/01M27VK1VN54RQJGJEHB5JTQJJ"
},
"dispatch_id": "toolu_013kM3X6DNLoZYjsTnFYQkTM",
"parent_dispatch_id": "",
"handle": "",
"panel_kind": "web_fetch"
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_013kM3X6DNLoZYjsTnFYQkTM",
"status": "running",
"result": null,
"error": "",
"elapsed": null,
"fields": {
"progress": {
"message": "incident detail",
"metadata": {
"browser_chain": false,
"url": "https://status.openai.com/incidents/01M27VK1VN54RQJGJEHB5JTQJJ"
}
},
"status": "running",
"updatedAt": 1789168525438
}
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_013kM3X6DNLoZYjsTnFYQkTM",
"status": "completed",
"result": {
"content": "Elevated errors for GPT-5.6 Sol on the API - OpenAI Status\n\n[# ](https://status.openai.com/)\n\nSubscribe to updates\n\nPowered by[https://incident.io?utm_source=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D\n\nAvailability metrics are reported at an aggregate level across all tiers, models and error types. Individual customer availability may vary depending on their subscription tier as well as the specific model and API features in use.\n\n[/](/)Elevated errors for GPT-5.6 Sol on the API\n\nResolved·Degraded performance\n\nAll impacted services have now fully recovered.\n\nFri, Sep 11, 2026, 11:21 AM\n\n(11 hours ago)\n\n·\n\n[View all updates](#updates)\n\nAffected components\n\n09:08 AM\n\n11:21 AM\n\nAPIs\n\n2 affected components\n\nUpdates\n\nResolved\n\nAll impacted services have now fully recovered.\n\nFri, Sep 11, 2026, 11:21 AM\n\nMonitoring\n\nWe have brought additional capacity online and are seeing improvements for some GPT-5.6 Sol API traffic.\nWe continue to mitigate elevated errors affecting Chat Completions and Responses and are monitoring recovery\n\nFri, Sep 11, 2026, 10:09 AM(1 hour earlier)\n\nIdentified\n\nWe have identified that users are experiencing elevated errors for the impacted services.\n\nWe are working on implementing a mitigation.\n\nFri, Sep 11, 2026, 09:08 AM(1 hour earlier)",
"content_length": 1507,
"content_type": "text/html",
"description": "",
"status_code": 200,
"success": true,
"title": "Elevated errors for GPT-5.6 Sol on the API - OpenAI Status",
"url": "https://status.openai.com/incidents/01M27VK1VN54RQJGJEHB5JTQJJ"
},
"error": "",
"elapsed": 0.261000241
}{
"tool_name": "web_fetch",
"tool_input": {
"brief": "incident detail",
"max_age_seconds": 3600,
"url": "https://status.openai.com/incidents/01M27Q9GH7WVKNA61ZR3RDMSY5"
},
"dispatch_id": "toolu_01QTrDj5uX9wxA66piN3aUVV",
"parent_dispatch_id": "",
"handle": "",
"panel_kind": "web_fetch"
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01QTrDj5uX9wxA66piN3aUVV",
"status": "running",
"result": null,
"error": "",
"elapsed": null,
"fields": {
"progress": {
"message": "incident detail",
"metadata": {
"browser_chain": false,
"url": "https://status.openai.com/incidents/01M27Q9GH7WVKNA61ZR3RDMSY5"
}
},
"status": "running",
"updatedAt": 1789168525446
}
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01QTrDj5uX9wxA66piN3aUVV",
"status": "completed",
"result": {
"content": "Elevated errors for ChatGPT users in Europe - OpenAI Status\n\n[# ](https://status.openai.com/)\n\nSubscribe to updates\n\nPowered by[https://incident.io?utm_source=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D\n\nAvailability metrics are reported at an aggregate level across all tiers, models and error types. Individual customer availability may vary depending on their subscription tier as well as the specific model and API features in use.\n\n[/](/)Elevated errors for ChatGPT users in Europe\n\nResolved·Degraded performance\n\nAll impacted services have now fully recovered.\n\nFri, Sep 11, 2026, 10:16 AM\n\n(12 hours ago)\n\n·\n\n[View all updates](#updates)\n\nAffected components\n\n07:53 AM\n\n10:16 AM\n\nChatGPT\n\n1 affected component\n\nUpdates\n\nResolved\n\nAll impacted services have now fully recovered.\n\nFri, Sep 11, 2026, 10:16 AM\n\nMonitoring\n\nWe have applied the mitigation and are monitoring the recovery.\n\nFri, Sep 11, 2026, 08:37 AM(1 hour earlier)\n\nIdentified\n\nWe have identified that users are experiencing elevated errors for the impacted services.\n\nWe are working on implementing a mitigation.\n\nFri, Sep 11, 2026, 07:53 AM(44 minutes earlier)",
"content_length": 1365,
"content_type": "text/html",
"description": "",
"status_code": 200,
"success": true,
"title": "Elevated errors for ChatGPT users in Europe - OpenAI Status",
"url": "https://status.openai.com/incidents/01M27Q9GH7WVKNA61ZR3RDMSY5"
},
"error": "",
"elapsed": 0.340102965
}{
"tool_name": "web_fetch",
"tool_input": {
"brief": "incident detail",
"max_age_seconds": 3600,
"url": "https://status.openai.com/incidents/01M26E3PPAYJMMRHX2MZJCTHMF"
},
"dispatch_id": "toolu_01EzxTZwu3moU2jUkHoJfqLD",
"parent_dispatch_id": "",
"handle": "",
"panel_kind": "web_fetch"
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01EzxTZwu3moU2jUkHoJfqLD",
"status": "running",
"result": null,
"error": "",
"elapsed": null,
"fields": {
"progress": {
"message": "incident detail",
"metadata": {
"browser_chain": false,
"url": "https://status.openai.com/incidents/01M26E3PPAYJMMRHX2MZJCTHMF"
}
},
"status": "running",
"updatedAt": 1789168525450
}
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01EzxTZwu3moU2jUkHoJfqLD",
"status": "completed",
"result": {
"content": "Delays in customer support responses - OpenAI Status\n\n[# ](https://status.openai.com/)\n\nSubscribe to updates\n\nPowered by[https://incident.io?utm_source=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D\n\nAvailability metrics are reported at an aggregate level across all tiers, models and error types. Individual customer availability may vary depending on their subscription tier as well as the specific model and API features in use.\n\n[/](/)Delays in customer support responses\n\nResolved\n\nAll impacted services have now fully recovered.\n\nThu, Sep 10, 2026, 09:48 PM\n\n(1 day ago)\n\n·\n\n[View all updates](#updates)\n\nAffected components\n\nNo components marked as affected\n\nUpdates\n\nResolved\n\nAll impacted services have now fully recovered.\n\nThu, Sep 10, 2026, 09:48 PM\n\nMonitoring\n\nWe have applied the mitigation and are monitoring the recovery.\n\nThu, Sep 10, 2026, 09:20 PM(27 minutes earlier)\n\nIdentified\n\nWe have identified the cause of the issue affecting our customer support systems and are implementing a mitigation. Customers may continue to experience longer than usual response times.\n\nThu, Sep 10, 2026, 08:54 PM(25 minutes earlier)\n\nInvestigating\n\nWe are continuing to investigate technical issues affecting our customer support systems. Customers may continue to experience longer than usual response times. We are working to restore normal operations.\n\nThu, Sep 10, 2026, 08:45 PM\n\nInvestigating\n\nWe are investigating technical issues affecting our customer support systems. Customers may experience longer than usual response times. We are working to restore normal operations.\n\nThu, Sep 10, 2026, 07:53 PM(51 minutes earlier)",
"content_length": 1862,
"content_type": "text/html",
"description": "",
"status_code": 200,
"success": true,
"title": "Delays in customer support responses - OpenAI Status",
"url": "https://status.openai.com/incidents/01M26E3PPAYJMMRHX2MZJCTHMF"
},
"error": "",
"elapsed": 0.215666851
}{
"tool_name": "web_fetch",
"tool_input": {
"brief": "incident detail",
"max_age_seconds": 3600,
"url": "https://status.openai.com/incidents/01M26DX2PP1AFHGJK5E4M6S2J6"
},
"dispatch_id": "toolu_01E3viTsZ5KKiSjc7dUqjHDj",
"parent_dispatch_id": "",
"handle": "",
"panel_kind": "web_fetch"
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01E3viTsZ5KKiSjc7dUqjHDj",
"status": "running",
"result": null,
"error": "",
"elapsed": null,
"fields": {
"progress": {
"message": "incident detail",
"metadata": {
"browser_chain": false,
"url": "https://status.openai.com/incidents/01M26DX2PP1AFHGJK5E4M6S2J6"
}
},
"status": "running",
"updatedAt": 1789168525455
}
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01E3viTsZ5KKiSjc7dUqjHDj",
"status": "completed",
"result": {
"content": "Elevated errors affecting ChatGPT Work - OpenAI Status\n\n[# ](https://status.openai.com/)\n\nSubscribe to updates\n\nPowered by[https://incident.io?utm_source=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D\n\nAvailability metrics are reported at an aggregate level across all tiers, models and error types. Individual customer availability may vary depending on their subscription tier as well as the specific model and API features in use.\n\n[/](/)Elevated errors affecting ChatGPT Work\n\nResolved·Degraded performance\n\nAll impacted services are now fully recovered.\n\nThu, Sep 10, 2026, 09:30 PM\n\n(1 day ago)\n\n·\n\n[View all updates](#updates)\n\nAffected components\n\nSep 10, 2026, 07:49 PM\n\n09:30 PM\n\nChatGPT\n\n1 affected component\n\nUpdates\n\nResolved\n\nAll impacted services are now fully recovered.\n\nThu, Sep 10, 2026, 09:30 PM\n\nMonitoring\n\nWe have applied mitigation and are monitoring recovery.\n\nThu, Sep 10, 2026, 08:31 PM(58 minutes earlier)\n\nInvestigating\n\nWe are investigating elevated errors affecting some ChatGPT Work users. Some users may encounter server errors. We are working to mitigate the issue.\n\nThu, Sep 10, 2026, 07:50 PM(41 minutes earlier)\n\nInvestigating\n\nWe are investigating the issue for the listed services.\n\nThu, Sep 10, 2026, 07:49 PM",
"content_length": 1480,
"content_type": "text/html",
"description": "",
"status_code": 200,
"success": true,
"title": "Elevated errors affecting ChatGPT Work - OpenAI Status",
"url": "https://status.openai.com/incidents/01M26DX2PP1AFHGJK5E4M6S2J6"
},
"error": "",
"elapsed": 0.351808932
}{
"tool_name": "web_fetch",
"tool_input": {
"brief": "incident detail",
"max_age_seconds": 3600,
"url": "https://status.openai.com/incidents/01M24HYC9SX2Q4471EVMY6EXQE"
},
"dispatch_id": "toolu_01SCzc5SLea95g4P49fSa2C3",
"parent_dispatch_id": "",
"handle": "",
"panel_kind": "web_fetch"
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01SCzc5SLea95g4P49fSa2C3",
"status": "running",
"result": null,
"error": "",
"elapsed": null,
"fields": {
"progress": {
"message": "incident detail",
"metadata": {
"browser_chain": false,
"url": "https://status.openai.com/incidents/01M24HYC9SX2Q4471EVMY6EXQE"
}
},
"status": "running",
"updatedAt": 1789168525459
}
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01SCzc5SLea95g4P49fSa2C3",
"status": "completed",
"result": {
"content": "Unable to open shared ChatGPT Project using direct link - OpenAI Status\n\n[# ](https://status.openai.com/)\n\nSubscribe to updates\n\nPowered by[https://incident.io?utm_source=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D\n\nAvailability metrics are reported at an aggregate level across all tiers, models and error types. Individual customer availability may vary depending on their subscription tier as well as the specific model and API features in use.\n\n[/](/)Unable to open shared ChatGPT Project using direct link\n\nResolved·Degraded performance\n\nAll impacted services have now fully recovered.\n\nThu, Sep 10, 2026, 02:28 PM\n\n(1 day ago)\n\n·\n\n[View all updates](#updates)\n\nAffected components\n\nSep 10, 2026, 02:21 AM\n\n02:28 PM\n\nChatGPT\n\n1 affected component\n\nUpdates\n\nResolved\n\nAll impacted services have now fully recovered.\n\nThu, Sep 10, 2026, 02:28 PM\n\nMonitoring\n\nWe have applied the mitigation and are monitoring the recovery.\n\nThu, Sep 10, 2026, 12:06 PM(2 hours earlier)\n\nIdentified\n\nWe are still implementing the mitigation.\n\nThu, Sep 10, 2026, 09:37 AM(2 hours earlier)\n\nIdentified\n\nWe are still implementing the mitigation.\n\nThu, Sep 10, 2026, 06:01 AM(3 hours earlier)\n\nInvestigating\n\nWe are investigating the issue for the listed services.\n\nThu, Sep 10, 2026, 02:21 AM(3 hours earlier)",
"content_length": 1527,
"content_type": "text/html",
"description": "",
"status_code": 200,
"success": true,
"title": "Unable to open shared ChatGPT Project using direct link - OpenAI Status",
"url": "https://status.openai.com/incidents/01M24HYC9SX2Q4471EVMY6EXQE"
},
"error": "",
"elapsed": 0.249020031
}{
"tool_name": "web_fetch",
"tool_input": {
"brief": "incident detail",
"max_age_seconds": 3600,
"url": "https://status.openai.com/incidents/01M23KG62KKK448RN434CQ64Z8"
},
"dispatch_id": "toolu_01HrHPotVSaPhqKcH2E9cYPx",
"parent_dispatch_id": "",
"handle": "",
"panel_kind": "web_fetch"
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01HrHPotVSaPhqKcH2E9cYPx",
"status": "running",
"result": null,
"error": "",
"elapsed": null,
"fields": {
"progress": {
"message": "incident detail",
"metadata": {
"browser_chain": false,
"url": "https://status.openai.com/incidents/01M23KG62KKK448RN434CQ64Z8"
}
},
"status": "running",
"updatedAt": 1789168534380
}
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01HrHPotVSaPhqKcH2E9cYPx",
"status": "completed",
"result": {
"content": "Investigating unexpected usage limit resets - OpenAI Status\n\n[# ](https://status.openai.com/)\n\nSubscribe to updates\n\nPowered by[https://incident.io?utm_source=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D\n\nAvailability metrics are reported at an aggregate level across all tiers, models and error types. Individual customer availability may vary depending on their subscription tier as well as the specific model and API features in use.\n\n[/](/)Investigating unexpected usage limit resets\n\nResolved\n\nAll impacted services have now fully recovered.\n\nWed, Sep 9, 2026, 05:54 PM\n\n(2 days ago)\n\n·\n\n[View all updates](#updates)\n\nAffected components\n\nNo components marked as affected\n\nUpdates\n\nResolved\n\nAll impacted services have now fully recovered.\n\nWed, Sep 9, 2026, 05:54 PM\n\nMonitoring\n\nWe have applied the mitigation and are monitoring the recovery.\n\nWed, Sep 9, 2026, 05:45 PM\n\nIdentified\n\nWe've identified the issue and are working on a fix.\n\nWed, Sep 9, 2026, 05:40 PM\n\nInvestigating\n\nSome Codex users may be experiencing unexpected usage limit resets.\n\nWed, Sep 9, 2026, 05:29 PM(10 minutes earlier)",
"content_length": 1331,
"content_type": "text/html",
"description": "",
"status_code": 200,
"success": true,
"title": "Investigating unexpected usage limit resets - OpenAI Status",
"url": "https://status.openai.com/incidents/01M23KG62KKK448RN434CQ64Z8"
},
"error": "",
"elapsed": 0.203368958
}{
"tool_name": "web_fetch",
"tool_input": {
"brief": "incident detail",
"max_age_seconds": 3600,
"url": "https://status.openai.com/incidents/01M23BNX5V1XT9P3NP0PX56FTN"
},
"dispatch_id": "toolu_019berkAAWx9AgsXTov43cmG",
"parent_dispatch_id": "",
"handle": "",
"panel_kind": "web_fetch"
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_019berkAAWx9AgsXTov43cmG",
"status": "running",
"result": null,
"error": "",
"elapsed": null,
"fields": {
"progress": {
"message": "incident detail",
"metadata": {
"browser_chain": false,
"url": "https://status.openai.com/incidents/01M23BNX5V1XT9P3NP0PX56FTN"
}
},
"status": "running",
"updatedAt": 1789168534388
}
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_019berkAAWx9AgsXTov43cmG",
"status": "completed",
"result": {
"content": "Increased Error Rate For Pro and Plus Plan Conversations - OpenAI Status\n\n[# ](https://status.openai.com/)\n\nSubscribe to updates\n\nPowered by[https://incident.io?utm_source=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D\n\nAvailability metrics are reported at an aggregate level across all tiers, models and error types. Individual customer availability may vary depending on their subscription tier as well as the specific model and API features in use.\n\n[/](/)Increased Error Rate For Pro and Plus Plan Conversations\n\nResolved·Degraded performance\n\nAll impacted services have now fully recovered.\n\nWed, Sep 9, 2026, 04:21 PM\n\n(2 days ago)\n\n·\n\n[View all updates](#updates)\n\nAffected components\n\nSep 9, 2026, 03:13 PM\n\n04:21 PM\n\nChatGPT\n\n1 affected component\n\nUpdates\n\nResolved\n\nAll impacted services have now fully recovered.\n\nWed, Sep 9, 2026, 04:21 PM\n\nMonitoring\n\nWe have applied a mitigation and are monitoring the impacted services.\n\nWed, Sep 9, 2026, 03:44 PM(37 minutes earlier)\n\nInvestigating\n\nWe have identified that users are experiencing elevated errors for the impacted services.\n\nWe are working on implementing a mitigation.\n\nWed, Sep 9, 2026, 02:51 PM(53 minutes earlier)",
"content_length": 1412,
"content_type": "text/html",
"description": "",
"status_code": 200,
"success": true,
"title": "Increased Error Rate For Pro and Plus Plan Conversations - OpenAI Status",
"url": "https://status.openai.com/incidents/01M23BNX5V1XT9P3NP0PX56FTN"
},
"error": "",
"elapsed": 0.466868605
}{
"tool_name": "web_fetch",
"tool_input": {
"brief": "incident detail",
"max_age_seconds": 3600,
"url": "https://status.openai.com/incidents/01M20PYYYGRT9303VHAPA7YNT2"
},
"dispatch_id": "toolu_01RS8VHYbYiCauth6Evvcrv9",
"parent_dispatch_id": "",
"handle": "",
"panel_kind": "web_fetch"
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01RS8VHYbYiCauth6Evvcrv9",
"status": "running",
"result": null,
"error": "",
"elapsed": null,
"fields": {
"progress": {
"message": "incident detail",
"metadata": {
"browser_chain": false,
"url": "https://status.openai.com/incidents/01M20PYYYGRT9303VHAPA7YNT2"
}
},
"status": "running",
"updatedAt": 1789168534395
}
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01RS8VHYbYiCauth6Evvcrv9",
"status": "completed",
"result": {
"content": "Elevated errors for image generation - OpenAI Status\n\n[# ](https://status.openai.com/)\n\nSubscribe to updates\n\nPowered by[https://incident.io?utm_source=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D\n\nAvailability metrics are reported at an aggregate level across all tiers, models and error types. Individual customer availability may vary depending on their subscription tier as well as the specific model and API features in use.\n\n[/](/)Elevated errors for image generation\n\nResolved·Degraded performance\n\nAll impacted services have now fully recovered.\n\nTue, Sep 8, 2026, 09:59 PM\n\n(3 days ago)\n\n·\n\n[View all updates](#updates)\n\nAffected components\n\nSep 8, 2026, 02:32 PM\n\n09:59 PM\n\nAPIs\n\n1 affected component\n\nChatGPT\n\n1 affected component\n\nUpdates\n\nResolved\n\nAll impacted services have now fully recovered.\n\nTue, Sep 8, 2026, 09:59 PM\n\nMonitoring\n\nWe have applied the mitigation and are monitoring the recovery.\n\nTue, Sep 8, 2026, 07:11 PM(2 hours earlier)\n\nIdentified\n\nWe have identified the issue affecting image generation in ChatGPT and the Images API. Some image-generation requests may continue to fail.\n\nTue, Sep 8, 2026, 04:35 PM(2 hours earlier)\n\nInvestigating\n\nWe’re continuing to investigate elevated errors affecting image generation in ChatGPT and the Images API. We saw an increase in failed Images API requests after our last update. We’re applying mitigations and assessing their effect. Some image requests may still fail. We’ll share another update as we learn more.\n\nTue, Sep 8, 2026, 03:38 PM(57 minutes earlier)\n\nInvestigating\n\nWe’re continuing to investigate elevated errors affecting image generation in ChatGPT and the Images API. We’ve made changes aimed at reducing failures and are assessing their effect. Some requests may still fail. We’ll share another update as we learn more.\n\nTue, Sep 8, 2026, 03:05 PM(32 minutes earlier)\n\nInvestigating\n\nWe’re investigating elevated errors affecting image generation in ChatGPT and the Images API. Some requests may fail. We’ll share another update as we learn more.\n\nTue, Sep 8, 2026, 02:32 PM(32 minutes earlier)",
"content_length": 2338,
"content_type": "text/html",
"description": "",
"status_code": 200,
"success": true,
"title": "Elevated errors for image generation - OpenAI Status",
"url": "https://status.openai.com/incidents/01M20PYYYGRT9303VHAPA7YNT2"
},
"error": "",
"elapsed": 0.230917226
}{
"tool_name": "web_fetch",
"tool_input": {
"brief": "incident detail",
"max_age_seconds": 3600,
"url": "https://status.openai.com/incidents/01M20QBACYZMK2PRCJQCBSWTYJ"
},
"dispatch_id": "toolu_01KMsMUGDnPkrHkGyxroqY8Q",
"parent_dispatch_id": "",
"handle": "",
"panel_kind": "web_fetch"
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01KMsMUGDnPkrHkGyxroqY8Q",
"status": "running",
"result": null,
"error": "",
"elapsed": null,
"fields": {
"progress": {
"message": "incident detail",
"metadata": {
"browser_chain": false,
"url": "https://status.openai.com/incidents/01M20QBACYZMK2PRCJQCBSWTYJ"
}
},
"status": "running",
"updatedAt": 1789168534395
}
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01KMsMUGDnPkrHkGyxroqY8Q",
"status": "completed",
"result": {
"content": "[# ](https://status.openai.com/)\n\nSubscribe to updates\n\nPowered by[https://incident.io?utm_source=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D\n\nAvailability metrics are reported at an aggregate level across all tiers, models and error types. Individual customer availability may vary depending on their subscription tier as well as the specific model and API features in use.\n\nFile uploads are delayed or failing - OpenAI Status\n\n[/](/)File uploads are delayed or failing\n\nResolved·Degraded performance\n\nAll impacted services have now fully recovered.\n\nTue, Sep 8, 2026, 07:16 PM\n\n(3 days ago)\n\n·\n\n[View all updates](#updates)\n\nAffected components\n\nSep 8, 2026, 02:39 PM\n\n07:16 PM\n\nChatGPT\n\n2 affected components\n\nUpdates\n\nResolved\n\nAll impacted services have now fully recovered.\n\nTue, Sep 8, 2026, 07:16 PM\n\nMonitoring\n\nWe have applied the mitigation and are monitoring the recovery.\n\nTue, Sep 8, 2026, 05:48 PM(1 hour earlier)\n\nIdentified\n\nWe have identified the issue causing file-upload processing failures and delays in ChatGPT. Some files may remain unavailable while processing, and some uploads may fail.\n\nTue, Sep 8, 2026, 04:29 PM(1 hour earlier)\n\nInvestigating\n\nWe’re continuing to investigate file-upload processing failures and delays in ChatGPT. Some files may appear uploaded but remain unavailable while processing; other uploads may fail. We have not confirmed recovery and will share another update as we learn more.\n\nTue, Sep 8, 2026, 03:37 PM(52 minutes earlier)\n\nInvestigating\n\nWe are investigating the issue for the listed services.\n\nTue, Sep 8, 2026, 02:47 PM(49 minutes earlier)\n\nInvestigating\n\nSome file uploads are failing to process. Successful uploads may take longer than usual to become available. We’re investigating and will share another update as we learn more.\n\nTue, Sep 8, 2026, 02:39 PM",
"content_length": 2065,
"content_type": "text/html",
"description": "",
"status_code": 200,
"success": true,
"title": "File uploads are delayed or failing - OpenAI Status",
"url": "https://status.openai.com/incidents/01M20QBACYZMK2PRCJQCBSWTYJ"
},
"error": "",
"elapsed": 0.362222264
}{
"tool_name": "web_fetch",
"tool_input": {
"brief": "incident detail",
"max_age_seconds": 3600,
"url": "https://status.openai.com/incidents/01M1NKFZH5EEYEREC54HNAHY35"
},
"dispatch_id": "toolu_019urUpu8dJ9RDJBLk2xDDza",
"parent_dispatch_id": "",
"handle": "",
"panel_kind": "web_fetch"
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_019urUpu8dJ9RDJBLk2xDDza",
"status": "running",
"result": null,
"error": "",
"elapsed": null,
"fields": {
"progress": {
"message": "incident detail",
"metadata": {
"browser_chain": false,
"url": "https://status.openai.com/incidents/01M1NKFZH5EEYEREC54HNAHY35"
}
},
"status": "running",
"updatedAt": 1789168534408
}
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_019urUpu8dJ9RDJBLk2xDDza",
"status": "completed",
"result": {
"content": "Users in APAC region may face increased error in ChatGPT, Work, image generation, file upload, Voice, and Codex Cloud - OpenAI Status\n\n[# ](https://status.openai.com/)\n\nSubscribe to updates\n\nPowered by[https://incident.io?utm_source=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D\n\nAvailability metrics are reported at an aggregate level across all tiers, models and error types. Individual customer availability may vary depending on their subscription tier as well as the specific model and API features in use.\n\n[/](/)Users in APAC region may face increased error in ChatGPT, Work, image generation, file upload, Voice, and Codex Cloud\n\nResolved·Degraded performance\n\nAll impacted services have now fully recovered.\n\nFri, Sep 4, 2026, 10:46 AM\n\n(1 week ago)\n\n·\n\n[View all updates](#updates)\n\nAffected components\n\nSep 4, 2026, 07:00 AM\n\n10:46 AM\n\nChatGPT\n\n4 affected components\n\nCodex\n\n1 affected component\n\nUpdates\n\nResolved\n\nAll impacted services have now fully recovered.\n\nFri, Sep 4, 2026, 10:46 AM\n\nMonitoring\n\nWe have applied the mitigation and are monitoring the recovery.\n\nFri, Sep 4, 2026, 09:47 AM(58 minutes earlier)\n\nInvestigating\n\nWe are investigating the issue for the listed services.\n\nFri, Sep 4, 2026, 07:00 AM(2 hours earlier)",
"content_length": 1474,
"content_type": "text/html",
"description": "",
"status_code": 200,
"success": true,
"title": "Users in APAC region may face increased error in ChatGPT, Work, image generation, file upload, Voice, and Codex Cloud - OpenAI Status",
"url": "https://status.openai.com/incidents/01M1NKFZH5EEYEREC54HNAHY35"
},
"error": "",
"elapsed": 0.399284625
}{
"tool_name": "web_fetch",
"tool_input": {
"brief": "incident detail",
"max_age_seconds": 3600,
"url": "https://status.openai.com/incidents/01M1KWEDH417T2CF44YYHZDFCR"
},
"dispatch_id": "toolu_014AiTMCngbXzyoWVrzaXSxB",
"parent_dispatch_id": "",
"handle": "",
"panel_kind": "web_fetch"
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_014AiTMCngbXzyoWVrzaXSxB",
"status": "running",
"result": null,
"error": "",
"elapsed": null,
"fields": {
"progress": {
"message": "incident detail",
"metadata": {
"browser_chain": false,
"url": "https://status.openai.com/incidents/01M1KWEDH417T2CF44YYHZDFCR"
}
},
"status": "running",
"updatedAt": 1789168534426
}
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_014AiTMCngbXzyoWVrzaXSxB",
"status": "completed",
"result": {
"content": "Elevated errors across ChatGPT and Codex - OpenAI Status\n\n[# ](https://status.openai.com/)\n\nSubscribe to updates\n\nPowered by[https://incident.io?utm_source=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D\n\nAvailability metrics are reported at an aggregate level across all tiers, models and error types. Individual customer availability may vary depending on their subscription tier as well as the specific model and API features in use.\n\n[/](/)Elevated errors across ChatGPT and Codex\n\nResolved·Degraded performance\n\n[We’ve published a write-up of this incidentRead the write-up\n\nRead it here](/incidents/01M1KWEDH417T2CF44YYHZDFCR/write-up)\n\nAffected components\n\nSep 3, 2026, 02:58 PM\n\n04:55 PM\n\nChatGPT\n\n15 affected components\n\nCodex\n\n4 affected components\n\nUpdates\n\nWrite-up published\n\n[Read it here](/incidents/01M1KWEDH417T2CF44YYHZDFCR/write-up)\n\nResolved\n\nThe issue causing elevated errors across ChatGPT and Codex has been resolved.\n\nSome Codex remote control users may need to pair their mobile device again following this incident.\n\nThu, Sep 3, 2026, 04:55 PM\n\nMonitoring\n\nWe have applied the mitigation and are monitoring the recovery.\n\nThu, Sep 3, 2026, 03:17 PM(1 hour earlier)\n\nInvestigating\n\nWe are investigating the issue for the listed services.\n\nThu, Sep 3, 2026, 02:43 PM(34 minutes earlier)",
"content_length": 1537,
"content_type": "text/html",
"description": "",
"status_code": 200,
"success": true,
"title": "Elevated errors across ChatGPT and Codex - OpenAI Status",
"url": "https://status.openai.com/incidents/01M1KWEDH417T2CF44YYHZDFCR"
},
"error": "",
"elapsed": 0.510882671
}{
"tool_name": "web_fetch",
"tool_input": {
"brief": "incident detail",
"max_age_seconds": 3600,
"url": "https://status.openai.com/incidents/01M1J99EDCYED5GP2W8GZ3N2NA"
},
"dispatch_id": "toolu_01D8oLaoMxxZgNuvK5odVUhs",
"parent_dispatch_id": "",
"handle": "",
"panel_kind": "web_fetch"
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01D8oLaoMxxZgNuvK5odVUhs",
"status": "running",
"result": null,
"error": "",
"elapsed": null,
"fields": {
"progress": {
"message": "incident detail",
"metadata": {
"browser_chain": false,
"url": "https://status.openai.com/incidents/01M1J99EDCYED5GP2W8GZ3N2NA"
}
},
"status": "running",
"updatedAt": 1789168543267
}
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01D8oLaoMxxZgNuvK5odVUhs",
"status": "completed",
"result": {
"content": "ChatGPT Work Mode High Error Rates - OpenAI Status\n\n[# ](https://status.openai.com/)\n\nSubscribe to updates\n\nPowered by[https://incident.io?utm_source=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D\n\nAvailability metrics are reported at an aggregate level across all tiers, models and error types. Individual customer availability may vary depending on their subscription tier as well as the specific model and API features in use.\n\n[/](/)ChatGPT Work Mode High Error Rates\n\nResolved·Partial outage\n\n[We’ve published a write-up of this incidentRead the write-up\n\nRead it here](/incidents/01M1J99EDCYED5GP2W8GZ3N2NA/write-up)\n\nAffected components\n\nSep 3, 2026, 12:04 AM\n\n12:10 AM\n\nChatGPT\n\n15 affected components\n\nUpdates\n\nWrite-up published\n\n[Read it here](/incidents/01M1J99EDCYED5GP2W8GZ3N2NA/write-up)\n\nResolved\n\nAll impacted services have now fully recovered.\n\nThu, Sep 3, 2026, 12:10 AM\n\nInvestigating\n\nChatGPT Work Mode is experiencing high error rates. We are investigating the issue.\n\nThu, Sep 3, 2026, 12:04 AM",
"content_length": 1243,
"content_type": "text/html",
"description": "",
"status_code": 200,
"success": true,
"title": "ChatGPT Work Mode High Error Rates - OpenAI Status",
"url": "https://status.openai.com/incidents/01M1J99EDCYED5GP2W8GZ3N2NA"
},
"error": "",
"elapsed": 0.559958136
}{
"tool_name": "web_fetch",
"tool_input": {
"brief": "incident detail",
"max_age_seconds": 3600,
"url": "https://status.openai.com/incidents/01M1HN7GRR6FJNWFVX2F8QMA3R"
},
"dispatch_id": "toolu_018rgZ3o4XM5b5ktsDVm7ZNi",
"parent_dispatch_id": "",
"handle": "",
"panel_kind": "web_fetch"
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_018rgZ3o4XM5b5ktsDVm7ZNi",
"status": "running",
"result": null,
"error": "",
"elapsed": null,
"fields": {
"progress": {
"message": "incident detail",
"metadata": {
"browser_chain": false,
"url": "https://status.openai.com/incidents/01M1HN7GRR6FJNWFVX2F8QMA3R"
}
},
"status": "running",
"updatedAt": 1789168543271
}
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_018rgZ3o4XM5b5ktsDVm7ZNi",
"status": "completed",
"result": {
"content": "Elevated errors creating new accounts - OpenAI Status\n\n[# ](https://status.openai.com/)\n\nSubscribe to updates\n\nPowered by[https://incident.io?utm_source=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D\n\nAvailability metrics are reported at an aggregate level across all tiers, models and error types. Individual customer availability may vary depending on their subscription tier as well as the specific model and API features in use.\n\n[/](/)Elevated errors creating new accounts\n\nResolved\n\n[We’ve published a write-up of this incidentRead the write-up\n\nRead it here](/incidents/01M1HN7GRR6FJNWFVX2F8QMA3R/write-up)\n\nAffected components\n\nNo components marked as affected\n\nUpdates\n\nWrite-up published\n\n[Read it here](/incidents/01M1HN7GRR6FJNWFVX2F8QMA3R/write-up)\n\nResolved\n\nThe issue affecting new account creation has been resolved.\n\nWed, Sep 2, 2026, 06:45 PM\n\nMonitoring\n\nWe have applied the mitigation and are monitoring recovery.\n\nWed, Sep 2, 2026, 06:39 PM\n\nInvestigating\n\nWe are investigating an issue preventing some users from creating new accounts. We will share updates as we learn more.\n\nWed, Sep 2, 2026, 06:13 PM(25 minutes earlier)",
"content_length": 1368,
"content_type": "text/html",
"description": "",
"status_code": 200,
"success": true,
"title": "Elevated errors creating new accounts - OpenAI Status",
"url": "https://status.openai.com/incidents/01M1HN7GRR6FJNWFVX2F8QMA3R"
},
"error": "",
"elapsed": 0.354810383
}{
"tool_name": "web_fetch",
"tool_input": {
"brief": "incident detail",
"max_age_seconds": 3600,
"url": "https://status.openai.com/incidents/01M1CYZDD84XD0H56XNEV2PT98"
},
"dispatch_id": "toolu_01FiXvmHFGevpsCRGnD1iXAi",
"parent_dispatch_id": "",
"handle": "",
"panel_kind": "web_fetch"
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01FiXvmHFGevpsCRGnD1iXAi",
"status": "running",
"result": null,
"error": "",
"elapsed": null,
"fields": {
"progress": {
"message": "incident detail",
"metadata": {
"browser_chain": false,
"url": "https://status.openai.com/incidents/01M1CYZDD84XD0H56XNEV2PT98"
}
},
"status": "running",
"updatedAt": 1789168543275
}
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01FiXvmHFGevpsCRGnD1iXAi",
"status": "completed",
"result": {
"content": "Elevated latency in the Responses API - OpenAI Status\n\n[# ](https://status.openai.com/)\n\nSubscribe to updates\n\nPowered by[https://incident.io?utm_source=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D\n\nAvailability metrics are reported at an aggregate level across all tiers, models and error types. Individual customer availability may vary depending on their subscription tier as well as the specific model and API features in use.\n\n[/](/)Elevated latency in the Responses API\n\nResolved·Degraded performance\n\nAll impacted services have now fully recovered.\n\nTue, Sep 1, 2026, 07:05 PM\n\n(1 week ago)\n\n·\n\n[View all updates](#updates)\n\nAffected components\n\nAug 31, 2026, 10:27 PM\n\nSep 1, 2026, 07:05 PM\n\nAPIs\n\n1 affected component\n\nUpdates\n\nResolved\n\nAll impacted services have now fully recovered.\n\nTue, Sep 1, 2026, 07:05 PM\n\nMonitoring\n\nWe have applied the mitigation and are monitoring the recovery.\n\nTue, Sep 1, 2026, 06:09 PM(56 minutes earlier)\n\nIdentified\n\nWe are implementing the mitigation.\n\nTue, Sep 1, 2026, 05:36 PM(33 minutes earlier)\n\nIdentified\n\nWe have identified elevated latencies impacting Responses API on the US endpoint.\n\nTue, Sep 1, 2026, 03:15 PM(2 hours earlier)\n\nMonitoring\n\nWe have applied the mitigation and are monitoring the recovery.\n\nTue, Sep 1, 2026, 01:46 AM(13 hours earlier)\n\nMonitoring\n\nWe have applied a mitigation and are monitoring recovery.\n\nMon, Aug 31, 2026, 11:13 PM(2 hours earlier)\n\nIdentified\n\nWe have identified an issue causing elevated latency for some Responses API requests. We are working on implementing a mitigation.\n\nMon, Aug 31, 2026, 10:27 PM(45 minutes earlier)",
"content_length": 1856,
"content_type": "text/html",
"description": "",
"status_code": 200,
"success": true,
"title": "Elevated latency in the Responses API - OpenAI Status",
"url": "https://status.openai.com/incidents/01M1CYZDD84XD0H56XNEV2PT98"
},
"error": "",
"elapsed": 0.346546497
}{
"tool_name": "web_fetch",
"tool_input": {
"brief": "incident detail",
"max_age_seconds": 3600,
"url": "https://status.openai.com/incidents/01M1D6E14BQSYQA3R5CNQBB7EB"
},
"dispatch_id": "toolu_01JFruf4GrCU2bXoaKL8bVQJ",
"parent_dispatch_id": "",
"handle": "",
"panel_kind": "web_fetch"
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01JFruf4GrCU2bXoaKL8bVQJ",
"status": "running",
"result": null,
"error": "",
"elapsed": null,
"fields": {
"progress": {
"message": "incident detail",
"metadata": {
"browser_chain": false,
"url": "https://status.openai.com/incidents/01M1D6E14BQSYQA3R5CNQBB7EB"
}
},
"status": "running",
"updatedAt": 1789168543275
}
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01JFruf4GrCU2bXoaKL8bVQJ",
"status": "completed",
"result": {
"content": "Elevated errors in ChatGPT conversations for Free and Go plans - OpenAI Status\n\n[# ](https://status.openai.com/)\n\nSubscribe to updates\n\nPowered by[https://incident.io?utm_source=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D\n\nAvailability metrics are reported at an aggregate level across all tiers, models and error types. Individual customer availability may vary depending on their subscription tier as well as the specific model and API features in use.\n\n[/](/)Elevated errors in ChatGPT conversations for Free and Go plans\n\nResolved·Degraded performance\n\n[We’ve published a write-up of this incidentRead the write-up\n\nRead it here](/incidents/01M1D6E14BQSYQA3R5CNQBB7EB/write-up)\n\nAffected components\n\nSep 1, 2026, 12:38 AM\n\n01:00 AM\n\nChatGPT\n\n1 affected component\n\nUpdates\n\nWrite-up published\n\n[Read it here](/incidents/01M1D6E14BQSYQA3R5CNQBB7EB/write-up)\n\nResolved\n\nAll impacted services have now fully recovered.\n\nTue, Sep 1, 2026, 01:00 AM\n\nMonitoring\n\nWe have applied the mitigation and are monitoring the recovery.\n\nTue, Sep 1, 2026, 12:52 AM\n\nInvestigating\n\nWe are investigating the issue for the listed services.\n\nTue, Sep 1, 2026, 12:38 AM(13 minutes earlier)",
"content_length": 1402,
"content_type": "text/html",
"description": "",
"status_code": 200,
"success": true,
"title": "Elevated errors in ChatGPT conversations for Free and Go plans - OpenAI Status",
"url": "https://status.openai.com/incidents/01M1D6E14BQSYQA3R5CNQBB7EB"
},
"error": "",
"elapsed": 0.372750466
}{
"tool_name": "web_fetch",
"tool_input": {
"brief": "incident detail",
"max_age_seconds": 3600,
"url": "https://status.openai.com/incidents/01M1C5M4K0WC8PPT0Z175RJA1E"
},
"dispatch_id": "toolu_01R4sNJeCGBRrLbYeR9zcyMc",
"parent_dispatch_id": "",
"handle": "",
"panel_kind": "web_fetch"
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01R4sNJeCGBRrLbYeR9zcyMc",
"status": "running",
"result": null,
"error": "",
"elapsed": null,
"fields": {
"progress": {
"message": "incident detail",
"metadata": {
"browser_chain": false,
"url": "https://status.openai.com/incidents/01M1C5M4K0WC8PPT0Z175RJA1E"
}
},
"status": "running",
"updatedAt": 1789168543280
}
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01R4sNJeCGBRrLbYeR9zcyMc",
"status": "completed",
"result": {
"content": "ChatGPT Work seeing elevated errors and latency - OpenAI Status\n\n[# ](https://status.openai.com/)\n\nSubscribe to updates\n\nPowered by[https://incident.io?utm_source=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D&utm_medium=%5BREDACTED%5D\n\nAvailability metrics are reported at an aggregate level across all tiers, models and error types. Individual customer availability may vary depending on their subscription tier as well as the specific model and API features in use.\n\n[/](/)ChatGPT Work seeing elevated errors and latency\n\nResolved·Partial outage\n\n[We’ve published a write-up of this incidentRead the write-up\n\nRead it here](/incidents/01M1C5M4K0WC8PPT0Z175RJA1E/write-up)\n\nAffected components\n\nAug 31, 2026, 03:04 PM\n\n08:28 PM\n\nChatGPT\n\n1 affected component\n\nUpdates\n\nWrite-up published\n\n[Read it here](/incidents/01M1C5M4K0WC8PPT0Z175RJA1E/write-up)\n\nResolved\n\nAll impacted services have now fully recovered.\n\nMon, Aug 31, 2026, 08:28 PM\n\nMonitoring\n\nWe have applied a mitigation and are monitoring recovery.\n\nMon, Aug 31, 2026, 08:01 PM(27 minutes earlier)\n\nIdentified\n\nUser across multiple subscription plans may be unable to start or continue tasks in ChatGPT Work.\n\nWe are continuing work on implementing a mitigation.\n\nMon, Aug 31, 2026, 07:29 PM(31 minutes earlier)\n\nIdentified\n\nUser across multiple subscription plans may be unable to start or continue tasks in ChatGPT Work.\n\nWe are continuing work on implementing a mitigation.\n\nMon, Aug 31, 2026, 05:52 PM(1 hour earlier)\n\nIdentified\n\nUser across multiple subscription plans may be unable to start or continue tasks in ChatGPT Work. We\n\nWe are continuing work on implementing a mitigation.\n\nMon, Aug 31, 2026, 05:01 PM(50 minutes earlier)\n\nIdentified\n\nUser across multiple subscription plans may be unable to start or continue tasks in ChatGPT Work. We are continuing to work on a mitigation.\n\nMon, Aug 31, 2026, 04:02 PM(59 minutes earlier)\n\nIdentified\n\nWe have identified that users are experiencing elevated errors for the impacted services. Plus users are particularly impacted, where Work mode is currently unavailable.\n\nWe are working on implementing a mitigation.\n\nMon, Aug 31, 2026, 03:21 PM(40 minutes earlier)\n\nIdentified\n\nWe have identified that users are experiencing elevated latency for the impacted services.\n\nWe are working on implementing a mitigation.\n\nMon, Aug 31, 2026, 03:04 PM(16 minutes earlier)",
"content_length": 2594,
"content_type": "text/html",
"description": "",
"status_code": 200,
"success": true,
"title": "ChatGPT Work seeing elevated errors and latency - OpenAI Status",
"url": "https://status.openai.com/incidents/01M1C5M4K0WC8PPT0Z175RJA1E"
},
"error": "",
"elapsed": 0.212801813
}{
"tool_name": "send_message",
"tool_input": {
"final": true,
"in_response_to": "893740d3",
"message": "17 incidents on [OpenAI's status page](https://status.openai.com/history) since Aug 31, 2026. One is still open; the other 16 are resolved. Times are as shown on the page.\n\n| Date | Incident | Components | Duration | Severity | Status |\n|---|---|---|---|---|---|\n| Sep 11 | [1% of ChatGPT Work turns failing on existing threads](https://status.openai.com/incidents/01M28MEQWTQJDRCRPFD9FWQ0H3) | ChatGPT (1) | 04:22 PM, ongoing ~5.5h | Degraded performance | Monitoring (open) |\n| Sep 11 | [Elevated errors for GPT-5.6 Sol on the API](https://status.openai.com/incidents/01M27VK1VN54RQJGJEHB5JTQJJ) | APIs (2): Chat Completions, Responses | 09:08–11:21 AM (2h13m) | Degraded performance | Resolved |\n| Sep 11 | [Elevated errors for ChatGPT users in Europe](https://status.openai.com/incidents/01M27Q9GH7WVKNA61ZR3RDMSY5) | ChatGPT (1) | 07:53–10:16 AM (2h23m) | Degraded performance | Resolved |\n| Sep 10 | [Delays in customer support responses](https://status.openai.com/incidents/01M26E3PPAYJMMRHX2MZJCTHMF) | none marked | 07:53–09:48 PM (1h55m) | No severity set | Resolved |\n| Sep 10 | [Elevated errors affecting ChatGPT Work](https://status.openai.com/incidents/01M26DX2PP1AFHGJK5E4M6S2J6) | ChatGPT (1) | 07:49–09:30 PM (1h41m) | Degraded performance | Resolved |\n| Sep 10 | [Shared ChatGPT Project not opening via direct link](https://status.openai.com/incidents/01M24HYC9SX2Q4471EVMY6EXQE) | ChatGPT (1) | 02:21 AM–02:28 PM (12h07m) | Degraded performance | Resolved |\n| Sep 9 | [Unexpected Codex usage limit resets](https://status.openai.com/incidents/01M23KG62KKK448RN434CQ64Z8) | none marked | 05:29–05:54 PM (25m) | No severity set | Resolved |\n| Sep 9 | [Increased error rate for Pro and Plus conversations](https://status.openai.com/incidents/01M23BNX5V1XT9P3NP0PX56FTN) | ChatGPT (1) | 02:51–04:21 PM (1h30m) | Degraded performance | Resolved |\n| Sep 8 | [Elevated errors for image generation](https://status.openai.com/incidents/01M20PYYYGRT9303VHAPA7YNT2) | ChatGPT (1) + APIs (1, Images) | 02:32–09:59 PM (7h27m) | Degraded performance | Resolved |\n| Sep 8 | [File uploads delayed or failing](https://status.openai.com/incidents/01M20QBACYZMK2PRCJQCBSWTYJ) | ChatGPT (2) | 02:39–07:16 PM (4h37m) | Degraded performance | Resolved |\n| Sep 4 | [APAC errors across ChatGPT, Work, images, uploads, Voice, Codex Cloud](https://status.openai.com/incidents/01M1NKFZH5EEYEREC54HNAHY35) | ChatGPT (4), Codex (1) | 07:00–10:46 AM (3h46m) | Degraded performance | Resolved |\n| Sep 3 | [Elevated errors across ChatGPT and Codex](https://status.openai.com/incidents/01M1KWEDH417T2CF44YYHZDFCR) | ChatGPT (15), Codex (4) | 02:43–04:55 PM (2h12m) | Degraded performance | Resolved, write-up published; some Codex remote-control users had to re-pair |\n| Sep 3 | [ChatGPT Work Mode high error rates](https://status.openai.com/incidents/01M1J99EDCYED5GP2W8GZ3N2NA) | ChatGPT (15) | 12:04–12:10 AM (6m) | Partial outage | Resolved, write-up published |\n| Sep 2 | [Elevated errors creating new accounts](https://status.openai.com/incidents/01M1HN7GRR6FJNWFVX2F8QMA3R) | none marked | 06:13–06:45 PM (32m) | No severity set | Resolved, write-up published |\n| Aug 31–Sep 1 | [Elevated latency in the Responses API](https://status.openai.com/incidents/01M1CYZDD84XD0H56XNEV2PT98) | APIs (1, US endpoint) | Aug 31 10:27 PM–Sep 1 07:05 PM (~20h38m) | Degraded performance | Resolved |\n| Sep 1 | [Elevated errors for Free and Go conversations](https://status.openai.com/incidents/01M1D6E14BQSYQA3R5CNQBB7EB) | ChatGPT (1) | 12:38–01:00 AM (22m) | Degraded performance | Resolved, write-up published |\n| Aug 31 | [ChatGPT Work elevated errors and latency](https://status.openai.com/incidents/01M1C5M4K0WC8PPT0Z175RJA1E) | ChatGPT (1) | 03:04–08:28 PM (5h24m) | Partial outage (Work mode unavailable for Plus) | Resolved, write-up published |\n\nPattern: ChatGPT Work and image generation/file uploads were the repeat offenders, and only two events rose above \"degraded performance\" to partial outage."
},
"dispatch_id": "toolu_01JkLQ7XgbAAckfzEJZv9Gff",
"parent_dispatch_id": "",
"handle": "",
"panel_kind": ""
}{
"tool_name": "send_message",
"dispatch_id": "toolu_01JkLQ7XgbAAckfzEJZv9Gff",
"status": "completed",
"result": "Delivered (confirmed) as 3 messages. Your draft was polished into texting register, so the wording differs from what you wrote; this is exactly what the user sees:\n1) 17 incidents since Aug 31. One still open; 16 resolved.\n2) ### Incidents on OpenAI's status page · 14 days since Aug 31\n\n| Date | Incident | Components | Duration | Severity | Status |\n|---|---|---|---|---|---|\n| Sep 11 | [1% of ChatGPT Work turns failing on existing threads](https://status.openai.com/incidents/01M28MEQWTQJDRCRPFD9FWQ0H3) | ChatGPT (1) | 04:22 PM, ongoing ~5.5h | Degraded performance | Monitoring (open) |\n| Sep 11 | [Elevated errors for GPT-5.6 Sol on the API](https://status.openai.com/incidents/01M27VK1VN54RQJGJEHB5JTQJJ) | APIs (2): Chat Completions, Responses | 09:08–11:21 AM (2h13m) | Degraded performance | Resolved |\n| Sep 11 | [Elevated errors for ChatGPT users in Europe](https://status.openai.com/incidents/01M27Q9GH7WVKNA61ZR3RDMSY5) | ChatGPT (1) | 07:53–10:16 AM (2h23m) | Degraded performance | Resolved |\n| Sep 10 | [Delays in customer support responses](https://status.openai.com/incidents/01M26E3PPAYJMMRHX2MZJCTHMF) | none marked | 07:53–09:48 PM (1h55m) | No severity set | Resolved |\n| Sep 10 | [Elevated errors affecting ChatGPT Work](https://status.openai.com/incidents/01M26DX2PP1AFHGJK5E4M6S2J6) | ChatGPT (1) | 07:49–09:30 PM (1h41m) | Degraded performance | Resolved |\n| Sep 10 | [Shared ChatGPT Project not opening via direct link](https://status.openai.com/incidents/01M24HYC9SX2Q4471EVMY6EXQE) | ChatGPT (1) | 02:21 AM–02:28 PM (12h07m) | Degraded performance | Resolved |\n| Sep 9 | [Unexpected Codex usage limit resets](https://status.openai.com/incidents/01M23KG62KKK448RN434CQ64Z8) | none marked | 05:29–05:54 PM (25m) | No severity set | Resolved |\n| Sep 9 | [Increased error rate for Pro and Plus conversations](https://status.openai.com/incidents/01M23BNX5V1XT9P3NP0PX56FTN) | ChatGPT (1) | 02:51–04:21 PM (1h30m) | Degraded performance | Resolved |\n| Sep 8 | [Elevated errors for image generation](https://status.openai.com/incidents/01M20PYYYGRT9303VHAPA7YNT2) | ChatGPT (1) + APIs (1, Images) | 02:32–09:59 PM (7h27m) | Degraded performance | Resolved |\n| Sep 8 | [File uploads delayed or failing](https://status.openai.com/incidents/01M20QBACYZMK2PRCJQCBSWTYJ) | ChatGPT (2) | 02:39–07:16 PM (4h37m) | Degraded performance | Resolved |\n| Sep 4 | [APAC errors across ChatGPT, Work, images, uploads, Voice, Codex Cloud](https://status.openai.com/incidents/01M1NKFZH5EEYEREC54HNAHY35) | ChatGPT (4), Codex (1) | 07:00–10:46 AM (3h46m) | Degraded performance | Resolved |\n| Sep 3 | [Elevated errors across ChatGPT and Codex](https://status.openai.com/incidents/01M1KWEDH417T2CF44YYHZDFCR) | ChatGPT (15), Codex (4) | 02:43–04:55 PM (2h12m) | Degraded performance | Resolved, write-up published; some Codex remote-control users had to re-pair |\n| Sep 3 | [ChatGPT Work Mode high error rates](https://status.openai.com/incidents/01M1J99EDCYED5GP2W8GZ3N2NA) | ChatGPT (15) | 12:04–12:10 AM (6m) | Partial outage | Resolved, write-up published |\n| Sep 2 | [Elevated errors creating new accounts](https://status.openai.com/incidents/01M1HN7GRR6FJNWFVX2F8QMA3R) | none marked | 06:13–06:45 PM (32m) | No severity set | Resolved, write-up published |\n| Aug 31–Sep 1 | [Elevated latency in the Responses API](https://status.openai.com/incidents/01M1CYZDD84XD0H56XNEV2PT98) | APIs (1, US endpoint) | Aug 31 10:27 PM–Sep 1 07:05 PM (~20h38m) | Degraded performance | Resolved |\n| Sep 1 | [Elevated errors for Free and Go conversations](https://status.openai.com/incidents/01M1D6E14BQSYQA3R5CNQBB7EB) | ChatGPT (1) | 12:38–01:00 AM (22m) | Degraded performance | Resolved, write-up published |\n| Aug 31 | [ChatGPT Work elevated errors and latency](https://status.openai.com/incidents/01M1C5M4K0WC8PPT0Z175RJA1E) | ChatGPT (1) | 03:04–08:28 PM (5h24m) | Partial outage (Work mode unavailable for Plus) | Resolved, write-up published |\n3) ChatGPT Work and image/file uploads were the repeat trouble spots. Only two incidents hit partial outage; the rest stayed degraded.\nThese are your words now, and this is the whole reply: the delivery layer chose its density and shape by design. Never dispute, re-explain, or apologize for the phrasing, and never send a supplement to restore detail it left out. Only a final send settles its request. Never chase wording with another send. If a fact in it is wrong and would change what the user does, correct it when their next message arrives.\n\nNothing else is open: no request awaits a reply and no work is running. A response with no tool call ends the run.\nanswers: 893740d3-0da9-4e87-b74e-f26c68cd925e",
"error": "",
"elapsed": 26.758053673
}| Date | Incident | Components | Duration | Severity | Status |
|---|---|---|---|---|---|
| Sep 11 | 1% of ChatGPT Work turns failing on existing threads | ChatGPT (1) | 04:22 PM, ongoing ~5.5h | Degraded performance | Monitoring (open) |
| Sep 11 | Elevated errors for GPT-5.6 Sol on the API | APIs (2): Chat Completions, Responses | 09:08–11:21 AM (2h13m) | Degraded performance | Resolved |
| Sep 11 | Elevated errors for ChatGPT users in Europe | ChatGPT (1) | 07:53–10:16 AM (2h23m) | Degraded performance | Resolved |
| Sep 10 | Delays in customer support responses | none marked | 07:53–09:48 PM (1h55m) | No severity set | Resolved |
| Sep 10 | Elevated errors affecting ChatGPT Work | ChatGPT (1) | 07:49–09:30 PM (1h41m) | Degraded performance | Resolved |
| Sep 10 | Shared ChatGPT Project not opening via direct link | ChatGPT (1) | 02:21 AM–02:28 PM (12h07m) | Degraded performance | Resolved |
| Sep 9 | Unexpected Codex usage limit resets | none marked | 05:29–05:54 PM (25m) | No severity set | Resolved |
| Sep 9 | Increased error rate for Pro and Plus conversations | ChatGPT (1) | 02:51–04:21 PM (1h30m) | Degraded performance | Resolved |
| Sep 8 | Elevated errors for image generation | ChatGPT (1) + APIs (1, Images) | 02:32–09:59 PM (7h27m) | Degraded performance | Resolved |
| Sep 8 | File uploads delayed or failing | ChatGPT (2) | 02:39–07:16 PM (4h37m) | Degraded performance | Resolved |
| Sep 4 | APAC errors across ChatGPT, Work, images, uploads, Voice, Codex Cloud | ChatGPT (4), Codex (1) | 07:00–10:46 AM (3h46m) | Degraded performance | Resolved |
| Sep 3 | Elevated errors across ChatGPT and Codex | ChatGPT (15), Codex (4) | 02:43–04:55 PM (2h12m) | Degraded performance | Resolved, write-up published; some Codex remote-control users had to re-pair |
| Sep 3 | ChatGPT Work Mode high error rates | ChatGPT (15) | 12:04–12:10 AM (6m) | Partial outage | Resolved, write-up published |
| Sep 2 | Elevated errors creating new accounts | none marked | 06:13–06:45 PM (32m) | No severity set | Resolved, write-up published |
| Aug 31–Sep 1 | Elevated latency in the Responses API | APIs (1, US endpoint) | Aug 31 10:27 PM–Sep 1 07:05 PM (~20h38m) | Degraded performance | Resolved |
| Sep 1 | Elevated errors for Free and Go conversations | ChatGPT (1) | 12:38–01:00 AM (22m) | Degraded performance | Resolved, write-up published |
| Aug 31 | ChatGPT Work elevated errors and latency | ChatGPT (1) | 03:04–08:28 PM (5h24m) | Partial outage (Work mode unavailable for Plus) | Resolved, write-up published |
### Incidents on OpenAI's status page · 14 days since Aug 31 | Date | Incident | Components | Duration | Severity | Status | |---|---|---|---|---|---| | Sep 11 | [1% of ChatGPT Work turns failing on existing threads](https://status.openai.com/incidents/01M28MEQWTQJDRCRPFD9FWQ0H3) | ChatGPT (1) | 04:22 PM, ongoing ~5.5h | Degraded performance | Monitoring (open) | | Sep 11 | [Elevated errors for GPT-5.6 Sol on the API](https://status.openai.com/incidents/01M27VK1VN54RQJGJEHB5JTQJJ) | APIs (2): Chat Completions, Responses | 09:08–11:21 AM (2h13m) | Degraded performance | Resolved | | Sep 11 | [Elevated errors for ChatGPT users in Europe](https://status.openai.com/incidents/01M27Q9GH7WVKNA61ZR3RDMSY5) | ChatGPT (1) | 07:53–10:16 AM (2h23m) | Degraded performance | Resolved | | Sep 10 | [Delays in customer support responses](https://status.openai.com/incidents/01M26E3PPAYJMMRHX2MZJCTHMF) | none marked | 07:53–09:48 PM (1h55m) | No severity set | Resolved | | Sep 10 | [Elevated errors affecting ChatGPT Work](https://status.openai.com/incidents/01M26DX2PP1AFHGJK5E4M6S2J6) | ChatGPT (1) | 07:49–09:30 PM (1h41m) | Degraded performance | Resolved | | Sep 10 | [Shared ChatGPT Project not opening via direct link](https://status.openai.com/incidents/01M24HYC9SX2Q4471EVMY6EXQE) | ChatGPT (1) | 02:21 AM–02:28 PM (12h07m) | Degraded performance | Resolved | | Sep 9 | [Unexpected Codex usage limit resets](https://status.openai.com/incidents/01M23KG62KKK448RN434CQ64Z8) | none marked | 05:29–05:54 PM (25m) | No severity set | Resolved | | Sep 9 | [Increased error rate for Pro and Plus conversations](https://status.openai.com/incidents/01M23BNX5V1XT9P3NP0PX56FTN) | ChatGPT (1) | 02:51–04:21 PM (1h30m) | Degraded performance | Resolved | | Sep 8 | [Elevated errors for image generation](https://status.openai.com/incidents/01M20PYYYGRT9303VHAPA7YNT2) | ChatGPT (1) + APIs (1, Images) | 02:32–09:59 PM (7h27m) | Degraded performance | Resolved | | Sep 8 | [File uploads delayed or failing](https://status.openai.com/incidents/01M20QBACYZMK2PRCJQCBSWTYJ) | ChatGPT (2) | 02:39–07:16 PM (4h37m) | Degraded performance | Resolved | | Sep 4 | [APAC errors across ChatGPT, Work, images, uploads, Voice, Codex Cloud](https://status.openai.com/incidents/01M1NKFZH5EEYEREC54HNAHY35) | ChatGPT (4), Codex (1) | 07:00–10:46 AM (3h46m) | Degraded performance | Resolved | | Sep 3 | [Elevated errors across ChatGPT and Codex](https://status.openai.com/incidents/01M1KWEDH417T2CF44YYHZDFCR) | ChatGPT (15), Codex (4) | 02:43–04:55 PM (2h12m) | Degraded performance | Resolved, write-up published; some Codex remote-control users had to re-pair | | Sep 3 | [ChatGPT Work Mode high error rates](https://status.openai.com/incidents/01M1J99EDCYED5GP2W8GZ3N2NA) | ChatGPT (15) | 12:04–12:10 AM (6m) | Partial outage | Resolved, write-up published | | Sep 2 | [Elevated errors creating new accounts](https://status.openai.com/incidents/01M1HN7GRR6FJNWFVX2F8QMA3R) | none marked | 06:13–06:45 PM (32m) | No severity set | Resolved, write-up published | | Aug 31–Sep 1 | [Elevated latency in the Responses API](https://status.openai.com/incidents/01M1CYZDD84XD0H56XNEV2PT98) | APIs (1, US endpoint) | Aug 31 10:27 PM–Sep 1 07:05 PM (~20h38m) | Degraded performance | Resolved | | Sep 1 | [Elevated errors for Free and Go conversations](https://status.openai.com/incidents/01M1D6E14BQSYQA3R5CNQBB7EB) | ChatGPT (1) | 12:38–01:00 AM (22m) | Degraded performance | Resolved, write-up published | | Aug 31 | [ChatGPT Work elevated errors and latency](https://status.openai.com/incidents/01M1C5M4K0WC8PPT0Z175RJA1E) | ChatGPT (1) | 03:04–08:28 PM (5h24m) | Partial outage (Work mode unavailable for Plus) | Resolved, write-up published |