OPRA historical data for 2026-09-04 delayed
Sep 4, 15:12 UTCSep 7, 15:04 UTC
Duration
2d 23h
Impact
Informational
Root cause
Not disclosed
Databento, 90 days
13 incidents
Affected
Not listed by the vendor.
Final update
This incident has been resolved.
Timeline
- Resolved · Sep 7, 15:04 UTC
This incident has been resolved.
- Identified · Sep 4, 15:12 UTC
Our primary link between NY4 and our primary datacenter went down, reducing the available bandwidth needed for us to upload and process the OPRA.PILLAR for our historical API. In working with remote hands and our carrier we've identified that a hardware port failed on a network router in our BO1 datacenter. After migrating the physical connectivity we have restored the link. This only impacts accessing today's data (Friday 2026-09-04) for OPRA.PILLAR through `timeseries.get_range` or `batch.submit_job`. The Live APIs are not impacted. No data loss has occurred, processing will resume as usual on the next trading day.
More from Databento
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| 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 |
| Aug 407:47 UTC2 months ago | Consistent 504 timeout on the Historical API | major | 16h 13m |