-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Increased throttling starting 2021-09-23? #841
Comments
@danlinenberg yes, same here, trying to spread the work across different ips. |
@danlinenberg same here. I added a sleep 2-5 seconds between the tickers, and it seemed to work for now. But I cannot be sure if all data are correct and up to date. Don't know if it's throttling, or hitting a cache server with outdated data. Really annoying as it's unpredictable. Anyone know a better way of solving this issue? btw, is yfinance version related to this problem? I'm using the latest 0.1.63. Thanks. |
I have this issue. I was running my download scripts in parallel rather than sequentially. This has made me realize how dependent I am on one source of data. I'm gonna look for a second free source of data to collect data from along with yfinance going farward. |
I got a similar issue. I suspect it has something to do with (Multi-)Threading of the download. By turning off the multithreading it is far slower but it seems to get all the data from yahoo until today correctly. Many other issues hint to the same problem in September, but i have no clue where to search for a solution |
Options:
|
This probably isn't a yfinance issue, but I didn't find any other place to ask this -
I noticed that starting 2021-09-23, after querying historical prices for a few tickers, Yahoo suddenly stops providing data for the last 2 weeks.
When going straight into Yahoo's UI (https://finance.yahoo.com/quote/AAPL/history) I can see starting from 2021-09-07 - there is no price data at all.
When I reset my IP or wait long enough - the problem gets resolved, so this seems intentional.
Does anyone else experience something similar to this?
The text was updated successfully, but these errors were encountered: