WeVideo Outage History

Started Oct 21, 2026, 01:31 PM UTC· resolved Oct 21, 2026, 03:49 PM UTC

1. investigating Oct 21, 2026, 01:31 PM UTC

   PlayPosit is temporarily offline while our team applies an urgent security update to our servers. This update addresses a recently disclosed vulnerability in PHP, a core component used by many web applications. During this maintenance window, access to PlayPosit—including logging in directly and launching activities via your LMS—will be unavailable. Please note that this is a proactive precautionary measure. There is no evidence that PlayPosit systems or user data have been compromised. All of your bulbs, classes, and student response records remain secure and will be fully available once service is restored. We are working to complete this maintenance as quickly as possible and will post status updates as they become available. We sincerely apologize for any inconvenience or disruption this may cause to your school day.

2. investigating Oct 21, 2026, 02:15 PM UTC

   PlayPosit is temporarily offline while our team applies an urgent security update to our servers. We are immediately addressing a recently disclosed vulnerability in PHP, a core component used by many web applications. During this maintenance window, access to PlayPosit—including logging in directly and launching activities via your LMS—will be unavailable. This impacts existing PlayPosit as well as any migrated PlayPosit customer to WeVideo where they rely upon content created prior to migration (newly created content in WeVideo is unaffected). Please note that this is a proactive precautionary measure. There is no evidence that PlayPosit systems or user data have been compromised. All of your bulbs, classes, and student response records remain secure and will be fully available once service is restored. We are working to complete this maintenance as quickly as possible and will post status updates as they become available. We sincerely apologize for any inconvenience or disruption this may cause to your school day.

3. monitoring Oct 21, 2026, 02:56 PM UTC

   Our PlayPosit servers are back online and fully operational. We temporarily took the PlayPosit servers offline for a short time earlier today to apply a critical PHP patch. This was precautionary in nature, and applied to protect your security and privacy above all else.The issue is completely resolved, and our team is continuously monitoring our systems as well as support tickets. There is no evidence of any data breach or compromise. Thank you for your patience & understanding.

4. monitoring Oct 21, 2026, 02:57 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Oct 21, 2026, 03:49 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 26, 2026, 01:05 PM UTC· resolved Aug 26, 2026, 03:01 PM UTC

1. investigating Aug 26, 2026, 01:24 PM UTC

   We are currently investigating the issue

2. identified Aug 26, 2026, 01:52 PM UTC

   The issue has been identified and a fix is being implemented.

3. identified Aug 26, 2026, 01:59 PM UTC

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

4. monitoring Aug 26, 2026, 02:02 PM UTC

   A fix has been implemented and we are monitoring the results.

5. resolved Aug 26, 2026, 03:01 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 27, 2026, 08:48 PM UTC· resolved Jul 28, 2026, 07:44 AM UTC

1. investigating Jul 28, 2026, 06:33 AM UTC

   We are getting reports and seeing issues with the monitoring page not loading for instuctors.

2. investigating Jul 28, 2026, 06:37 AM UTC

   We are investigating reports that the Monitor page for interactive videos does not load for instructors. Affected users see an "Unable to get bulb assignment data" error and no assignment data appears. This occurs both when the video is opened through an LMS (Moodle, Canvas) and when opened directly from the WeVideo dashboard. Account administrators are not affected. No reports of impact to video playback, editing, recording, or student submissions.

3. identified Jul 28, 2026, 06:38 AM UTC

   We have identified the cause. A change included in our latest release caused the Monitor page to request assignment data from an endpoint restricted to account administrators. Instructor accounts receive a permissions error and the page loads no data. Existing assignment and submission data is unaffected; this is a read failure only. We are preparing a fix.

4. identified Jul 28, 2026, 06:40 AM UTC

   A fix is in progress. Affected customers can contact our support team to apply an account level workaround that restores the Monitor page for affected instructors.

5. identified Jul 28, 2026, 06:41 AM UTC

   The fix has been written and is currently being tested before release.

6. identified Jul 28, 2026, 06:43 AM UTC

   To avoid any additional disruption, an additional testing round is taking place with a patch to production aimed during evening-night US time.

7. identified Jul 28, 2026, 06:44 AM UTC

   The fix is currently being staged for production and we'll be released as soon as it passes all checks.

8. monitoring Jul 28, 2026, 07:42 AM UTC

   The fix has been patched to production. We'll continue monitoring.

9. resolved Jul 28, 2026, 07:44 AM UTC

   Production testing has completed and the Issue is considered resolved.

Read the full incident report →

Started Oct 20, 2025, 09:31 AM UTC· resolved Oct 21, 2025, 03:40 AM UTC

1. monitoring Oct 20, 2025, 12:31 PM UTC

   WeVideo services might continue to experience degraded performance and intermittent availability issues due to an ongoing outage affecting Amazon Web Services (AWS) infrastructure in us-east-1. We're monitoring https://health.aws.amazon.com/health/status for updates.

2. monitoring Oct 20, 2025, 03:38 PM UTC

   AWS continues to see significant API errors and connectivity issues across multiple services in the US-EAST-1 Region. Right now the impacted services grew back up to more than 80, including the ones we need to ensure system operability. https://health.aws.amazon.com/health/status

3. monitoring Oct 20, 2025, 05:15 PM UTC

   AWS continues to see significant API errors and connectivity issues across multiple services in the US-EAST-1 Region. Right now the impacted services grew back up to more than 80, including the ones we need to ensure system operability. https://health.aws.amazon.com/health/status

4. monitoring Oct 20, 2025, 05:17 PM UTC

   AWS is still working to resolve the issue and has hinted at a potential fix. We expect their next update by 10:45 AM PDT and will keep you posted. Our service is functioning with interruptions. You're likely to experience slow loading or errors. Due to the AWS outage, we're currently unable to add more server resources to handle the load, which means things will be slower than usual. If possible, you may want to wait until the issue is fully resolved for the best experience. We're continuously monitoring our infrastructure and https://health.aws.amazon.com/health/status for updates.

5. monitoring Oct 20, 2025, 07:15 PM UTC

   AWS reports significant progress. They're seeing improvements with their systems and fewer errors across the board. We're also seeing improvements on our side with reduced errors and better stability. Things should continue to improve as AWS completes their recovery.

6. monitoring Oct 21, 2025, 03:37 AM UTC

   AWS reported the Increased Error Rates and Latencies incident was resolved. All WeVideo services are functional and stable. Users may still experience processing jobs, such as exporting, subtitling, being stuck in an invalid state. We recommend cancelling and restarting them.

7. resolved Oct 21, 2025, 03:40 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 20, 2025, 07:00 AM UTC· resolved Oct 20, 2025, 07:00 AM UTC

1. resolved Oct 20, 2025, 09:56 AM UTC

   WeVideo services experienced degraded performance and intermittent availability issues due to an ongoing outage affecting Amazon Web Services (AWS) infrastructure in us-east-1. This external incident impacted our ability to serve requests, process jobs, and maintain stable connections to core services.

Read the full incident report →

Started Aug 28, 2025, 08:17 PM UTC· resolved Aug 28, 2025, 09:49 PM UTC

1. investigating Aug 28, 2025, 08:35 PM UTC

   We are experiencing Bad Requests in the Interactivity module, when trying to create or edit interactive videos. Investigating.

2. investigating Aug 28, 2025, 08:44 PM UTC

   We are rolling out a patch and expanded our server resources to stabilize the platform. This has resulted in a significant reduction in errors, and performance should be improving for most users. Our team is closely monitoring the effectiveness of these measures while we continue to investigate the root cause.

3. identified Aug 28, 2025, 08:51 PM UTC

   Root cause identified: an unstructured error log message includes a request parameter that the logging system is misinterpreting as a timestamp. The patch that is being rolled out provides the correct fix.

4. investigating Aug 28, 2025, 08:57 PM UTC

   Testing the patch identified an additional issue that we are currently investigating.

5. identified Aug 28, 2025, 09:05 PM UTC

   Patch updated and is being rolled out to production after passing internal testing.

6. monitoring Aug 28, 2025, 09:38 PM UTC

   The patch has been rolled out to production, after passing internal tests. We'll continue to monitor.

7. resolved Aug 28, 2025, 09:49 PM UTC

   The partial outage has been resolved.

Read the full incident report →

Started Nov 21, 2024, 12:49 PM UTC· resolved Nov 21, 2024, 01:12 PM UTC

1. investigating Nov 21, 2024, 12:49 PM UTC

   We are currently investigating this issue.

2. investigating Nov 21, 2024, 12:52 PM UTC

   We are continuing to investigate this issue.

3. identified Nov 21, 2024, 01:04 PM UTC

   The issue has been identified and a fix is being implemented.

4. monitoring Nov 21, 2024, 01:06 PM UTC

   A fix has been implemented and we are monitoring the results.

5. resolved Nov 21, 2024, 01:12 PM UTC

   This incident has been resolved.

Read the full incident report →