OpenAI Confirms Shared ChatGPT Project Direct-Link Failure: How Teams Should Degrade the Workflow

OpenAI’s status page currently lists “Unable to open shared ChatGPT Project using direct link” as a ChatGPT incident. The incident remains in progress and the page says mitigation is being implemented. This describes a failure opening direct links to shared Projects; it does not mean that every ChatGPT conversation, API request, or project record is unavailable.

For individual users, do not create a replacement Project just because a link fails. For teams, temporarily replace “click the link to enter the workspace” with “open from the workspace list plus an approved backup for source material.” Preserve the original URL, timestamp, and error details while the status page changes; repeated refreshes and duplicate work can make the incident worse operationally.

Latest status: the incident is resolved

When OpenAI Status was rechecked at 08:03 China Standard Time on September 11, 2026, it reported “Fully operational” and said it was not aware of issues affecting its systems. The direct-link incident is therefore no longer shown as publicly ongoing. Teams should still verify their own Project access and permissions rather than treating a service recovery as a guarantee of future availability.

After recovery, open the original Project and confirm that recent tasks, source material, and shared members are present. If a temporary duplicate was created during the incident, compare versions before archiving anything. Use OpenAI Status as the source of truth for future changes.

Confirmed facts

• OpenAI’s official status page marks ChatGPT as the affected component.
• The incident is named “Unable to open shared ChatGPT Project using direct link.”
• The status page says the incident is ongoing and mitigation is being implemented.
• The public status information does not currently state the number of affected users, confirm data loss, or provide a recovery time.

What to do now

1. Try the workspace list: if the Project is still visible in ChatGPT’s project list, open it there. A failed deep link is not evidence that the Project was deleted.
2. Preserve evidence: record the original URL, time, account/workspace type, client or browser version, and the error. Do not put credentials in a ticket or content record.
3. Avoid duplicate Projects: have one person confirm whether the original still exists before creating a copy. Otherwise the team can split work across divergent versions.
4. Use an approved fallback: put time-sensitive source material, task instructions, and approvals in an approved team document or ticket, clearly labeled as a temporary degraded path.
5. Follow the official status page: do not promise a recovery time based on social posts or informal reports.

Engineering reminder for AI product teams

A shared link is an entry point, not a sole source of state or permission truth. Internal workflows that depend on ChatGPT Project links should include:

• a workspace/project-list fallback;
• idempotent retries and human confirmation when a link fails;
• independent audit records for task inputs, outputs, and approvals;
• a rule that a page opening is not proof that work was saved or executed;
• a post-recovery check for duplicate tasks, version conflicts, and permission changes.

Claims you should not make

• This is not an official confirmation of a full ChatGPT outage, an API outage, or data loss.
• OpenAI has not published a definitive recovery time on the status page, so do not promise one.
• A failed direct link does not prove that a Project was deleted or that sharing permissions are misconfigured.
• This article does not claim independent uptime monitoring or an SLA test of OpenAI services.

Sources

• OpenAI official status page: OpenAI Status
• OpenAI official history: Status History

This article structures the public incident information on OpenAI’s status pages. Follow the status page for subsequent updates.