Databento portal and historical API down
Monitoring - We identified an issue with one of the storage metadata servers affecting IO operations on our storage cluster.
This resulted in a cascade of effects causing our web services to hang.
We have failed over the problem server and all historical API and web services are back operational.
Batch job processing was delayed during the incident, but jobs are now progressing.

We are continuing to monitor for any issues.
Aug 06, 2026 - 15:05 UTC
Update - We are continuing to work on a fix for this issue.
Aug 06, 2026 - 12:53 UTC
Identified - The issue has been identified and a fix is being implemented.
Aug 06, 2026 - 11:33 UTC
Investigating - We are investigating an issue with the historical API and Databento web portal
Aug 06, 2026 - 11:13 UTC
Uptime over the past 90 days. View historical uptime.
Portal Operational
90 days ago
99.75 % uptime
Today
Historical Partial Outage
90 days ago
98.67 % uptime
Today
Live Operational
90 days ago
99.99 % uptime
Today
Live CME - Aurora DC3 Operational
90 days ago
99.99 % uptime
Today
Live US Equities - Secaucus NY4 Operational
90 days ago
99.99 % uptime
Today
Live OPRA - Secaucus NY4 Operational
90 days ago
99.99 % uptime
Today
Live ICE - Aurora DC3 Operational
90 days ago
99.99 % uptime
Today
Live Eurex/EEX - Frankfurt FR2 Operational
90 days ago
99.99 % uptime
Today
Live CFE - Secaucus NY4 Operational
90 days ago
99.99 % uptime
Today
FTP Operational
90 days ago
98.85 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

Scheduled upgrade of GLBX.MDP3 to new version of data Aug 8, 2026 00:00-02:00 UTC

CME data since 2026-08-06 00:00:00Z will be unavailable while we perform this upgrade.
Posted on Aug 05, 2026 - 17:58 UTC

Aug 6, 2026

Unresolved incident: Databento portal and historical API down.

Aug 5, 2026

Batch job processing delayed
Resolved - This incident has been resolved.
Aug 5, 01:35 UTC
Monitoring - We've implemented some improvements to our batch job processing infrastructure, and have observed that it is keeping up with incoming batch jobs.
We're continuing to monitor for further delays or issues.
Jul 30, 16:58 UTC
Identified - The fixes implemented earlier helped the situation temporarily, but the batch system has fallen behind again.
This is impacting the rate at which customer jobs are being completed.
We are working on a solution.
Jul 30, 12:33 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jul 29, 10:23 UTC
Identified - Our batch job processing system fell behind, processing is resuming with the backlog of jobs. (There is no need to re-submit any jobs.)

We're expecting the system to be caught up by 10:00 UTC.
Jul 29, 08:51 UTC
Consistent 504 timeout on the Historical API
Resolved - This incident has been resolved.
Aug 5, 00:00 UTC
Update - We are continuing to monitor for any further issues.
Aug 4, 22:07 UTC
Update - We are continuing to monitor.
Aug 4, 14:08 UTC
Monitoring - We've applied mitigations to the historical service and continue to monitor for timeouts.
Aug 4, 09:57 UTC
Investigating - We are investigating an issue where the Historical API is showing timeout errors.
Aug 4, 07:47 UTC

Aug 4, 2026

Consistent 504 timesouts on Databento.com and the API
Resolved - This incident has been resolved.
Aug 4, 04:49 UTC
Monitoring - We've been working internally to resolve this issue and are monitoring it. The portal, API, and FTP are responsive now as we continue to observe the recovery.
Aug 4, 01:56 UTC
Investigating - We are investigating an issue where the portal (databento.com) and Historical API and FTP are showing timeout errors.
Aug 4, 01:04 UTC

Aug 3, 2026

No incidents reported.

Aug 2, 2026

No incidents reported.

Aug 1, 2026

No incidents reported.

Jul 31, 2026

No incidents reported.

Jul 30, 2026

Jul 29, 2026

Jul 28, 2026

No incidents reported.

Jul 27, 2026

Batch job processing delayed
Resolved - This incident has been resolved.
Jul 27, 21:28 UTC
Update - We have taken additional internal steps to remediate this issue, and we're seeing improved batch job processing times (as of 10 minutes ago).
Jul 27, 17:12 UTC
Monitoring - The batch job processing system has caught up on the backlog of jobs, we're continuing to monitor the system.
Jul 27, 04:18 UTC
Identified - Our batch job processing system fell behind due to internal storage degradation. Processing is resuming with the backlog of jobs. (There is no need to re-submit any jobs.)
Jul 27, 02:53 UTC

Jul 26, 2026

No incidents reported.

Jul 25, 2026

No incidents reported.

Jul 24, 2026

Intermittent API outage due to an internal DNS issue
Resolved - This incident has been resolved.
Jul 24, 23:20 UTC
Monitoring - We've implemented a fix internally and the system looks healthy again. We'll continue to monitor.
Jul 24, 23:04 UTC
Identified - We're investigating an issue with an internal DNS server, which is causing intermittent API 500 errors. We expect this to be resolved within the next 15 minutes.
Jul 24, 23:03 UTC

Jul 23, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage