Delayed AI Responses
resolved- Started
- Aug 31, 11:00 AM EDT
- Resolved
- Aug 31, 11:27 PM EDT
- Duration
- 12h 27m
Decagon's updates (5)
- update · Aug 31, 11:00 AM EDT
We've identified an issue causing delays or interruptions for some conversations. We've identified the cause and are actively working to resolve it. We'll provide an update within 30 minutes.
- update · Aug 31, 12:32 PM EDT
We are continuing to investigate this issue. We will provide more updates in 30 minutes.
- update · Aug 31, 2:20 PM EDT
We are continuing to investigate this issue. We will provide more updates as we work towards a confirmed resolution.
- update · Aug 31, 4:50 PM EDT
The errors from this issue have been resolved. Some customers may still experience elevated response latency, specifically at the higher end (P95+) of end-to-end response times, while we wait for full resolution from our upstream AI provider. We're continuing to monitor and will post again once we've confirmed full recovery.
- resolved · Aug 31, 11:27 PM EDT
This has been resolved. We’ll continue to monitor and will provide a preliminary post-incident review upon request within 48hrs.
What our checks recorded
We checked Decagon 150 times from Decagon's start time to its resolution, once every five minutes. Every one of them reached Decagon's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 108 ms, against 150 ms over the 24 hours before. Decagon posted the incident at Aug 31, 11:00 AM EDT.
Updates are Decagon's own words from its status page (status: resolved); we never add an inferred cause.