Stripo incident

Degraded performance in Plugin API Gateway affecting plugin initialization

Critical Resolved View vendor source →

Stripo experienced a critical incident on April 21, 2026 affecting API Gateway Service (plugin), lasting 21m. The incident has been resolved; the full update timeline is below.

Started
Apr 21, 2026, 01:36 PM UTC
Resolved
Apr 21, 2026, 01:57 PM UTC
Duration
21m
Detected by Pingoru
Apr 21, 2026, 01:36 PM UTC

Affected components

API Gateway Service (plugin)

Update timeline

  1. investigating Apr 21, 2026, 01:36 PM UTC

    We are currently experiencing increased response times in the Plugin API Gateway, which is impacting the speed and ability to initialize new plugins.

  2. monitoring Apr 21, 2026, 01:51 PM UTC

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

  3. resolved Apr 21, 2026, 01:57 PM UTC

    The issue with increased response times in the Plugin API Gateway has been resolved, and plugin initialization is now operating normally. Root cause: During a scheduled AWS infrastructure update to apply patches, which was expected to proceed without downtime and therefore was not communicated in advance, an unfortunate misconfiguration occurred, which we have already identified and fixed. Some pods were terminated before new ones were fully ready, leading to a significant accumulation of requests in the queue. Instead of being processed gradually, a large batch of queued requests was handled simultaneously, which exhausted available database connections and caused delays in processing new incoming requests. We are optimizing our deployment and scaling procedures to prevent similar situations in the future.