Databento incident

Investigating intermittent timeouts on historical APIs

Critical Resolved View vendor source →

Databento experienced a critical incident on April 27, 2026 affecting Historical, lasting 1d 12h. The incident has been resolved; the full update timeline is below.

Started
Apr 27, 2026, 10:13 AM UTC
Resolved
Apr 28, 2026, 10:26 PM UTC
Duration
1d 12h
Detected by Pingoru
Apr 27, 2026, 10:13 AM UTC

Affected components

Historical

Update timeline

  1. investigating Apr 27, 2026, 10:13 AM UTC

    We are currently investigating intermittent issues on our historical API. We believe this is due to slow reads on our storage cluster.

  2. investigating Apr 27, 2026, 10:14 AM UTC

    We are continuing to investigate this issue.

  3. identified Apr 27, 2026, 10:38 AM UTC

    We have taken action to mitigate the impact. Our systems engineers have identified the root cause and are working to resolve the issue. Customers may continue to experience timeouts and errors from the historical API.

  4. monitoring Apr 27, 2026, 12:56 PM UTC

    We have taken steps to resolve the slow operations on the storage cluster. We will continue to monitor for issues.

  5. identified Apr 27, 2026, 02:39 PM UTC

    We are still experiencing performance issues on our storage cluster. This is causing intermittent issues on the historical API and delays to historical data availability. We are working on a fix.

  6. monitoring Apr 28, 2026, 12:34 AM UTC

    We have taken additional steps to resolve the slow operations on the storage cluster. We will continue to monitor for issues.

  7. resolved Apr 28, 2026, 10:26 PM UTC

    This incident has been resolved.