16

I was trying to access SEDE and was greeted by a nginx 503 error. I refreshed the page, once, and was then greeted with the following error:

Too many requests

This IP address <My IP Address> has performed an unusually high number of requests and has been temporarily rate limited. If you believe this to be in error, please contact us at [email protected].

When contacting us, please include the following information in the email:

Method: block

IP: <My IP Address>

RAY ID: a156ba993ff479c4

GEO: GB

I'm confident no one else at the office is trying to access SEDE, but just in case, I switched to my VM at the data centre, and tried again. As I wasn't logged in I did actually manage to load the site. I logged in, and then was greeted with a 503 error. Refreshing gave me the above error, but with my IP at the data centre.

I then launched my VPN instead, giving me a third IP. Same interaction; first a 503 error and then a "too many requests". Why is 2 attempts now "too many"? There is an email address to email, yes, but this doesn't appear to be a problem with a single IP, but with the service; 3 IPs blocked in short succession from 2(ish) requests each means that it's not me abusing the services.

A couple of moderators from different sites in the network also experience the same issue, and geographically are in completely different parts of the world; this therefore doesn't appear to be IP, Account, or individual server related (unless all global users are being routed to the same server at the moment, which I would hope not, if there's multiple servers for resource balancing).

Improve this question
6
  • 8
    It is two many. Commented Jul 3 at 15:17
  • 1
    related / similar issue: meta.stackexchange.com/questions/408051/… Commented Jul 3 at 18:25
  • 6
    I can reproduce this and am seeing the same issue. Commented Jul 3 at 23:58
  • 1
    more similar issues in meta.stackexchange.com/q/410488/997587 and its linked questions. surprisingly, I can't repro right now. but since at least one other person can, I'm going to tag status-review. though, on first page load of the new query page, I did get an issue where all the resources didn't load (I could tell because there was no syntax highlighting), and when I clicked "run query", it returned the captcha by making the whole page the captcha response instead of rendering it near the run button. unfortunately not the first time I've seen that issue. Commented Jul 4 at 21:56
  • 2
    I just got hit with this today after reloading a tab that went dormant; Ray ID a1798d3a7a0569f9 Commented Jul 7 at 20:21
  • 1
    I just had this issue as well, having run a query only once and then getting rate-limited when trying to run it again with a different search term. Commented Jul 8 at 17:49

0

Reset to default

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.