Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- An admin seeing the list, opening settings and a member completing the original operation are separate results.
- The October 2026 incident affected some admins managing plugin availability and settings, and some members seeing plugins as unavailable.
- The incident was resolved on October 9 at 23:26 UTC. The earlier Monitoring update was an observation stage.
- The notice did not establish persistent permission changes or announce new migration dates, plan eligibility, fees or compensation.
Separate the admin and member results
In the same workspace normally used to manage plugins, admins should inspect the originally affected list and settings. Record list visibility, whether settings open and any remaining errors separately. A visible list does not establish that every management function works.
Members should return to the same plugin and original task that showed it as unavailable. Record whether the original message persists. A working ChatGPT home screen or admin page does not replace the member’s result.
Inspect the existing state without broadening installation policy, changing member permissions or reconnecting business systems merely to test recovery. Confirm current entry points and eligibility from the workspace’s actual conditions and official guidance. The old incident record does not grant feature access.
What did the October incident affect?
This is a historical case from October 2026. OpenAI recorded that some workspace admins could not view or manage plugin availability and settings, while some members might see plugins as unavailable. The listed component was Connectors/Apps.
The record did not disclose a root cause, affected plans, countries or account counts, or establish that plugins were deleted or persistent permissions changed. Compare a problem today with the actual role, workspace and error; this old notice alone does not establish the same cause.
Monitoring and resolution were separate updates
Investigation began on October 9, 2026 at 21:48 UTC, or October 10 at 05:48 Beijing time. At 22:52 UTC, or 06:52 Beijing time, OpenAI reported recovery in admins’ ability to view and manage availability and settings, and moved the incident to Monitoring.
The incident was marked Resolved at 23:26 UTC, or 07:26 Beijing time, confirming full recovery of affected services. The same incident page still retains that conclusion when checked for this guide. It does not independently verify recovery for every workspace or member.
How should the team resume its existing workflow?
Inspect the original task’s records and saved outputs before resuming unfinished steps under the team’s existing procedures. A plugin becoming visible does not prove that a previous task did nothing. Confirm the outcome of actions that create records or send content before repeating them.
For example, suppose a team used a plugin for a weekly report, then switched to an existing reporting process during the incident. In this hypothetical case, after an admin checks the original settings, members still need to inspect the original task and saved report before deciding what remains. Do not process the same material again just to test recovery.
How should you describe a continuing failure?
Record the time and time zone, client, admin or member role, plugin name and redacted error text. Specify whether the list is missing, settings will not open or the original operation fails. Preserve the distinction between admin and member results.
Check the relevant official incident and report continuing problems through the official support channel you normally use. Redact private conversations, company material, account information and connection credentials from screenshots. This resolution notice did not require disconnecting, reauthorizing or reinstalling plugins, or guarantee those actions would resolve a problem.
Migration schedules, retirement plans, plan eligibility and current workspace policies need their own official guidance. Resolving a service incident does not rewrite those conditions, and this incident page provides no new universal workspace rule.
Sources
Frequently Asked Questions
Does this case mean every workspace can enable plugins?
No. It records a service problem affecting some workspaces, without announcing access for every plan, country or role. Confirm your workspace’s current eligibility and admin policy.
Should I reinstall or reauthorize a plugin to prove recovery?
The notice did not require that. First inspect the existing settings and the same task’s actual result. Do not change a business connection or permission solely to test it.
Did resolution also reset usage or provide compensation?
This incident reported service recovery without announcing usage resets, refunds or compensation. Fees and usage require their own applicable official guidance.