WeVideo Outage History

WeVideo is up right now

WeVideo had 6 outages in the last 2 years totaling 32h 55m of downtime — averaging 0.2 incidents per month.

There were 6 WeVideo outages since November 21, 2024 totaling 32h 55m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.wevideo.com

Minor August 26, 2026

Application unresponsive caused by a DB CPU spike

Detected by Pingoru
Aug 26, 2026, 01:05 PM UTC
Resolved
Aug 26, 2026, 03:01 PM UTC
Duration
1h 55m
Affected: APIWebsiteWeb appRendering service
Timeline · 5 updates
  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 →

Major October 20, 2025

Degraded Performance Due to AWS Outage

Detected by Pingoru
Oct 20, 2025, 09:56 AM UTC
Resolved
Oct 20, 2025, 07:00 AM UTC
Duration
—
Timeline · 1 update
  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 →

Major October 20, 2025

Degraded Performance due to AWS us-east-1 outage

Detected by Pingoru
Oct 20, 2025, 09:31 AM UTC
Resolved
Oct 21, 2025, 03:40 AM UTC
Duration
18h 9m
Affected: APIWeb appRendering service
Timeline · 7 updates
  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 →

Major August 28, 2025

Bad Requests in Interactivity module

Detected by Pingoru
Aug 28, 2025, 08:17 PM UTC
Resolved
Aug 28, 2025, 09:49 PM UTC
Duration
1h 31m
Affected: Web app
Timeline · 7 updates
  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 →

Critical November 21, 2024

Application unresponsive

Detected by Pingoru
Nov 21, 2024, 12:49 PM UTC
Resolved
Nov 21, 2024, 01:12 PM UTC
Duration
22m
Affected: APIWebsiteWeb appRendering service
Timeline · 5 updates
  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 →