CelestiQ incident

Degraded Conversational Agent Response Quality

Minor Resolved View vendor source →

CelestiQ experienced a minor incident on September 2, 2026 affecting Chat API and AI Services, lasting 1h 30m. The incident has been resolved; the full update timeline is below.

Started
Sep 02, 2026, 05:16 PM UTC
Resolved
Sep 02, 2026, 06:47 PM UTC
Duration
1h 30m
Detected by Pingoru
Sep 02, 2026, 05:16 PM UTC

Affected components

Chat APIAI Services

Update timeline

  1. identified Sep 02, 2026, 05:16 PM UTC

    Status: Identified We are currently experiencing issues with our primary conversational API provider. Your agent remains operational and has automatically switched to a secondary provider. This fallback uses a different model, so you may notice slightly reduced response quality or differences in how answers are generated. We are monitoring the situation and will restore the primary provider once service has stabilized. No action is required on your part. Affected components AI Services (Degraded performance) Chat API (Degraded performance)

  2. monitoring Sep 02, 2026, 05:28 PM UTC

    Status: Monitoring We have stabilized our fallback provider and tuned the fallback model to deliver response quality comparable to our primary model. Agents remain on the secondary provider while we continue monitoring our primary conversational API provider. At this time, we do not expect users to experience a meaningful degradation in answer quality. If errors continue, please provide feedback to assist our team. Affected components AI Services (Operational) Chat API (Operational)

  3. resolved Sep 02, 2026, 06:47 PM UTC

    Status: Resolved Our primary conversational API provider has recovered and is now back in place. Agents have been transitioned from the fallback provider back to the primary model, and normal service has been fully restored. We will continue to monitor performance to ensure ongoing stability. Affected components AI Services (Operational) Chat API (Operational)