Base says configuration change caused transaction delays, fixes issue

On May 14th, our monitoring systems registered a significant degradation in transaction processing times across primary API endpoints, specifically affecting user checkout and login services. Preliminary root cause analysis (RCA) concluded that the incident was triggered by a recently deployed configuration update.

This configuration change, deployed during a routine deployment window, involved an adjustment to the internal database connection pool settings. Specifically, the maximum concurrent connection limit was inadvertently set below the minimum operational requirement. The resulting resource contention led to severe queue backlogs and substantial transaction latency spikes, peaking at 4.5 seconds against the established Service Level Agreement (SLA) of 500ms.

The incident window lasted for 120 minutes before resolution. No customer data was compromised, but approximately 18% of user transactions experienced severe delays or timeouts during this period. The issue was resolved by the immediate isolation and controlled rollback of the faulty configuration file to the previous stable state (Version 2.1.0). Service stability was fully restored shortly thereafter.

To prevent recurrence, the organization is implementing mandatory automated pre-deployment validation checks (APVC) specifically designed to simulate peak load against resource allocation changes. Furthermore, an immediate audit of all configuration management templates is underway to ensure robust boundary checking for key resource variables.

Source: Base says configuration change caused transaction delays, fixes issue