Anybody else’s Dot completely broken
A user reported their OpenAI Dot was completely broken, not responding to messages and only showing "read" status. Initially, they suspected an outage, but the service came back online at 11:07 am. After reviewing similar bug reports and their personal experience, they concluded they had hit an unpublished, Dot-specific usage limit. Despite OpenAI's use of phrases like "virtually unlimited" and "not count towards your current usage," the user reached a limit after approximately 2 billion tokens in one day, wishing for more transparency.
This report is the first to identify an unpublished, Dot-specific usage limit, unlike OpenAI's public statements about "virtually unlimited" usage.
Time & source
Times shown in UTC
Display time zone: UTC
Local time zone unavailable; showing UTC.
IngestedOffset at this time: UTC+0Oct 4, 2026, 16:00 UTC
- Ingested
- Oct 4, 2026, 16:00
- Source type
- Dev community
Full text isn't available here.
Read at source →