Historical batch job processing is delayed
Apr 7, 17:20 UTCApr 7, 20:58 UTC
Duration
3h 38m
Impact
Minor
Root cause
Not disclosed
Databento, 90 days
13 incidents
Affected
Historical
Final update
This incident has been resolved.
Timeline
- Resolved · Apr 7, 20:58 UTC
This incident has been resolved.
- Identified · Apr 7, 17:20 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.
More from Databento
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 415:12 UTC4 weeks ago | OPRA historical data for 2026-09-04 delayed | none | 2d 23h |
| Aug 2807:59 UTC5 weeks ago | Live authentication timeouts in NY4 | critical | 6h 50m |
| Aug 2109:56 UTC6 weeks ago | Batch jobs being queued indefinitely | major | 3h 34m |
| Aug 1319:04 UTC7 weeks ago | GLBX.MDP3 intraday data is delayed | none | 5h 5m |
| Aug 1022:55 UTC7 weeks ago | GLBX.MDP3 delays in the Historical API | minor | 4h 3m |
| Aug 615:05 UTC8 weeks ago | Databento portal and historical API down | critical | 4h 26m |