Unresponsive dns

seneca-public-site.netlify.app

Since this morning we are facing a production issue on accessing https://senecalearning.com/. We think it might be linked to a DNS issue cause we are receiving 429 responses. Could you confirm that everything is good on the netlify side of things if you have access to logs, etc?

Our domain is hosted with AWS, correspondence from them on this.

"
I understand that you are getting HTTP 429 responses when connecting to https://senecalearning.com.I checked the Route 53 configuration of this resource record and I can see that it points to an IP address of 75.2.60.5.DNS resolving this FQDN works as expected:
\t\t$ dig senecalearning.com\t\t; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.68.rc1.87.amzn1 <<>> senecalearning.com
\t\t;; global options: +cmd
\t\t;; Got answer:
\t\t;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61678
\t\t;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0\t\t;; QUESTION SECTION:
\t\t;senecalearning.com. IN A\t\t;; ANSWER SECTION:
\ttsenecalearning.com. 60 IN A 75.2.60.5I can therefore confirm that the issue is not with Route 53 as it is resolving the IP address correctly but the issue is with the service that is accessed through the IP address of 75.2.60.5. I traced this IP address to an AWS Global Accelerator in another AWS account. AWS has security policies in place that only allows me to view resources in the account where the case is opened in so I cannot view resources in another AWS account without getting explicit authorization from that account owner. Please get the owner of the resources behind the Global Accelerator to log a case in that account with AWS to allow us to troubleshoot the resources in that account.
"

Hi, @Lukas1. I do see the site in question triggered the rate limits today. There was a highly unusual spike in traffic that triggered this. Were you perhaps doing load testing when this occurred?