Subscribe to UpdatesSubscribe
Get email notifications whenever Databento creates, updates or resolves an incident.
Get text message notifications whenever Databento creates or resolves an incident.
Get incident updates and maintenance status messages in Slack.
Subscribe via Slack
By subscribing you acknowledge our Privacy Policy. In addition, you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy.
Visit our support site.
All Systems Operational
Uptime over the past 90 days. View historical uptime.
Portal
Operational
90 days ago
99.99
% uptime
Today
Historical
Operational
90 days ago
99.73
% uptime
Today
Live CME - Aurora DC3
Operational
90 days ago
99.93
% uptime
Today
Live US Equities - Secaucus NY4
Operational
90 days ago
99.85
% uptime
Today
Live OPRA - Secaucus NY4
Operational
90 days ago
99.81
% uptime
Today
Live ICE - Aurora DC3
Operational
90 days ago
99.87
% uptime
Today
FTP
Operational
90 days ago
99.98
% 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.
Related
No incidents or maintenance related to this downtime.
Past Incidents
Feb 9, 2026
No incidents reported today.
Feb 8, 2026
Resolved -
This incident has been resolved.
Feb 8, 21:15 UTC
Feb 8, 21:15 UTC
Identified -
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.
Feb 8, 20:49 UTC
A fix is in progress.
Feb 8, 20:49 UTC
Resolved -
This incident has been resolved.
Feb 8, 20:46 UTC
Feb 8, 20:46 UTC
Update -
We are continuing to monitor for any further issues.
Feb 5, 15:04 UTC
Feb 5, 15:04 UTC
Monitoring -
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.
Feb 5, 15:03 UTC
Older data is available over the historical endpoint.
Feb 5, 15:03 UTC
Feb 7, 2026
No incidents reported.
Feb 6, 2026
No incidents reported.
Feb 5, 2026
Resolved -
This incident has been resolved.
Feb 5, 12:22 UTC
Feb 5, 12:22 UTC
Monitoring -
We have identified one of our GLBX gateways stopped responding for ~5m.
The affected gateway was restarted.
Feb 5, 06:56 UTC
The affected gateway was restarted.
Feb 5, 06:56 UTC
Feb 4, 2026
Resolved -
This incident has been resolved.
Feb 4, 22:41 UTC
Feb 4, 22:41 UTC
Update -
We have restarted the instance exhibiting issues. Affected customers are instructed to reconnect.
Feb 4, 16:11 UTC
Feb 4, 16:11 UTC
Monitoring -
We have brought up additional production gateway resources to manage the extra load.
Feb 4, 15:03 UTC
Feb 4, 15:03 UTC
Resolved -
This incident has been resolved.
Feb 4, 22:40 UTC
Feb 4, 22:40 UTC
Monitoring -
An OPRA live instance without an important fix for a bug causing live symbology issues was brought up this morning. We've removed this instance from the prod pool
Feb 4, 19:34 UTC
Feb 4, 19:34 UTC
Feb 3, 2026
No incidents reported.
Feb 2, 2026
Resolved -
This incident has been resolved.
Feb 2, 17:35 UTC
Feb 2, 17:35 UTC
Update -
We are continuing to monitor for any further issues.
Feb 2, 13:21 UTC
Feb 2, 13:21 UTC
Update -
We have identified and solved the issue, and have migrated XNAS.BASIC to a new host.
Connected customers are required to restart their connections.
Feb 2, 13:19 UTC
Connected customers are required to restart their connections.
Feb 2, 13:19 UTC
Monitoring -
We have migrated the XNAS.BASIC gateway to a new functioning host - it will, however, require manual reconnection on the client side.
Clients are instructed to manually restart their connections to be redirected to the new host. Clients will NOT be automatically disconnected.
Not regarding replay: Data prior to this point should be available over the historical connection for backfill, but will have been lost on the live endpoint.
Feb 2, 13:19 UTC
Clients are instructed to manually restart their connections to be redirected to the new host. Clients will NOT be automatically disconnected.
Not regarding replay: Data prior to this point should be available over the historical connection for backfill, but will have been lost on the live endpoint.
Feb 2, 13:19 UTC
Investigating -
For the live XNAS.BASIC dataset, cmbp-1, cbbo-1s, cbbo-1m, ohlcv messages are not being published.
XNAS.ITCH is unaffected. Historical data is unaffected.
Feb 2, 11:33 UTC
XNAS.ITCH is unaffected. Historical data is unaffected.
Feb 2, 11:33 UTC
Feb 1, 2026
No incidents reported.
Jan 31, 2026
No incidents reported.
Jan 30, 2026
Resolved -
This incident has been resolved.
Jan 30, 09:35 UTC
Jan 30, 09:35 UTC
Update -
We restarted the gateways in an attempt to improve this issue; Affected customers are instructed to reconnect
Jan 29, 16:59 UTC
Jan 29, 16:59 UTC
Investigating -
We're investigating an issue with increased latency on the GLBX.MDP3 live gateway.
Jan 29, 16:52 UTC
Jan 29, 16:52 UTC
Jan 29, 2026
Resolved -
The fix is working and the issue did not reoccur
Jan 29, 02:40 UTC
Jan 29, 02:40 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jan 28, 17:30 UTC
Jan 28, 17:30 UTC
Identified -
We are restarting the live gateways with a fix to the symbology, affected clients are instructed to reconnect
Jan 28, 17:24 UTC
Jan 28, 17:24 UTC
Investigating -
We're investigating an issue with OPRA.PILLAR live data where some symbols are receiving duplicated instrument ids.
This is affecting subscriptions with stype_in=raw_symbol for the affected instruments.
Affected users are instructed, as a workaround, to subscribe using stype_in=instrument_id and the earlier instrument id.
Jan 28, 15:45 UTC
This is affecting subscriptions with stype_in=raw_symbol for the affected instruments.
Affected users are instructed, as a workaround, to subscribe using stype_in=instrument_id and the earlier instrument id.
Jan 28, 15:45 UTC
Jan 28, 2026
Resolved -
This incident has been resolved.
Jan 28, 17:45 UTC
Jan 28, 17:45 UTC
Update -
We are continuing to monitor for any further issues.
Jan 28, 17:45 UTC
Jan 28, 17:45 UTC
Monitoring -
We have failed over to a different gateway, affected clients are instructed to reconnect
Jan 28, 15:41 UTC
Jan 28, 15:41 UTC
Update -
We are continuing to investigate this issue.
Jan 28, 15:40 UTC
Jan 28, 15:40 UTC
Investigating -
One of our GLBX.MDP3 gateways stopped processing messages.
Jan 28, 15:35 UTC
Jan 28, 15:35 UTC
Jan 27, 2026
No incidents reported.
Jan 26, 2026
Resolved -
This incident has been resolved.
Jan 26, 14:17 UTC
Jan 26, 14:17 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jan 26, 13:04 UTC
Jan 26, 13:04 UTC
Update -
We have failed over our XNAS.ITCH gateway to another instance. Affected clients are instructed to reconnect.
Jan 26, 13:04 UTC
Jan 26, 13:04 UTC
Identified -
The issue has been identified and a fix is being implemented.
Jan 26, 13:04 UTC
Jan 26, 13:04 UTC
Resolved -
This incident has been resolved.
Jan 26, 13:01 UTC
Jan 26, 13:01 UTC
Update -
We have identified the root cause of this issue and implemented a fix.
Clients are now able to subscribe to the OHLCV and BBO schemas for all ICE datasets.
Other schemas were not affected.
Full replay is available for the OHLCV and BBO schemas on reconnection for the period of the outage.
We are continuing to monitor.
Jan 26, 10:59 UTC
Clients are now able to subscribe to the OHLCV and BBO schemas for all ICE datasets.
Other schemas were not affected.
Full replay is available for the OHLCV and BBO schemas on reconnection for the period of the outage.
We are continuing to monitor.
Jan 26, 10:59 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jan 26, 10:22 UTC
Jan 26, 10:22 UTC
Investigating -
We are currently investigating this issue.
Jan 26, 09:59 UTC
Jan 26, 09:59 UTC