Bitmovin - Notice history

The issue affecting Bitmovin Encoding has been resolved, and full functionality has been restored.

Our systems are stable, and we are no longer observing any errors or delays.

A Root Cause Analysis (RCA) will follow once our internal review is completed. Thank you for your patience throughout this disruption.

We apologize for all customers that were affected by this outage, unfortunately failed encodings cannot be restarted on our side but need to be recreated in your workflow.

A fix has been implemented, and we are currently monitoring the system to ensure full recovery.

Early indicators are positive, but we are validating to confirm that services are fully restored.

We will provide a final resolution update shortly.

We have identified the root cause and our Engineering team is actively working on implementing a fix for the identified issue impacting encoding start calls.

We are making progress and will share an update as soon as validation is underway or the fix is rolled out.

Thank you for your continued understanding.

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.

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.