Chatgpt All Deep Research request failed, stuck on "Researching..."

I know VPN isn’t an ideal situation, but it is the current workaround. I will ping the team again, and see what the situation is on resolving this.

(post deleted by author)

The VPN workaround isn’t working for me, I used Tor/Orbot on macOS

I’m not allowed to use VPN in my job… So that’s not a solution for me. Already two weeks and no solution nor an admission of the problem. That’s embarrassing for a high tech company like OpenAI :sweat_smile: .

Curt, thanks for sharing the update and bring some light.

However, this situation raises a few concerns that I think OpenAI should address more clearly. And i hope you could help us on that

First, the workaround currently being suggested, using a VPN to route traffic through the US or EU, is not realistic for many environments. This issue is affecting users on Enterprise plans, which are typically running in controlled corporate environments where installing a random VPN or routing traffic through external regions is often not permitted by security policies.

Second, the OpenAI status page currently says “We’re not aware of any issues affecting our systems.”
Yet this thread has been active for more than a week, multiple users across regions are reporting the same failure, and you mentioned the issue was reproduced internally. The status page already lists incidents that affect only subsets of users, so it seems reasonable that this situation should at least be acknowledged there.

Finally, there hasn’t been any official communication stating that OpenAI is aware of the disruption and actively working on a fix. For teams depending on this functionality, especially enterprise customers, the lack of visibility makes it difficult to understand whether this is being investigated, what regions are affected, and whether any mitigation is planned.

Could you ask the OpenAI team to clarify:

Whether this issue will be acknowledged on the official status page
Whether there is any ETA or progress update on a fix
Whether there is a proper workaround suitable for enterprise environments

Even a brief official note confirming the investigation would help users plan around the disruption, as there is no response from help center.

I forwarded off your concerns, all valid. They can’t share a timeline when the fix will be ready. The engineering team is still looking into it.