Historial de interrupciones de Videoask

At 09:00 CET on the 20th of October, our service experienced an unexpected outage due to an issue with AWS. We understand how much you rely on our service, and we sincerely apologize for any disruption this may have caused. Our team is actively working with AWS to investigate the root cause and ensure that measures are put in place to prevent similar issues in the future. Thank you for your patience and understanding during this time. Your continued support means a lot to us, and we remain committed to providing you with a reliable service.

We are currently investigating an issue where creators cannot log into their VideoAsk accounts via the 'Login with Typeform' option. Apologies for the inconvenience this may be causing.

This incident has now been resolved. Apologies for the inconvenience this may have caused.

Our team is currently investigating an issue where new responses can't be submitted. We appreciate your patience and understanding during this time. Please check back for updates. Thank you for your continued support.

Our technical support team has identified that the problem currently occurs with the Streamed recording method. To resolve this issue promptly, we advise you to switch the recording method in your forms from Streamed to Uploaded. For guidance on switching recording methods, please refer to this article: https://www.videoask.com/help/video-audio/360044119891-what-s-the-difference-between-an-uploaded-recording-and-a-streamed-recording Our team will continue to investigate why the Streamed version is failing. Please check back for updates. Again we appreciate your patience and understanding during this time. Thank you for your continued support.

This incident has been resolved.

We are currently investigating this issue.

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

This incident has been resolved.

We have identified a service interruption impacting videoasks using custom subdomains. We are working on a resolution with highest priority. We're sorry for any inconvenience this is causing.

A fix has been implemented and we are monitoring the results. Thank you for your patience & understanding.

We are glad to inform you that a fix has been implemented and the incident resolved. Thank you

We are currently investigating an issue where some creators cannot log into their VideoAsk accounts via Typeform login.

We are currently investigating an issue where some creators cannot log into their VideoAsk accounts via Typeform login. As a temporary workaround, you should be able to log into VideoAsk via Typeform from a private/Incognito window in your browser.

The issue has been identified and a fix is being implemented. In the meantime, you can use these workarounds to log into your VideoAsk account: - Option #1: Log in using a private/Incognito window in your browser. - Option #2: If you get stuck in an infinite login loop, open your browser's developer console. While you're stuck in the loop, clear your storage for the webpage. Here is a screenshot showing where to find this option in Chrome: https://drive.google.com/file/d/13oUiGTyY9yOARTI0POTqwtaaR89FcRt7/view?usp=sharing

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

This incident has been resolved.

We are currently investigating an issue where responses submitted by a respondent are not appearing in the creator's inbox. This outage is also impacting webhooks and email notifications.

A fix has been implemented and we are monitoring the results. VideoAsk should start functioning normally in approximately 30 minutes. Responses and replies that were sent during the outage should appear in your inbox shortly.

This incident has been resolved.

Our services are currently experiencing an interruption, and we are actively working to resolve the issue. We appreciate your patience and understanding during this time. Please check back for updates. Thank you for your continued support.

The issue has been identified and a fix is being implemented. Thank you again for your patience & understanding.

A fix has been implemented and we are monitoring the results. Apologies again for the inconvenience caused.

This incident has been resolved.

We are aware of an issue currently affecting the VideoAsk functionality. We are working on a fix. Apologies for the inconvenience.

The issue has been identified and we are implementing a fix. Thank you for your patience.

A fix has been implemented and we are monitoring the results. Thank you again for your patience.

This incident has been resolved.

We have identified a traffic interruption impacting our checkout page. Users paying or upgrading may be impacted. We are working on resolution with high priority. We are really sorry for any inconvenience this is causing. Next update in 20-30 minutes or as soon as it's available.

We are continuing to work on a fix for this issue. Apologies again for any inconvenience this is causing.

We are glad to inform you that a fix has been implemented and the incident resolved. We will run a problem investigation to understand what happened and how to prevent it from happening again. Thank you for your patience.

Degraded performance with some Amazon Web Service (AWS) tools is causing issues with uploading, processing, and transcribing videos in VideoAsk. Updates on this incident can be viewed through AWS directly here: https://health.aws.amazon.com/health/status

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

This incident has been resolved.

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

We're experiencing some errors that are affecting the performance of our application. We have identified the issue and are actively investigating it to find a prompt resolution.

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

This incident has been resolved.

We are currently investigating this issue.

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

This incident has been resolved.

We have identified errors impacting our Subscriptions Services. Users trying to change their plans are impacted. We are working on a resolution with high priority. We plan to provide an update in 20-30 minutes or as soon as it's available.

This incident has been resolved.

All services have been restored with logins and signups working as they should. The incident was caused by an expired SSL certificate failing to update due to an integration issue with our security supplier. To note, although login and signup services were interrupted during the incident, submissions were functioning throughout and no data was lost. We sincerely apologize for this outage and any inconvenience we may have caused. Our engineering teams will review the details and ensure we put measures in place to prevent this from happening again.

Our team is currently investigating an issue where new responses, transcripts, and email notifications are delayed.

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

All responses submitted during this downtime should be processed within the next 15-20 minutes. New responses, transcripts, and email notifications should return to processing as normal at that point.

This incident has been resolved.

We are currently investigating an issue related to responses not appearing in the inbox and email notifications not being sent.

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

We are currently investigating an issue related to responses not appearing in the inbox and email notifications not being sent. Responses that are submitted during this outage should eventually arrive in your inbox. Responses appear to be delayed by 15-20 minutes. Email notifications appear to be delayed by approximately 30 minutes.

This delay in processing responses and email notifications was caused by an unusually high volume of text responses, which created a bottleneck in our systems. Response and email notification processing times should return to normal within several hours.

Issue has been resolved.

This incident has been resolved.

We are currently investigating an issue where audio and video content is not being processed. Responses, creator replies, and respondent replies are affected. Text responses do not appear to be affected.

This incident appears to be related to an Amazon Web Services (AWS) outage, which has now been resolved. Audio and video content that was stuck in processing during the outage should now start reprocessing. Affected audio and video content should become available soon.

This incident has been resolved.

VideoAsk website was unavailable, returning 403 Forbidden errors. This resulted in the creation & answering being down for all users.

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

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

A task in our database was taking longer than expected and slowing our services down. The task is now completed and Videoask should be available again.

This incident has been resolved.