Studio Dashboard Not Available
Timeline · 2 updates
- investigating Feb 13, 2026, 06:32 PM UTC
We are currently investigating this issue.
- resolved Feb 13, 2026, 08:17 PM UTC
This incident has been resolved.
Livepeer Studio had 12 outages in the last 2 years totaling 191h 36m of downtime — averaging 0.5 incidents per month.
There were 12 Livepeer Studio outages since May 20, 2024 totaling 191h 36m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
This incident has been resolved.
Logging into the Livepeer Studio dashboard is down at the moment, and we are investigating into this issue
We are continuing to investigate this issue.
An issue with an upstream provider has been identified and their support has been engaged.
Our upstream provider has confirmed the issue on their end and has escalated the issue to their engineering team
We are continuing to work on a fix for this issue.
Our upstream provider's engineers have resolved the issue on their end, normal service has been restored
Our upstream provider's engineers have resolved the issue on their end, normal service has been restored
Due to an issue with a third party provider we are seeing very high error rates for Studio API and the Dashboard.
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.
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.
This incident has been resolved.
## 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.
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.
This incident has been resolved.
## 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.
Our storage provider informed us that certain regions in the US might experience uploading unsuccessfully briefly. We will update as we get new information.
Got confirmation that we were not impacted by this incident.
We are aware of some users having issues with livestream playback and are investigating at the highest priority
This incident has been resolved.
We have identified an issue causing delays when processing VOD assets. All videos will be correctly processed, but may take longer than usual to complete. The Livepeer engineering team is currently working on a mitigation.
This incident was resolved at approximately 17:00 UTC on the 30th of May. The team has been monitoring since and confirmed that there has been no recurrence.