Bitmovin Outage History
Bitmovin is up right nowBitmovin had 11 outages in the last 2 years totaling 53h 40m of downtime, averaging 0.5 incidents per month.
There were 11 Bitmovin outages since September 4, 2025 totaling 53h 40m of downtime. Each is summarised below. Incident details, duration, and resolution information.
Observability Database Unavailable
Timeline · 4 updates
Bitmovin Observability Querying Issues
Timeline · 2 updates
- investigating Jul 21, 2026, 10:24 AM UTC
We are currently investigating issues for specific observability queries affecting historic datasets. Data ingest is not affected..
- resolved Jul 21, 2026, 01:00 PM UTC
Query operations are back to normal and we continue to monitor the situation. We apologize for any inconvenience caused due to this incident..
Bitmovin Encodings cannot be started
Timeline · 5 updates
Delayed Observability Data Ingestion (US Region)
Timeline · 3 updates
- investigating Jun 07, 2026, 04:37 PM UTC
We are currently investigating connectivity issues between our US datacenter and our central Observability data store happening since 16:26 UTC. As a result, approximately 20% of analytics requests originating in the US are not being ingested in real time. Affected data is being buffered and will be inserted into the database once connectivity is restored, so no data is being lost. Querying of previously ingested data is unaffected. We are working with our cloud providers to identify the root cause and will provide an update as soon as we have more information..
- identified Jun 07, 2026, 04:59 PM UTC
We have identified the cause of the connectivity issue between our US datacenter and our central Observability data store and have failed over to an alternative transport protocol. Real-time ingestion of US analytics data has been fully restored. We are now draining the backlog of buffered data into the database. Some recently buffered records may appear with a short delay until this process completes. No data loss is expected. We will continue to monitor the system and will post a final update once all buffered data has been backfilled..
- resolved Jun 07, 2026, 05:35 PM UTC
This incident is now resolved. As of 17:32 UTC, all buffered data has been successfully backfilled into our central Observability data store, and ingestion has been operating normally on the alternative transport protocol since the failover at 16:52 UTC. There was no data loss. Records buffered during the connectivity issue are now fully available for querying. The incident began at 16:26 UTC and was fully resolved at 17:32 UTC. We apologize for any inconvenience and will follow up with a post-incident review once we have performed a full root cause analysis..
Observability API — Historic Data Queries Returning Empty Results
Timeline · 9 updates
Encoding Job Processing in AWS eu-west-1 (Ireland)
Timeline · 3 updates
- identified Jan 28, 2026, 05:15 PM UTC
Jobs started in AWS eu-west-1 (Ireland) may be affected by an upstream networking issue on AWS EC2..
- monitoring Jan 28, 2026, 05:48 PM UTC
We implemented a fix and are currently monitoring the result..
- resolved Jan 28, 2026, 07:56 PM UTC
This incident has been resolved..
Increased Error Rates on Encoding API
Timeline · 10 updates
Encoding Failures in us-east-1 Due to EC2 Instance Creation Issues
Timeline · 4 updates
- monitoring Oct 20, 2025, 10:30 AM UTC
Since 12:30 UTC on October 20, our encoding service in the us-east-1 region has again been impacted by an AWS issue preventing the creation of new EC2 instances. As a result, new encoding jobs in this region may fail to start. Running encodings on existing capacity are not affected. Workaround: We recommend all customers switch to another cloud region that is not affected or make use of the fallbackRegion setting when creating encodings, as described in our Documentation: . We are monitoring AWS’s recovery efforts closely and will provide further updates as more information becomes available..
- monitoring Oct 20, 2025, 12:58 PM UTC
The incident is still ongoing. Our encoding service in us-east-1 continues to be impacted by AWS EC2 instance creation issues. We are waiting for further updates from AWS and will continue to monitor their recovery efforts. For more detailed and up-to-date information, we recommend customers check the AWS Health Dashboard: In the meantime, we continue to recommend switching to another unaffected cloud region or using the fallbackRegion setting as described in our Encoding Incident Operational Playbook: .
- monitoring Oct 20, 2025, 01:33 PM UTC
The AWS incident affecting EC2 instance creation in us-east-1 is still ongoing. As a result, encoding jobs in this region may continue to fail to start. There are currently no actions we can take on our side until AWS resolves the underlying issue. Therefore, we will pause posting further updates until AWS has marked the incident as resolved. For the latest information, we recommend monitoring the AWS Health Dashboard: In the meantime, we continue to recommend switching to another unaffected cloud region or using the fallbackRegion setting as described in our Encoding Incident Operational Playbook: .
- resolved Oct 20, 2025, 07:48 PM UTC
The AWS incident affecting EC2 instance creation in us-east-1 has been resolved by AWS as of Oct 20 21:48 UTC.
Elevated API Error Rate on Muxing creation
Timeline · 3 updates
Encoding failures on AWS
Timeline · 2 updates
- investigating Sep 04, 2025, 03:45 AM UTC
We are currently experiencing failures with encodings on AWS. Our engineering team is currently investigating the issue.
- resolved Sep 04, 2025, 04:53 AM UTC
We have identified the root cause of the encoding failures: a misconfiguration in our S3 bucket. The S3 configuration has been corrected, and encoding jobs on AWS are now recovering. We are seeing encoding tasks completing successfully again. We are actively monitoring the system to confirm full recovery..