Kaltura experienced a major incident on January 23, 2023 affecting Kaltura API and Playback and 1 more component, lasting 1d 1h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 23, 2023, 01:41 PM UTC
What is the issue: We have identified issues with KLTR service, general service degradation. Users might experience issues when loading the KMS/KMC/Playback/Player. Current status: Our engineering team is investigating the issue and in progress to mitigate this issue. What to expect next: We will provide another update in 30 minutes.
- identified Jan 23, 2023, 02:11 PM UTC
What is the issue: We have identified issues with KLTR service, general service degradation. Users might experience issues when loading the KMS/KMC/Playback/Player . Current status: Our team identified the issue and is working on a resolution. What to expect next: We will provide an update during the next 30 minutes.
- identified Jan 23, 2023, 02:51 PM UTC
What is the issue: We have identified issues with KLTR service, general service degradation. Users might experience issues when loading the KMS/KMC/Playback/Player. Current status: Our team is actively working on a resolution. What to expect next: The next update will be provided in 30 minutes.
- identified Jan 23, 2023, 03:35 PM UTC
What is the issue: We have identified issues with KLTR service, general service degradation. Users might experience issues when loading the KMS/KMC/Playback/Player . Current status: Investigation is currently in progress, the team is working on mitigating the issue. What to expect next: Next update will be provided in 30 minutes.
- monitoring Jan 23, 2023, 03:59 PM UTC
What is the issue: We have identified issues with KLTR service, general service degradation. Users might experience issues when loading the KMS/KMC/Playback/Player. Current status: Our engineering team identified and mitigated the issue, at this point we are in recovery stage, all components are back to normal and KMS/KMC/Playback/Player loads. What to expect next: Issue has been resolved, we will keep monitoring it and the next update will be provided in 1 hour.
- monitoring Jan 23, 2023, 05:01 PM UTC
What was the issue: We have identified issues with KLTR service, general service degradation. Users might experience issues when loading the KMS/KMC/Playback/Player. Current status: Our engineering team mitigated the issue, at this point we are still in recovery stage. Users might also experience some slowness with thumbnail loading. What to expect next: We keep monitoring all services and will provide another update in 1 hour.
- monitoring Jan 23, 2023, 05:40 PM UTC
What is the issue: We have identified issues with KLTR service, general service degradation. Users might experience issues when loading the KMS/KMC/Playback/Player. Current status: Users may experience intermittent load issues, our engineering team is working on mitigating the issue. What to expect next: We will keep monitoring, the next update will be in 30 minutes.
- monitoring Jan 23, 2023, 06:22 PM UTC
What was the issue: We have identified issues with KLTR service, general service degradation. Users might experience issues when loading the KMS/KMC/Playback/Player. Current status: Our engineering team identified and mitigated the issue, KMS/KMC/Playback/Upload and API components are back to normal and function normally, however, the Thumbnails are still not fully recovered yet. What to expect next: We will keep monitoring, next update will be in 1 hour.
- monitoring Jan 23, 2023, 06:47 PM UTC
What was the issue: We have identified issues with KLTR service, general service degradation. Users might experience issues when loading the KMS/KMC/Playback/Player. Current status: Our engineering team identified and mitigated the issue, all components KMS/KMC/Playback/Upload/Thumbnails/Captions and API are all back to normal and function normally. What to expect next: Issue has been fully resolved, we will keep monitoring the behavior during the next 24 hours and close the incident.
- resolved Jan 24, 2023, 03:27 PM UTC
This incident has been resolved.