Databento Outage History

Started May 01, 2026, 12:29 PM UTC· resolved May 01, 2026, 03:41 PM UTC

1. investigating May 01, 2026, 12:29 PM UTC

   We're investigating an issue where OPRA.PILLAR historical data is being published with a delay. The live API is not affected.

2. identified May 01, 2026, 03:06 PM UTC

   Historical data has been released for 2026-04-30.

3. resolved May 01, 2026, 03:41 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 27, 2026, 10:13 AM UTC· resolved Apr 28, 2026, 10:26 PM UTC

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.

Read the full incident report →

Started Apr 23, 2026, 06:16 PM UTC· resolved Apr 23, 2026, 09:25 PM UTC

1. identified Apr 23, 2026, 06:16 PM UTC

   We have identified an issue where high latencies are being observed for some MBP-10 subscriptions on GLBX.MDP3. Other schemas are not affected Affected customers are instructed to disconnect manually and reconnect.

2. identified Apr 23, 2026, 06:17 PM UTC

   We are continuing to work on a fix for this issue.

3. monitoring Apr 23, 2026, 06:23 PM UTC

   Feed handler latencies for MBP-10 look reverted back to normal. We continue to monitor for any abnormalities.

4. resolved Apr 23, 2026, 09:25 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 07, 2026, 05:20 PM UTC· resolved Apr 07, 2026, 08:58 PM UTC

1. identified Apr 07, 2026, 05:20 PM UTC

   Batch jobs for historical data are currently being processed slowly. During this period, jobs may appear as "queued" or have a "stuck" completion percentage. No additional action is needed to resume these jobs, and they will be processed in first-in-first-out order so there is no need to re-submit them.

2. resolved Apr 07, 2026, 08:58 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 06, 2026, 08:10 PM UTC· resolved Apr 06, 2026, 08:38 PM UTC

1. identified Apr 06, 2026, 08:10 PM UTC

   We're aware of intermittent errors and/or timeouts on the Historical API as of 19:46 UTC. We've identified that this is caused by a networking issue impacting one of our servers providing our Historical API. We expect this should be resolved within 15 minutes.

2. monitoring Apr 06, 2026, 08:31 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Apr 06, 2026, 08:38 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 06, 2026, 12:43 PM UTC· resolved Apr 06, 2026, 01:42 PM UTC

1. identified Apr 06, 2026, 12:43 PM UTC

   Historical data after 2026-04-06 00:00 UTC (the last ~12 hours) is unavailable in most datasets: ARCX.PILLAR EDGX.PITCH EDGA.PITCH BATS.PITCH BATY.PITCH EPRL.DOM IEX.TOPS MEMX.MEMOIR OPRA.PILLAR XASE.PILLAR XBOS.ITCH XCHI.PILLAR XCIS.PILLAR XEEE.EOBI XEUR.EOBI XNAS-BASIC XNAS.ITCH XNYS.PILLAR XPSX.ITCH

2. monitoring Apr 06, 2026, 01:11 PM UTC

   A fix has been implemented and we are monitoring; data should be available within 10 minutes.

3. resolved Apr 06, 2026, 01:42 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 02, 2026, 02:48 PM UTC· resolved Apr 02, 2026, 03:36 PM UTC

1. investigating Apr 02, 2026, 02:48 PM UTC

   One of or GLBX.MDP3 live gateways sterted experiencing anomalous behavior and was brought down. Affected customers are instructed to reconnect.

2. monitoring Apr 02, 2026, 02:48 PM UTC

   We have taken the affected gateway out of the pool. Affected customers were disconnected and are instructed to reconnect.

3. investigating Apr 02, 2026, 02:55 PM UTC

   Other gateways started experiencing anomalous behavior, leading to crossed books on some instruments. We have taken those gateways from the pool. Gateway throughput is affected by this and customers may experience increased latency.

4. monitoring Apr 02, 2026, 03:09 PM UTC

   We have manually cleared books for the affected channels on the affected instance. Customers experiencing low throughput are instructed to reconnect to be steered to one of the other gateways

5. resolved Apr 02, 2026, 03:36 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 30, 2026, 08:06 AM UTC· resolved Mar 30, 2026, 02:16 PM UTC

1. identified Mar 30, 2026, 08:06 AM UTC

   CME (dataset GLBX.MDP3) data through the historical API is delayed. We are working to get data from this week's session available soon.

2. monitoring Mar 30, 2026, 12:33 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Mar 30, 2026, 02:16 PM UTC

   This incident has been resolved. Data from this weeks session is up to date and available though the historical API.

Read the full incident report →

Started Mar 19, 2026, 09:46 AM UTC· resolved Mar 19, 2026, 02:49 PM UTC

1. investigating Mar 19, 2026, 09:46 AM UTC

   One of our live servers stopped processing incoming data. The live gateway will be shutdown. The affected customers should reconnect to be redirected to one of the other servers.

2. monitoring Mar 19, 2026, 12:54 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Mar 19, 2026, 02:49 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 15, 2026, 11:06 PM UTC· resolved Mar 21, 2026, 02:18 AM UTC

1. investigating Mar 15, 2026, 11:06 PM UTC

   We are currently investigating an issue where crypto products on CME (dataset GLBX.MDP3) are unavailable in the Live API.

2. identified Mar 16, 2026, 12:37 AM UTC

   We've identified an issue with our network connectivity vendor impacting channels 326 and 327 (Crypto Futures and Crypto Options, respectively). This impacts both our Live and Historical APIs for the GLBX.MDP3 dataset. Our current plan is to reconfigure our network and restart our gateways during the next session pause at 5-6 PM ET (21:00 - 22:00 UTC). Until then, we're continuing to investigate to see if we can enable access to these channels ahead of the pause.

3. monitoring Mar 16, 2026, 01:06 PM UTC

   We have temporarily stood up a separate gateway at glbx-mdp3.crypto.lsg.databento.com to serve the cryptocurrency channels. Clients should configure their cryptocurrency subscriptions to target that gateway for this week. For example in the Python client: ``` import databento as db client = db.Live(gateway="glbx-mdp3.crypto.lsg.databento.com") client.subscribe(dataset="GLBX.MDP3", schema="bbo-1s", stype_in="continuous", symbols="MBT.c.0") ``` Market data is available starting on 12:35Z. Data prior to that moment is not available. The cryptocurrency channels will not be added to the normal instances until the weekend. This change will be reverted over the weekend.

4. monitoring Mar 17, 2026, 11:58 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Mar 21, 2026, 02:18 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 12, 2026, 02:59 PM UTC· resolved Mar 12, 2026, 09:04 PM UTC

1. identified Mar 12, 2026, 02:59 PM UTC

   We're seeing higher latencies on our GLBX live gateways and we'll be performing a rolling restart to address the issue

2. monitoring Mar 12, 2026, 03:10 PM UTC

   We've restarted all the gateways and we'll continue monitoring latencies

3. resolved Mar 12, 2026, 09:04 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 11, 2026, 04:44 AM UTC· resolved Mar 11, 2026, 05:41 PM UTC

1. identified Mar 11, 2026, 04:44 AM UTC

   Some long-running batch jobs (that take more than 1 hour to process) are running at a slower, degraded rate. We expect the processing to resume at a normal speed within a few hours.

2. resolved Mar 11, 2026, 05:41 PM UTC

   The batch job processing issue has been resolved, jobs are processing at a normal speed.

Read the full incident report →

Started Feb 28, 2026, 11:51 AM UTC· resolved Feb 28, 2026, 11:58 PM UTC

1. identified Feb 28, 2026, 12:34 PM UTC

   Our historical API and portal are down due to a power issue impacting our storage cluster. Although markets are not open, the Live APIs should not be impacted.

2. identified Feb 28, 2026, 01:02 PM UTC

   We are working to fully restore power, and until then batch download processing is paused.

3. identified Feb 28, 2026, 01:23 PM UTC

   The API and Portal have been restored, with the exception of batch job processing which is still paused. (Existing completed batch jobs can still be accessed.)

4. monitoring Feb 28, 2026, 01:54 PM UTC

   Batch job processing has been resumed. Our APIs have all been restored. We're continuing to monitor for power issues over the next few hours.

5. resolved Feb 28, 2026, 11:58 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 25, 2026, 02:20 AM UTC· resolved Feb 25, 2026, 04:50 AM UTC

1. monitoring Feb 25, 2026, 02:20 AM UTC

   There are currently delays in processing batch downloads, we believe the root cause of the issue with our system has been resolved and it is catching up. We expect processing to return to normal within 2 hours.

2. resolved Feb 25, 2026, 04:50 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 11, 2026, 03:30 PM UTC· resolved Feb 11, 2026, 10:01 PM UTC

1. investigating Feb 11, 2026, 03:30 PM UTC

   We're currently investigating an issue with degraded throughput on our GLBX.MDP3 gateways

2. identified Feb 11, 2026, 03:39 PM UTC

   We've restarted the affected gateways, affected clients are instructed to reconnect

3. monitoring Feb 11, 2026, 03:54 PM UTC

   We're continuing to monitor latencies after restart.

4. resolved Feb 11, 2026, 10:01 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 09, 2026, 09:32 PM UTC· resolved Feb 10, 2026, 11:21 AM UTC

1. investigating Feb 09, 2026, 09:32 PM UTC

   We're currently investigating a connectivity issue affecting some customers connecting to our DC3 gateways.

2. investigating Feb 09, 2026, 10:12 PM UTC

   The issue appears to have resolved on its own. We are still investigating the cause

3. monitoring Feb 09, 2026, 10:52 PM UTC

   After reviewing our logs, the majority of the connections that timed out originated from Virginia, more specifically AWS. As the incident resolved without any changes on our end, we believe the issue occurred there.

4. resolved Feb 10, 2026, 11:21 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 09, 2026, 10:50 AM UTC· resolved Feb 09, 2026, 01:54 PM UTC

1. investigating Feb 09, 2026, 10:50 AM UTC

   We have identified an outage affecting cbbo-1s/cbbo-1m and ohlcv schemas for XNAS.BASIC. Non-subsampled schemas are unaffected.

2. monitoring Feb 09, 2026, 12:06 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Feb 09, 2026, 01:54 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 08, 2026, 08:49 PM UTC· resolved Feb 08, 2026, 09:15 PM UTC

1. identified Feb 08, 2026, 08:49 PM UTC

   Our historical API is experiencing an outage that may cause intermittent request timeouts. This was caused by an unusual amount of request traffic causing some API instances to hit memory limit. Users may experience 502/504 request timeouts. A fix is in progress.

2. resolved Feb 08, 2026, 09:15 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 05, 2026, 03:03 PM UTC· resolved Feb 08, 2026, 08:46 PM UTC

1. monitoring Feb 05, 2026, 03:03 PM UTC

   Due to disk space concerns downstream from increased activity volume in the market, we reduced the live intraday replay from 24h to 10h for the rest of this week. Older data is available over the historical endpoint.

2. monitoring Feb 05, 2026, 03:04 PM UTC

   We are continuing to monitor for any further issues.

3. resolved Feb 08, 2026, 08:46 PM UTC

   This incident has been resolved.

Read the full incident report →