Daily incident

Problems creating raw-tracks recordings

Minor Resolved View vendor source →

Daily experienced a minor incident on January 18, 2023 affecting Recording/Live Streaming, lasting 7h 33m. The incident has been resolved; the full update timeline is below.

Started
Jan 18, 2023, 08:54 PM UTC
Resolved
Jan 19, 2023, 04:27 AM UTC
Duration
7h 33m
Detected by Pingoru
Jan 18, 2023, 08:54 PM UTC

Affected components

Recording/Live Streaming

Update timeline

  1. investigating Jan 18, 2023, 08:54 PM UTC

    We're investigating reports of errors from customers trying to create "raw-tracks" recordings.

  2. identified Jan 18, 2023, 09:27 PM UTC

    We've confirmed an issue preventing the creation of raw-tracks recordings. Other recording types are unaffected, including "cloud" recordings to your own S3 bucket. If you need to record an important call during this incident, you can change the enable_recording property on your domain, room, or meeting token to cloud to make a cloud recording.

  3. identified Jan 19, 2023, 02:18 AM UTC

    We're in the process of deploying updates to resolve this issue. We'll resolve the incident as soon as the fix is live in production.

  4. monitoring Jan 19, 2023, 02:32 AM UTC

    We've deployed new call servers and recording infrastructure to resolve the issue. You should be able to start a raw-tracks recording from any call session that started on or after approximately 02:15 UTC. Existing long-running call sessions may still be running on older call server instances. Those sessions may still experience errors with raw-tracks recordings. Those sessions will automatically move to new call server instances within the next few hours as part of our normal deploy process. We'll resolve this incident when all of the old call server instances have been retired and operations are back to normal.

  5. resolved Jan 19, 2023, 04:27 AM UTC

    This incident has been resolved.