Gorilla Outage History

Started Mar 20, 2026, 05:05 AM UTC· resolved Mar 20, 2026, 09:44 AM UTC

1. resolved Mar 20, 2026, 11:29 AM UTC

   Impact calculations: Some calculations have failed because of a formula dependency not being found. 20 Mar 2026, 07:05 CEST: Internally noticed errors popping up, a hotfix was being created 20 Mar 2026, 10:31 CEST: The hotfix was already ready, but deployment of the fix would disrupt currently running production workloads. 20 Mar 2026, 11:18 CEST: Incidents got further escalated. 20 Mar 2026, 11:44 CEST: Fix was deployed to affected customers and environments.

Read the full incident report →

Started Mar 02, 2026, 11:00 AM UTC· resolved Mar 03, 2026, 01:00 PM UTC

1. resolved Mar 02, 2026, 03:21 PM UTC

   Impact to SFTP based integration: Failure to upload files Impact calculations: Some calculations have failed because of internal packages/libraries could not be installed. 27 Feb 2026, 20:32 CEST: We got a notification from our domain registrar that our internal domain failed the renewal. 02 Mar 2026, 11:48 CEST: Intermittent calculations failures for some customers 02 Mar 2026, 12:00 CEST: Notification on failure to connect to the Gorilla SFTP 02 Mar 2026, 12:28 CEST: Internal domain renewed successfully 02 Mar 2026, 15:00 CEST: Full recovery Cause: Credit card fault (not expiration). Resolution: We use specific subscription based credit cards. A new credit card needed to be created and attached to the domain registrar and forced the DNS records to be propagated. Actions requested from integrations using the SFTP: please check your logs and re-upload any failed uploads to the Gorilla SFTP.

Read the full incident report →

Started Dec 17, 2025, 03:02 PM UTC· resolved Dec 18, 2025, 05:31 PM UTC

1. investigating Dec 17, 2025, 03:02 PM UTC

   Some users experienced intermittent API errors and slower response times. In certain cases, repeated requests failed until the affected service instances were restarted. We are investigating an ongoing issue causing intermittent API errors and slower response times for calculation-related requests. The issue occurs when the API exceeds execution time limits and enters a degraded state, which can cause repeated request failures until the affected service instances are recycled. We are actively mitigating impacted instances and monitoring the platform. In parallel, we are enhancing detection and alerting to ensure a faster response while we work on a longer-term solution to prevent this behavior from recurring. Further updates will be shared as progress is made.

2. identified Dec 17, 2025, 04:13 PM UTC

   We are investigating a potential interaction between a recently updated monitoring component and our API runtime. This may, under certain conditions, prevent proper timeout handling and lead to intermittent errors. Fixes are being rolled out, and the investigation is ongoing.

3. identified Dec 17, 2025, 04:23 PM UTC

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

4. monitoring Dec 17, 2025, 04:42 PM UTC

   We have identified a likely contributing factor related to a recent update in a third-party monitoring component that was automatically included in our latest deployment. This update affected our ability to observe the API and may have contributed to intermittent timeouts and 500 errors. In parallel, the monitoring provider has deprecated their legacy Lambda monitoring and recommended migrating to a newer APM-based integration. We have completed this migration, applied a workaround for the identified issue, and rolled out a hotfix across all environments. The remaining work is to update dashboards and alerts to fully use the new monitoring data. We continue to monitor the situation closely and will provide further updates as stability is confirmed.

5. investigating Dec 17, 2025, 07:01 PM UTC

   We are investigating a recurrence of intermittent API errors and slow responses. Previous changes did not fully resolve the issue. Early findings suggest our internal timeout safeguards are not consistently triggering in production, allowing platform-level timeouts to occur and cause repeated service restarts. The exact cause is still under investigation. We are actively working on mitigations and will share updates as we learn more.

6. identified Dec 17, 2025, 08:09 PM UTC

   We have identified the cause of the ongoing API issues. In some cases, individual requests can take longer than expected, which may prevent our internal safeguards from triggering correctly. This can lead to temporary service degradation and errors. Mitigation in progress: We are applying changes to ensure slow requests fail cleanly without affecting overall service stability, and are identifying additional improvements to prevent this behavior from recurring. We will provide another update once the fix is deployed and move the incident to the Monitoring phase.

7. monitoring Dec 17, 2025, 08:24 PM UTC

   A fix has been implemented to ensure slow requests fail cleanly without impacting overall service stability. We are actively monitoring to confirm the fix fully resolves the issue. Further updates will be shared if needed.

8. resolved Dec 18, 2025, 05:31 PM UTC

   This incident has been resolved. Our team will continue to explore long-term solutions and improvements. If you continue to experience, please reach out to our support team

Read the full incident report →

Started Dec 17, 2025, 09:35 AM UTC· resolved Dec 17, 2025, 09:48 AM UTC

1. investigating Dec 17, 2025, 09:35 AM UTC

   We are currently investigating why the INT environment is inaccessible.

2. resolved Dec 17, 2025, 09:48 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 19, 2025, 12:56 PM UTC· resolved Nov 20, 2025, 08:38 AM UTC

1. identified Nov 19, 2025, 12:56 PM UTC

   Dear Customer, As part of our ongoing commitment to ensure the stability and continuity of your operations, our team has identified a compatibility issue affecting some older formulas. To prevent any potential disruption, we will be deploying a hot-fix today at 5:00pm UTC. To apply this improvement safely, there will be a brief period of downtime, expected to last no more than one hour. Any calculations running during the deployment window may be interrupted, so we recommend avoiding critical processing at that time. Thank you for your understanding and cooperation as we work to maintain a reliable and seamless experience for you. Our team will ensure the update is completed as quickly as possible. Kind regards, Gorilla

2. resolved Nov 20, 2025, 08:38 AM UTC

   The hot-fix deployed successfully at 5:30pm UTC. The Statuspage update to notify the resolution was overlooked.

Read the full incident report →

Started Oct 20, 2025, 10:03 AM UTC· resolved Oct 20, 2025, 11:22 PM UTC

1. monitoring Oct 20, 2025, 10:03 AM UTC

   An issue in the US-EAST-1 Region is impacting different services/applications that make use of it. Gorilla US customers can incur degraded performance. We have seen it impact a non-US customer where calculations could fail or have degraded performance. It is currently looking stable for non-US customers. AWS is aware and are actively resolving the issues and are seeing significant signs of recovery. We're reaching out through other channels as well. Statuspage was also affected and is cause of the late communication. We'll keep you updated on how it is progressing.

2. monitoring Oct 20, 2025, 11:27 AM UTC

   Most large issues have been resolved by AWS. AWS still mentions that there can be some delays and degraded performance, but are working towards full mitigation.

3. monitoring Oct 20, 2025, 11:31 AM UTC

   We are continuing to monitor for any further issues.

4. resolved Oct 20, 2025, 11:22 PM UTC

   AWS has communicated that they have fully resolved the issues and we are happy to announce that we are fully up and running again. Following from this incident, we will be doing discovery work to identify the gaps in our mitigation plan to better manage future incidents of a similar nature.

Read the full incident report →

Started Jul 11, 2025, 12:34 PM UTC· resolved Jul 11, 2025, 12:34 PM UTC

1. resolved Jul 11, 2025, 02:24 PM UTC

   We experienced an issue where the API failed during calculation processes. This caused the calculation results to not load or be received as expected. Additionally, the frontend was partially impacted for a brief period, leading to degraded functionality for some users.

Read the full incident report →

Started Jan 29, 2025, 10:33 AM UTC· resolved Jan 29, 2025, 11:54 AM UTC

1. identified Jan 29, 2025, 10:33 AM UTC

   Our infrastructure provider has reported an incident affecting our platform’s hosting. As a result, you may encounter occasional “404 Not Found” errors. They are actively investigating the issue. In most cases, refreshing the page will restore access without further problems. Calculations remain unaffected and can still be run and scheduled as usual.

2. identified Jan 29, 2025, 10:43 AM UTC

   Direct access to the platform is working correctly. The infrastructure provider is engaged and is actively working on developing a mitigation. An additional update in the next hour will be provided.

3. monitoring Jan 29, 2025, 11:15 AM UTC

   The root cause of the issue with our website origin has been identified. Our provider is implementing mitigations to ensure full recovery. We will keep monitoring the state of the issue. Another update will be provided in the next 45 minutes.

4. resolved Jan 29, 2025, 11:54 AM UTC

   The provider initiated a rollback of the change which led to a full recovery of errors. The issue has been resolved and the service is operating normally.

Read the full incident report →