Degraded historical API
- Type changed from degraded to outage on Nov 19, 2026
- Impact changed from Minor to Major on Nov 19, 2026
Nov 19, 10:22 UTCNov 21, 00:46 UTC
Duration
38h 25m
Impact
Major
Root cause
Not disclosed
Databento, 90 days
15 incidents
Affected
Historical
Final update
This incident has been resolved.
Timeline
- Resolved · Nov 21, 00:46 UTC
This incident has been resolved.
- Monitoring · Nov 20, 03:43 UTC
A fix has been implemented and we are continuing to monitor for any increased error rates. Batch job processing is continuing as normal.
- Identified · Nov 19, 17:36 UTC
Data availability through the Historical API is restored. There continue to be delays with batch job processing.
- Identified · Nov 19, 13:22 UTC
We are continuing to work to balance load. We are still seeing delays with batch processing and availability.
- Identified · Nov 19, 11:28 UTC
The team has implemented a fix. An internal symbology metadata service became overloaded, causing slow responses, timeouts, and delayed / stalled batch jobs. Its standby replica got out of sync and had to be rebuilt before load could be shifted to it; that’s now done and traffic is being rebalanced. We expect jobs to begin processing once traffic has rebalanced to the standby.
- Identified · Nov 19, 10:22 UTC
We have identified an issue causing degraded performance of the historical API. Requests are timing out intermittently; batch jobs are processing more slowly than expected or may be stalled. We are working on a fix. Live APIs are not affected.
More from Databento
Full historyLive API disconnections at Aurora DC3lasted 0mIntraday GLBX.MDP3 and OPRA.PILLAR delayslasted 42h 55mDegraded intraday data for 2026-11-05lasted 7d 6hOPRA.PILLAR Historical data delayedlasted 7d 12hOPRA.PILLAR data degraded for 2026-11-04lasted 11h 53mInvestigating an issue in FR2 (Frankfurt) Datacenter affecting both XEUR.EOBI and XEEE.EOBIlasted 2d 16h