Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Http code 429 on command "check status all" #129

Closed
charphi opened this issue Aug 2, 2021 · 1 comment
Closed

Http code 429 on command "check status all" #129

charphi opened this issue Aug 2, 2021 · 1 comment
Labels
bug Something isn't working PROVIDER
Milestone
3.0.0-beta.4

Comments

@charphi
Copy link
Member

charphi commented Aug 2, 2021

HTTP 429 = Too Many Requests response status
@charphi charphi added bug Something isn't working PROVIDER labels Aug 2, 2021
@charphi charphi added this to the 3.0.0-beta.3 milestone Aug 2, 2021
@charphi charphi modified the milestones: 3.0.0-beta.3, 3.0.0-beta.4 Sep 13, 2021
@charphi
Copy link
Member Author

charphi commented Sep 20, 2021 •
edited
Loading

check status command is currently using UptimeRobot as backend.
According to its documentation, the API returns 429 HTTP status code in the response when the rate limits are hit.
Theses limits seems to be too low for sdmx-dl usage.

Rate limits have been modified recently: only 10 requests/minute
https://blog.uptimerobot.com/uptimerobot-july-2021-update-heartbeat-monitor-and-api-rate-limits/

@charphi charphi mentioned this issue Sep 20, 2021
Closed
@charphi charphi closed this as completed Oct 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working PROVIDER
Projects
None yet
Milestone
3.0.0-beta.4
Development

No branches or pull requests
1 participant
@charphi