Plugins Locked. Daybreak Says No. Again.
On Friday, October 9, OpenAI rated a ChatGPT workspace plugin problem a major incident. Overnight, users of its Daybreak program said they were being turned away again.
A home office desk, shown for illustration. Photo: Free-Photos via Pixabay, CC0, via Wikimedia Commons.
Friday was a busy afternoon on OpenAI's status page. At 2:48 PM Pacific on October 9, the company opened an incident titled "Workspace admins may be unable to manage plugins" and rated it major. It was the second major ChatGPT incident of the afternoon, landing while the Android "content unavailable" problem we covered yesterday was still open.
What OpenAI said
According to the first update, some ChatGPT workspace administrators couldn't view or manage plugin availability and settings, and some users may also have seen plugins as unavailable. At 3:52 PM OpenAI said it was seeing recovery and was monitoring. At 4:26 PM it marked the incident resolved. That's 98 minutes from first post to all clear for the people who pay for ChatGPT on behalf of a whole team.
The Android incident finally closed too. OpenAI marked "Some ChatGPT content may be unavailable on Android" resolved at 5:26 PM Pacific, about three and a half hours after it was first posted.
There's a slower one still running. Since 10:23 AM Friday, OpenAI has been reporting delays in organization cost data through its Compliance API. At 3:03 PM it said a mitigation was in place, but that some customers may keep seeing incomplete cost data while the backlog catches up, a process it expects to run through Sunday, October 11. OpenAI says ChatGPT usage and API requests themselves aren't affected.
Daybreak users say the lockout is back
This part isn't on the status page. On the OpenAI Community forum late Friday night, a user posting as pakung wrote about Daybreak restrictions: "Yesterday they fixed it, and now they've brought it back again."
A few hours later another user, posting as devdanmuji, described a ChatGPT Business account in South Korea with Advanced Account Security turned on and a physical YubiKey registered since October 6. Every visit to chatgpt.com/cyber, the post says, ends with "This account is not currently eligible for Daybreak," before the user ever reaches identity verification. The user says OpenAI Support replied that the message can reflect an eligibility or availability outcome and that Support can't override it or explain the decision. As of October 10, nothing had changed.
We can't tell from the outside whether those are individual eligibility decisions or a bug. But being told no, with no reason and no appeal, after doing every security step OpenAI asked for, is exactly the kind of experience people write to us about.
What you can do
Workspace admins should recheck plugin settings now that the incident is resolved, since some users saw plugins as unavailable while it was open. If your organization relies on Compliance API cost data, expect gaps through Sunday. We'll keep tracking all of it on the status tracker.
Sources: OpenAI status, Workspace admins may be unable to manage plugins; OpenAI status, Some ChatGPT content may be unavailable on Android; OpenAI status, Delayed Costs data in the Compliance API; OpenAI Community, The restrictions on Daybreak came back; OpenAI Community, Daybreak says account isn't currently eligible. All read October 10, 2026.