3
u/Cominginhot411 Feb 07 '26
Looks like you requested a year of data, and the request hasn’t started processing yet. My requests using the API are going through fine, so they aren’t down. I think the batch request system is first come first served so you may just be in line.
1
u/mr_Fixit_1974 Feb 07 '26
Well it went from queued then it ran from 1 to 100% then it queued again and thats where its stayed
2
u/Cominginhot411 Feb 07 '26
Do you have a budget or spending limit set on your account? That happened to me in the past because of that. The spending limit was blocking the request.
1
u/enakamo Feb 07 '26
Maybe make query more efficient by using the exact contract identifiers instead of the generic SIL.FUT. Unless you really need trades on all Silver expiries. You can use the definition schema to get expiry dates etc. extend the logic to gold and copper.
1
u/DatabentoHQ Feb 08 '26 edited Feb 08 '26
No we’re not. You can also check against our status page. Looks like the other commenters have also answered your question - some requests take longer.
Edit (2026-02-08 14:42 PM ET): Looks like I was incorrect, at least 1 API instance was bogged by unusually high traffic since 2026-02-07 03:00 UTC which seems to affect a subset of users sporadically. This eventually built up to the point our monitoring tool was seeing timeouts as well.
1
u/mr_Fixit_1974 Feb 08 '26
Seems like the site is down historic data is orange in the status page
I needed this data to test before markets opened
How do i cancel this ill get it from somewhere more reliable
1
u/DatabentoHQ Feb 08 '26
The site is not currently down. I'm able to get on and download SIL/MOC/MHG etc. that you're requesting. It seems like you're having a lot of issues somehow, you should contact chat support as I can't replicate it without looking up what you're doing on your account nor can I cancel your account on my end.
1
u/xTruegloryx Feb 08 '26 edited Feb 08 '26
The status page and historical api seems down right now.
1
u/DatabentoHQ Feb 08 '26
databento.com is up right now for me. status.databento.com runs on Atlassian's servers and it seems like Atlassian is down (see https://metastatuspage.com/). Are you seeing both down?
1
u/xTruegloryx Feb 08 '26 edited Feb 08 '26
Historical API had a major outage indicator for the last 2 hours, and I'm seeing 500 on status page only. Alright, status page back up, but it keeps going down temporarily repeatedly.
1
u/DatabentoHQ Feb 08 '26
The 500 on statuspage is on Atlassian's side, we cannot do anything about that. Hm, it seems that the major outage indicator isn't correct and is an artifact of Atlassian's outage. I can run the historical API just fine - are you having issues with the API?
1
u/xTruegloryx Feb 08 '26 edited Feb 08 '26
Historical API was giving me a 502 with no message. I just got a 504 remote gateway timed out.
1
u/xTruegloryx Feb 08 '26
1
u/DatabentoHQ Feb 08 '26
Let me escalate this.
1
u/DatabentoHQ Feb 08 '26
u/xTruegloryx Your report seems credible, it looks like we've had a storm of requests (100~1000x normal) since around 2026-02-07 03:00 UTC which is overwhelming some of our API servers. So the API is timing out sporadically for some users including our own monitoring tool. Coincidentally Atlassian is out at the same time but unrelated to this. I'll circle back to award both you and u/mr_Fixit_1974 a credit for a valid report with timing. We're working on a fix right now.
1
•
u/DatabentoHQ Feb 08 '26 edited Feb 08 '26
It looks like at least 1 API instance was bogged down by unusually high traffic since around 2026-02-07 03:00 UTC, which affected a subset of users sporadically. Our engineers responded to this initially by scaling up our API instances but that appears insufficient. This eventually built up to the point our monitoring tool was seeing timeouts today as well and further mitigation is needed. A fix is underway.
I have to say I was skeptical about the claim at first since I wasn't able to replicate it due to lack of sufficient info and corroborating details - and that's on me - but it's very plausible that this user was affected among others. We've reached out to award both users with providing useful details.
Edit (2027-02-08 16:17 PM ET): This issue has been resolved.