Waterfall incident

Elevated error rates and increased latency.

Minor Resolved View vendor source →

Waterfall experienced a minor incident on February 27, 2026 affecting Individual Services (Enrichment Contact) and Individual Services (Enrich Company) and 1 more component, lasting –. The incident has been resolved; the full update timeline is below.

Started
Feb 27, 2026, 09:44 PM UTC
Resolved
Feb 27, 2026, 09:44 PM UTC
Duration
–
Detected by Pingoru
Feb 27, 2026, 09:44 PM UTC

Affected components

Individual Services (Enrichment Contact)Individual Services (Enrich Company)Individual Services (Account Info V2)

Update timeline

  1. resolved Feb 27, 2026, 09:44 PM UTC

    On February 27, 2026, 20:49 UTC, the Waterfall API experienced degraded performance affecting some asynchronous job endpoints. The incident was triggered by an unexpected surge in enrichment request volume that exceeded normal traffic patterns, causing temporary resource contention in our backend infrastructure. This resulted in intermittent timeouts and elevated error rates for some API consumers. Our engineering team identified the root cause quickly and took immediate action to restore full service. Normal operations were restored within 15 minutes. No data was lost — any jobs that failed during the incident window can be safely re-submitted. As part of our ongoing commitment to platform reliability, we are rolling out infrastructure improvements designed to handle higher throughput and ensure all clients can take full advantage of their allocated rate limits without interruption. These enhancements include more resilient connection management, improved load isolation between accounts, and smarter capacity scaling under peak demand. We're confident these changes will deliver a faster, more reliable experience as your usage grows. We appreciate your patience and are always available to discuss your integration needs.