Gorilla Experiment Builder had 4 outages in the last 2 years totaling 15h 20m of downtime — averaging 0.2 incidents per month.
There were 4 Gorilla Experiment Builder outages since September 2, 2024 totaling 15h 20m of downtime. Each is summarised below — incident details, duration, and resolution information.
Due to a bug in a routine deployment, there was a partial outage lasting approximately 15-20 minutes that may have prevented some users accessing the app. This has now been resolved
A sudden increase in traffic to the platform resulted in heavily impaired performance for a short period. The issue was diagnosed, rectified, and measures have been taken to prevent future occurrences.
We are aware of an issue with Microsoft Azure (our cloud service provider) which is currently impacting the Gorilla platform. We are continuing to monitor the issue and our technical team will take whatever mitigating options become available to them. We will provide an update as soon as we are able to.
We are continuing to investigate this issue.
Azure have successfully rolled back to their last know good configuration, and the service's performance should continually improve. They have forecast recovery by 23:20 UTC on 29 October 2025, though performance may still be degraded until then as they continue to restore nodes.
A fix has been implemented and we are monitoring the results.
Microsoft Azure are no longer reporting any issues and the platform has returned to normal stability, though we are continuing to monitor and respond to the aftereffects of the outage
A service outage on Azure resulted in task assets distributed via an Azure CDN (Content Delivery network) being unavailable. For Task Builder 1 and Questionnaire Builder 1 this will have resulted in some stimuli failing to load. For Task Builder 2, Questionnaire Builder 2, Shop Builder and Game Builder, this will have resulted in participants receiving an error message "No-Mani-1" on initial task load. While the service issue appears to have been resolved, we'll continue to investigate and identify any routes for mitigating similar issues in the future (especially as this is the second time in as many months that the Azure CDN has experienced difficulties!)