Skip to content

Too Many Requests Error even though there hasn't been? #57

Discussion options

You must be logged in to vote

Hey @marwan-at-work!

The error you're getting is actually due to an internal rate limit that's being hit, not anything to do with your connection volume. As you pointed out, it's normal course of business for a service to initiate 100s of connections (if not thousands) when it's being deployed or scaled out. Our connection handling system doesn't rate limit this when it's functioning properly, but right now it's a bit behind due to some internal scaling limitations.

I'm sorry you're experiencing this, and we're working on getting things back to full capacity as quickly as possible.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by hallaroo
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants