Livepeer Studio Outage History

Started Feb 13, 2026, 06:32 PM UTC· resolved Feb 13, 2026, 08:17 PM UTC

1. investigating Feb 13, 2026, 06:32 PM UTC

   We are currently investigating this issue.

2. resolved Feb 13, 2026, 08:17 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 06, 2026, 09:54 PM UTC· resolved Feb 07, 2026, 12:15 AM UTC

1. investigating Feb 06, 2026, 09:54 PM UTC

   Logging into the Livepeer Studio dashboard is down at the moment, and we are investigating into this issue

2. investigating Feb 06, 2026, 09:54 PM UTC

   We are continuing to investigate this issue.

3. identified Feb 06, 2026, 10:06 PM UTC

   An issue with an upstream provider has been identified and their support has been engaged.

4. identified Feb 06, 2026, 10:15 PM UTC

   Our upstream provider has confirmed the issue on their end and has escalated the issue to their engineering team

5. identified Feb 07, 2026, 12:12 AM UTC

   We are continuing to work on a fix for this issue.

6. identified Feb 07, 2026, 12:13 AM UTC

   Our upstream provider's engineers have resolved the issue on their end, normal service has been restored

7. resolved Feb 07, 2026, 12:15 AM UTC

   Our upstream provider's engineers have resolved the issue on their end, normal service has been restored

Read the full incident report →

Started Nov 18, 2025, 11:30 AM UTC· resolved Nov 18, 2025, 05:47 PM UTC

1. identified Nov 18, 2025, 01:16 PM UTC

   Due to an issue with a third party provider we are seeing very high error rates for Studio API and the Dashboard.

2. monitoring Nov 18, 2025, 02:46 PM UTC

   Service has been restored by the third party, however there have been periods of intermittent downtime so we're monitoring very closely in case any issues occur again.

3. monitoring Nov 18, 2025, 02:48 PM UTC

   Service has been restored by the third party, however there have been periods of intermittent downtime so we're monitoring very closely in case any issues occur again.

4. resolved Nov 18, 2025, 05:47 PM UTC

   This incident has been resolved.

5. postmortem Nov 19, 2025, 06:32 PM UTC

   ## Postmortem ## **Livepeer Studio Outage** **Date:** 11/18/25 **Time:** 17:47 UTC **Summary:** The outage was triggered by an incident with our upstream hosting provider, which led to issues and disrupted access to Livepeer Studio services. After identifying the root cause, the team implemented corrective measures, closely monitored the resolution, and verified that all platform services were fully restored. **Impact:** * Users were unable to stream, upload VODs, or play back existing streams in Livepeer Studio. * Developers could not create livestreams or upload assets via the Livepeer Studio API. * Daydream users relying on Studio playback experienced interruptions and could not view their streams. **Prevention:** To reduce the risk of similar incidents, the team is evaluating the use of a secondary hosting provider as a fallback plan.

Read the full incident report →

Started Nov 03, 2025, 05:56 PM UTC· resolved Nov 04, 2025, 02:16 AM UTC

1. investigating Nov 03, 2025, 05:56 PM UTC

   Some users may experience a message indicating that this website has been temporarily rate-limited when trying to log in to Livepeer Studio. This also affects the ability to use the api and the dashboard. We are currently investigating this issue.

2. resolved Nov 04, 2025, 02:16 AM UTC

   This incident has been resolved.

3. postmortem Nov 04, 2025, 09:23 PM UTC

   ## Postmortem **Temporarily rate-limited Incident** **Date:** 11/3/25 **Time:** 11:36 AM EST **Summary:** The incident was caused by DNS issues that disrupted normal service operations. After identifying the root cause, the team implemented a fix, monitored the resolution to ensure stability, and confirmed that all services were fully restored. **Impact:** During the incident, users of the Livepeer Studio API and Dashboard were unable to access the dashboard interface, initiate or manage livestreams, upload assets, or use multi-streaming functionality. **Prevention:** To mitigate future occurrences, the team will increase the frequency of audits on DNS services, improve DNS health monitoring, and improve configuration change controls to ensure prompt detection and resolution of potential issues before they impact users.

Read the full incident report →

Started Apr 25, 2025, 08:07 PM UTC· resolved Apr 25, 2025, 08:23 PM UTC

1. investigating Apr 25, 2025, 08:07 PM UTC

   Our storage provider informed us that certain regions in the US might experience uploading unsuccessfully briefly. We will update as we get new information.

2. resolved Apr 25, 2025, 08:23 PM UTC

   Got confirmation that we were not impacted by this incident.

Read the full incident report →

Started Dec 19, 2024, 03:51 PM UTC· resolved Dec 19, 2024, 05:18 PM UTC

1. investigating Dec 19, 2024, 03:51 PM UTC

   There are some servers not responding, we are currently investigating the root cause.

2. resolved Dec 19, 2024, 05:18 PM UTC

   We have isolated the issue and implemented a fix.

3. postmortem Dec 19, 2024, 06:30 PM UTC

   # Incident on 12/19/2024 ‌ **Overview** On Thursday, December 19th, 2024, an issue arose with live streams and video-on-demand \(VOD\) while operating on our infrastructure, resulting in disruptions across the New York, Chicago, Miami, and Madrid regions. The problem impacted streaming services and user experience within these regions. **Incident Details** An issue within the Livepeer infrastructure triggered the disruption during ongoing maintenance and configuration updates. This caused interruptions in services, including: * **Streaming Availability**: Users in the New York, Chicago, and Miami regions experienced interruptions or inability to access streams. * **VOD Availability**: Users in the Madrid region experienced interruptions or inability to upload or access videos. * **Playback Availability**: * Some livestream playback sessions failed to start, disconnected unexpectedly, or experienced buffering. * Some assets were not able to be playback. ### **Resolution** After identifying the root cause our team implemented a fix. The solution addressed the service disruptions and restored normal operations across all affected regions. ### **Mitigation Steps** To mitigate the impact and ensure a smooth recovery, we: * **Isolated Affected Services**: Redirected workloads to unaffected regions to minimize user impact. * **Applied Fixes**: Implemented configuration updates and restarted the affected service in the affected regions. * **Monitored Service Restoration**: Closely monitored infrastructure recovery to ensure stability. **Root Cause** * **Primary Cause**: Configuration changes in Livepeer infrastructure triggered service disruptions. ### **Impact Assessment** * **Users Affected**: Users in New York, Chicago regions experienced streaming interruptions. * **Service Downtime**: Approximately 3 hours before all services were fully restored. * **Impact Scope**: Regional degradation of streaming services with no data loss reported. **Next Steps** * To prevent configuration changes from impacting Livepeer’s service, we will prioritize implementing processes and tools to monitor, validate, and maintain stability both during and after these changes.

Read the full incident report →

Started Nov 08, 2024, 05:02 PM UTC· resolved Nov 14, 2024, 05:00 PM UTC

1. identified Nov 08, 2024, 05:02 PM UTC

   One of our service provider is currently addressing issues that is affecting links to view playback for accessing assets. They are aware of this impact on our service and is working to resolve this as soon as possible. At the moment, links being used to access assets is currently not working. We are in close communication with them and will update when we hear something.

2. identified Nov 11, 2024, 02:34 PM UTC

   The links to clips and Vods are up again and running. Currently, the path to thumbnails are still being worked on. We will continuing to resolve this as soon as we can.

3. resolved Nov 14, 2024, 05:00 PM UTC

   This incident has been resolved.

4. postmortem Nov 14, 2024, 05:01 PM UTC

   ### **Overview** On Friday, November 8, 2024, our storage provider experienced a disruption in service across the North American and European regions. This affected our asset links, causing failures for video-on-demand \(VOD\), clipping, thumbnails, and livestream recordings. ### **Incident Details** The outage stemmed from an issue with our storage provider’s services. After their investigation, they reported that links for assets were inaccessible due to a broader regional service outage. Specific impacts included: * **Link Accessibility** * Links generated for VODs, clipping, thumbnails, and livestream recordings were inaccessible, returning an “Access Denied” error. * **Asset Generation** * No new assets \(including clips, recordings, and thumbnails\) were generated during the incident window. ### **Resolution** Once the storage provider resolved the regional outage, our services began to be restored. However, we discovered that a high volume of requests repeatedly hit our livestream thumbnail link path. This request rate exceeded the provider’s limits, resulting in blocking our account. We have implemented a solution to reduce the number of requests, restore livestream thumbnail functionality, and unblock our account.. ### **Mitigation Steps** To minimize service impact and restore functionality, we: * Blocked access to the shared link path specifically for livestream thumbnails, allowing VOD, clipping, and recording paths to function as usual. * Implement a rate limit on the livestream thumbnail path once the request volume normalizes. ### **Root Cause** * **Primary Cause**: Storage provider outage in North America and Europe. * **Secondary Cause**: Excessive requests to the livestream thumbnail path following service restoration, triggering a rate-limit response from the provider. ### **Impact Assessment** * **Users Affected**: Users attempting to access VOD, clipping, thumbnails, and livestream recordings received an “Access Denied” error. * **Service Downtime**: Approximately 12\+ hours, with the issue partially resolved upon blocking the livestream thumbnail path. ### **Follow-up Actions** * **Implement Rate Limiting** * Deploy CDNs in front of the targeted links to manage and distribute incoming requests efficiently. * **Monitoring and Alerts** * Set up monitoring for high request volumes on specific asset paths to detect and address potential bottlenecks before they impact service.

Read the full incident report →