D
Outage recap · Decagon

Decagon outage — August 31, 2026

On August 31, 2026, Decagon had 3 reported incidents on Decagon's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

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)

  1. 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.

  2. update · Aug 31, 12:32 PM EDT

    We are continuing to investigate this issue. We will provide more updates in 30 minutes.

  3. 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.

  4. 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.

  5. 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.

Voice Call Errors

resolved
Started
Aug 31, 2:30 PM EDT
Resolved
Aug 31, 2:37 PM EDT
Duration
7 min

Decagon's updates (2)

  1. update · Aug 31, 2:30 PM EDT

    We've identified an issue with a third-party transcription provider that is causing increased call restarts and, for a subset of customers, call failures on voice. We've identified the root cause and are actively working on migrating traffic to resolve the symptoms. We'll provide an update within 30 minutes.

  2. resolved · Aug 31, 2:37 PM EDT

    This issue has been resolved. We’ll continue to monitor and will provide a preliminary post-incident review upon request within 48hrs. Thank you for your patience and understanding.

What our checks recorded

We checked Decagon 2 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 98 ms, against 142 ms over the 24 hours before. Decagon posted the incident at Aug 31, 2:30 PM EDT.

Updates are Decagon's own words from its status page (status: resolved); we never add an inferred cause.

Conversations Not Loading in Dashboard

resolved
Started
Aug 31, 2:56 PM EDT
Resolved
Aug 31, 3:05 PM EDT
Duration
9 min

Decagon's updates (2)

  1. update · Aug 31, 2:56 PM EDT

    We're investigating an issue causing conversations to intermittently fail to load in the dashboard for some customers. This does not affect live conversation handling or agent performance. We're actively looking into the cause and will provide an update within 30 minutes.

  2. resolved · Aug 31, 3:05 PM EDT

    We have identified the root cause of this issue and a fix has been deployed. This issue is now resolved. We’ll continue to monitor and will provide a preliminary post-incident review upon request within 48hrs. Thank you for your patience and understanding.

What our checks recorded

We checked Decagon 1 time 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 98 ms, against 142 ms over the 24 hours before. Decagon posted the incident at Aug 31, 2:56 PM EDT.

Updates are Decagon's own words from its status page (status: resolved); we never add an inferred cause.

AIDownCheck is not affiliated with Decagon. This recap summarizes incidents published on Decagon's official status page.