Gorilla Outage History

Gorilla is up right now

Gorilla had 8 outages in the last 2 years totaling 61h 1m of downtime — averaging 0.3 incidents per month.

There were 8 Gorilla outages since January 29, 2025 totaling 61h 1m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.gorilla.co

Notice March 20, 2026

Indiscriminate calculation failures caused by failure to load a formula dependency

Detected by Pingoru
Mar 20, 2026, 06:00 AM UTC
Resolved
Mar 20, 2026, 06:00 AM UTC
Duration
Timeline · 1 update
  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 →

Major March 2, 2026

Possible calculation and SFTP failure: Internal domain name used for SFTP and package manager payment failed

Detected by Pingoru
Mar 02, 2026, 03:21 PM UTC
Resolved
Mar 02, 2026, 11:00 AM UTC
Duration
Timeline · 1 update
  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 →

Notice December 17, 2025

INT inaccessible

Detected by Pingoru
Dec 17, 2025, 09:35 AM UTC
Resolved
Dec 17, 2025, 09:48 AM UTC
Duration
12m
Timeline · 2 updates
  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 →

Notice November 19, 2025

Hot-fix to address formula compatibility issue

Detected by Pingoru
Nov 19, 2025, 12:56 PM UTC
Resolved
Nov 20, 2025, 08:38 AM UTC
Duration
19h 41m
Timeline · 2 updates
  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 →

Major October 20, 2025

AWS issues in US-EAST-1 Region could impact US customers and in some cases impact non-US customers.

Detected by Pingoru
Oct 20, 2025, 10:03 AM UTC
Resolved
Oct 20, 2025, 11:22 PM UTC
Duration
13h 19m
Affected: API
Timeline · 4 updates
  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 →

Notice July 11, 2025

Failing calculation processing

Detected by Pingoru
Jul 11, 2025, 12:34 PM UTC
Resolved
Jul 11, 2025, 12:34 PM UTC
Duration
Affected: APIWeb Application
Timeline · 1 update
  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 →

Major January 29, 2025

Operational issue - Platform hosting

Detected by Pingoru
Jan 29, 2025, 10:33 AM UTC
Resolved
Jan 29, 2025, 11:54 AM UTC
Duration
1h 20m
Affected: Web Application
Timeline · 4 updates
  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 →