ElevenLabs incident

Post-Call Webhook Schema Missing conversation_id

Minor Resolved View vendor source →
Started
Feb 10, 2026, 10:15 PM UTC
Resolved
Feb 10, 2026, 10:15 PM UTC
Duration
Detected by Pingoru
Feb 10, 2026, 10:15 PM UTC

Affected components

Other API endpoints

Update timeline

  1. identified Feb 10, 2026, 08:13 PM UTC

    Status: Identified At 18:30 UTC, an unintentional change resulted in conversation_id not being included as a field within Post Call Transcript webhooks. As a temporary workaround, we advise consuming it from conversation_initiation_client_data.dynamic_variables.system__conversation_id, if possible. We are currently working on a fix to address this. Affected components Other API endpoints (Partial outage)

  2. resolved Feb 10, 2026, 10:15 PM UTC

    Status: Resolved The fix to resolve the missing conversation_id in Post Call Transcripts has been successfully deployed. A detailed RCA will be published later. Affected components Other API endpoints (Operational)

Looking to track ElevenLabs downtime and outages?

Pingoru polls ElevenLabs's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when ElevenLabs reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track ElevenLabs alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring ElevenLabs for free

5 free monitors · No credit card required