3 ms·
It sounds a lot like a cache issue (CDN caching something from the API layer? new cache sharding? run out of keyspace?). In addition to users reporting other u
by bcjordan 4y ago
It sounds a lot like a cache issue (CDN caching something from the API layer? new cache sharding? run out of keyspace?).
In addition to users reporting other users' summaries, this user and two others report seeing someone else's email address in their pay-to-upgrade flow: https://old.reddit.com/r/ChatGPT/comments/11wkw5z/has_chatgpt_or_me_been_hacked_ive_never_had_these/jcyhyit/ https://old.reddit.com/r/ChatGPT/comments/11wkw5z/has_chatgp...
> When I'm finally able to get the option to upgrade to Plus to work, the contact email is not the email address I used to subscribe. And you can't change it.
> EDIT: Got it to load again, and it's a completely different email address now. If I pay, who am I paying for?
Which all makes me feel like this could be APIs getting over-cached.
Incident status at https://status.openai.com/incidents/jq9232rcmktd https://status.openai.com/incidents/jq9232rcmktd
> We are investigating an issue with the ChatGPT web experience.
I swear every successful web company has had their cache leaking issues moment right after they've hit product market fit and began scaling up. They've made the big time!
- AgentME 4y agoThis issue pops up somewhat commonly with web services that decide to add a reverse-proxy CDN but don't put the "Cache-Control: private" header on all HTTP endpoints that return data specific to the logged in user.