Skip to content
Databento · Data and observabilityJul 24, 2026, 23:03 UTC 2 months ago

Intermittent API outage due to an internal DNS issue

MinorDNSUpdated 17h ago
Jul 24, 23:03 UTCJul 24, 23:20 UTC
Duration
17m
Impact
Minor
Root cause
DNS
Databento, 90 days
13 incidents
Affected
PortalHistoricalFTP
Status page

Final update

This incident has been resolved.

Timeline

  1. Resolved · Jul 24, 23:20 UTC
    This incident has been resolved.
  2. Monitoring · Jul 24, 23:04 UTC
    We've implemented a fix internally and the system looks healthy again. We'll continue to monitor.
  3. Identified · Jul 24, 23:03 UTC
    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.

More from Databento

Full history
StartedIncidentDuration
Sep 415:12 UTC4 weeks agoOPRA historical data for 2026-09-04 delayed2d 23h
Aug 2807:59 UTC5 weeks agoLive authentication timeouts in NY46h 50m
Aug 2109:56 UTC6 weeks agoBatch jobs being queued indefinitely3h 34m
Aug 1319:04 UTC7 weeks agoGLBX.MDP3 intraday data is delayed5h 5m
Aug 1022:55 UTC7 weeks agoGLBX.MDP3 delays in the Historical API4h 3m
Aug 615:05 UTC8 weeks agoDatabento portal and historical API down4h 26m

Also caused by dns

All
StartedIncidentDuration
Jul 2720:34 UTC2 months agoDelays in creation of DNS recordsSupabase2h 2m
Jun 2301:05 UTC3 months agoINC20000046Snowflake1h 30m
Jun 410:12 UTC4 months agoDNS API ServiceDigitalOcean1h 35m
May 2223:27 UTC4 months agoNew Database Creation Failing Due to Upstream Provider IssueUpstash32m
May 1413:57 UTC4 months agoDNS service, Certificates and Managed MongoDBDigitalOcean6h 49m
May 715:17 UTC5 months agoAWS Cluster DNS Changes Degraded PerformanceMongoDB6h 58m

Outages by email

Saturday mornings: the week's major outages, new postmortems and disclosed breaches, only in weeks that had some.

Double opt-in. Unsubscribe any time.