Is Rainforest QA Down Right Now? Check if there is a current outage ongoing.

One of our upstream providers is currently experiencing an outage. We are monitoring the impact of this on our application.

The fix has been fully applied and all AI services should be back to normal.

A fix has been applied and will be rolling out over the next hour. AI services should now be broadly available for most platforms but some older runs / previews may still be affected. We'll continue to monitor the situation until the rollout is complete.

We have identified an issue that is affecting step generation, self-healing snippets, and AI test assertions. Those service will be unavailable until such time as the incident is fixed.

This incident has been resolved.

We've implemented a fix and all delayed background jobs have been processed. We are monitoring to make sure everything continues working properly.

We are investigating an issue related to background job processing. Some results or runs may be delayed during this time.

This incident has been resolved.

The application is back online, and we're monitoring to make sure everything is working properly again.

The Rainforest application is currently offline. This affects access to the application, as well as any tests or runs that were in progress. We're looking into it and will provide an update shortly.

The backlog of runs has been processed and everything should be back to normal.

We've applied a fix and everything should be operational again. We're processing the backlog of runs created in the last 3 hours which will take some time. We'll update the status to "Resolved" once the backlog is processed.

We've identified an issue which is causing problems when trying to execute tests. Test runs are not being processed. Virtual machines in the Visual Editor are not available. We're working on a fix.

We have resolved the issue affecting test video recording. Test runs from approximately 06:30 UTC to 17:35 UTC may be missing their video recordings.

We are investigating an issue that is delaying the availability of test result videos

This incident has been resolved.

A permanent fix has been implemented and performance appears to have returned to normal. No further delays are expected.

We have applied a temporary fix to mitigate the issue and are continuing to work on a more permanent fix.

We are working on an issue that is delaying the allocation of virtual machines when starting a run. We have identified the issue and are working to resolve it.

We've fixed the issue and runs are now starting and progressing as usual.

We've identified an issue that may have caused some runs to be delayed.

The incident has been resolved.

A fix has been implemented, we are now monitoring.

We are currently investigating the issue.

This incident has been resolved.

We've shipped a fix and are monitoring the situation.

We've identified the component we believe is causing the problem and are investigating why it's behaving badly.

We've noticed that some test executions are not being processed correctly, which is holding up the completion of runs. We're currently investigating it.

We realized that our provider for AI infrastructure was having a soft outage which was causing some requests to take a very long time \(10 minutes\) to error. We worked around this by decreasing the timeout for the requests so that they would error faster and we could then retry them.

This incident has been resolved.

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

Operations involving AI are taking some time to complete. We're investigating the issue.

This incident has been resolved.

We implemented a fix and are monitoring the results.

We’ve identified another problem with action generation and are working on a fix

The issue has been resolved

We've shipped a fix and will continue to monitor the situation.

We’ve identified a problem with action generation and are working on a fix”

This incident has been resolved.

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

We're experiencing issues with failure summarization. The fix is being deployed.

This incident has been resolved.

We've shipped a fix and will continue to monitor the situation.

We've identified the cause of the delays and are working on a fix.

We are continuing to investigate this issue.

We are currently experiencing an issue with runs being delayed and currently working on a fix.

This incident has been resolved.

The problem is somewhat improved, but we're continuing to investigate.

We've noticed a problem with our fleet of VMs, which are used for test execution and test authoring. This may mean that you can't edit tests, and that test execution will be delayed.

Confirmed that everything is back to normal. There should be no more delayed runs.

We've resolved the issue and are continuing to monitor. Runs should be progressing normally again.

We're experiencing some internal issues. Runs are being delayed. We've identified the source and are resolving it.

This incident has been resolved.

Our new fix is applied and appears to be working properly. We will continue to monitor the situation to ensure it is fully resolved.

There was an issue with the fix we had applied which caused the issue to re-appear. We've applied a new fix and things are starting to improve, but it may take a few minutes for the backlog to be processed. Any runs that were unable to proceed should begin progressing soon.

We identified an issue that was preventing test editing and runs from proceeding. We've deployed a fix and are monitoring the situation.

This incident has been resolved.

All Android tests are fully operational.

We've identified the problem - it's restricted to tests and previews that use Android. We're working on a fix.

We are continuing to investigate this issue.

Our monitoring has identified an issue that may be causing some runs to be delayed. We're investigating the issue.

This incident has been resolved. Any delayed runs are now in progress and Android VMs are available for use in the Visual Editor.

We've detected a problem with Android VMs not loading in the Visual Editor. Runs may also be affected. We're investigating now.

This incident has been resolved.

The application is back online. We are monitoring for any lingering performance degradation.

The Rainforest app is currently experiencing a major outage. Engineers are actively working on a resolution.

This incident has been resolved.

One of our upstream providers that helps power our test editor is experiencing an outage. Editing tests may be slow or fail, and existing sessions may be interrupted.

This incident has been resolved.

We've resolved this issue and now SMS messages can be sent in response to inbound messages in tests.

This has occurred because of new regulations surrounding registering sending messages from "long code" phone numbers (A2P 10DLC). We have started the process to register the numbers we use for sending SMS messages and our vendor has informed us this may take a few weeks. This only affects sending SMS messages from our virtual SMS inbox service. It does not affect receiving them - so tests that involve sending SMS messages such as MFA login and don't require a response via SMS are unaffected.

We've identified an issue with some messages sent via the Rainforest SMS app not being delivered. Incoming messages are not affected: messages sent to Rainforest SMS numbers from other services are viewable in the Rainforest SMS app.

This incident has been resolved.

Our upstream provider has implemented a fix and things are working better. We are no longer seeing elevated error rates but will continue to monitor this.

One of our upstream providers that helps power our test editor is experiencing an outage. Editing tests may be slow or fail, and existing sessions may be interrupted.

This incident has been resolved.

Our upstream provider is reporting that the issues are resolved, and we have seen a sharp drop off in errors being reported. We'll continue to monitor this to ensure the issue is resolved.

Our upstream provider reports that performance should be improving but they are continuing to monitor the situation. Some test editing sessions may still encounter errors.

We are continuing to investigate this issue.

We are currently experiencing degraded performance from an upstream provider that is impacting loading of test previews and are working on resolving the issue.

We've identified the issue and all runs that were delayed have finished properly.

We are investigating an issue with runs not finishing properly. This will result in delays receiving test execution results.

This issue has been resolved and runs are progressing as normal. If you are still experiencing issues, please reach out to us as at support@rainforestqa.com.

We are continuing to investigate this issue.

We are currently investigating an issue that is causing runs to be delayed from starting

This issue has been resolved. If you are still experiencing issues loading a virtual machine, please reach out to us as at support@rainforestqa.com.

Some users are reporting issues loading a Virtual Machine. Our team is actively investigating this issue.

We've reverted the bad code change and reverted it. We've confirmed the visual editor is working as expected.

We've identified a problem with the visual editor that means that any tests with an "Observe" action can't be saved. We're located the problem and are currently working on the fix.

We have deployed a fix and verified that the site should be loading properly again.

We've identified an issue with some pages of our application failing to load. We are deploying a fix and hope to have this issue resolved shortly.

This incident has been resolved.

Our service provider has restored service. We are monitoring the situation

Virtual Credit Card functionality is currently unavailable due to a major incident with our virtual card service provider.

We are running at full capacity.

We've resolved the issue that was causing VMs to fail to load in the Visual Editor, we're now working to recover our full capacity. This incident has also affected our capacity to execute tests as part of a run, so runs may be delayed until we've fully recovered.

We have identified and mitigated the issue. We're still experiencing reduced availability and are working to fully resolve it.

We've detected a problem with VMs not loading in the Visual Editor and are investigating.

This incident has been resolved.

We are currently investigating an issue where users are not able to access test data from within the platform.

We identified the change that caused the issue and reverted it.

We are currently investigating this issue.

This incident has been resolved.

We're currently experience an issue with test execution on our virtual machines that's affecting screenshot capture. This will affect test editing and crowd execution. There may be a delay in viewing artifacts from automatic test execution.

Our provider has reported the issue as being resolved and we have confirmed that our service is working as expected.

An upstream provider is currently experiencing issues that is impacting the ability to get a virtual desktop for editing tests.

This incident has been resolved.

The fix has been deployed.

Test automation service is disrupted, a fix is in progress.

We are no longer seeing any VM loading issues in the Visual Editor.

Our upstream provider has rolled out a fix for these networking issues.

We are seeing elevated rates of errors related to network connectivity from our Virtual Machine infrastructure and are investigating. We've identified the problem as an issue with one of our upstream service providers and are waiting on a fix to finish being rolled out.

Our upstream provider has resolved these networking issues. We are no longer seeing any issues on our end.

Our upstream provider is working to resolve these networking issues, but we are still seeing periodic network connectivity issues within our virtual machine infrastructure. We'll continue to monitor the situation.

We've identified the problem as an issue with one of our upstream hosting providers. Network connectivity appears to be improving and we are seeing fewer errors, but we will continue to monitor the situation.

We are seeing elevated rates of errors related to network connectivity from our Virtual Machine infrastructure and are investigating.

All operations back to normal.

We have applied a fix that seems to have resolved the issue. Runs should progress normally now, and we will be monitoring performance over the next few hours.

We've identified the issue and are working to restore VM performance.

We are currently investigating an issue with VM loading affecting Runs being delayed.

This incident has been resolved.

A fix has been implemented by our CDN provider. We will monitor the situation to see if there are any outstanding issues.

Our hosting provider appears to be suffering from a problem that is preventing access to our service from certain locations. We're currently investigating this issue to determine if there is a work around we can apply.

We have resolved the issue.

We've identified an issue with our SMS testing backend which may cause tests that rely on testing SMS verification to fail. We're currently working towards resolving this problem.

A small number of emails were not delivered due to an issue with an upstream email provider.

This incident has been resolved.

We are continuing to monitor for any further issues.

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

We've identified the problem and deployed a fix, the VM infrastructure should be returning to normal.

We're investigating problems with our VM infrastructure, runs and test previews are likely to be impacted.

This incident has been resolved.

We've observed a small number of network connectivity issues with our test infrastructure hosting provider, and are monitoring the issue.

This incident has been resolved.

We're monitoring network connectivity issues with our test infrastructure hosting provider.

This incident has been resolved.

We've experienced connectivity problems for about 2 minutes, including email delivery problems. Currently monitoring for any other disruption.

This incident has been resolved.

The Results page (/runs) was misbehaving. This should now be resolved, we're monitoring the situation.

This incident has been resolved.

We are no longer seeing any text matching request failures. However, our upstream provider's maintenance is still ongoing, which could cause these to start happening again and cause run delays once more. We'll continue to monitor the situation.

We are still seeing a small number of text matching request failures, which may result in some run delays. We'll continue to monitor the situation.

Network performance appears to have improved and we are continuing to monitor the situation.

Our upstream provider is performing maintenance work on their network backbone affecting connectivity. This work is expected to be complete soon.

We are currently investigating an issue affecting the network connectivity of our VM infrastructure. This may impact run execution and test writing previews.

This incident has been resolved by the upstream provider.

We are monitoring the operational status of upstream provider.

The issue has been identified.

One of our upstream providers is experiencing issues that will possibly impact some Rainforest features, such as processing email to our inboxes. We're currently monitoring the situation.

This incident has been resolved.

It appears that the issue our hosting provider was suffering from is resolved. We will monitor the situation to see if there are any outstanding issues.

Our hosting provider appears suffering from a problem that is preventing access to our service. We're currently investigating this issue to determine if there is a work around we can apply.